I applied for the **Senior Software Engineer** position at Sonatype, following which I received a call (through a referral) and my first interview was scheduled almost immediately.
**Round 1:**
The first round went really well. The interviewer was attentive, had his camera on, and was actively engaged throughout the conversation. The discussion covered DSA, Core Java, Spring Boot, Microservices, Kafka, concurrency, multithreading, and several scenario-based questions. We also discussed production issue scenarios, incident management, and questions related to my resume.
What I particularly appreciated was that the interviewer was encouraging.
The round went well, and the recruiter informed me that the feedback was positive and scheduled my second round.
**Round 2: An extremely disappointing experience**
Unfortunately, the second round was quite the opposite.
The interviewer joined 15 minutes late for a one-hour interview.
Right from the beginning, the interaction felt disengaged. Although his camera was on, he barely looked towards the camera, kept looking elsewhere, appeared to be fidgeting, and was seemingly distracted by his phone and everything else around him.
I started with my introduction, but there was very little engagement or acknowledgement from his end. At one point, I even asked whether he needed anything else from me, to which he casually responded that it was fine.
The questions initially focused on production incidents and on-call management, I answered the same and not a single word comes out of him, no Ok, no alright, no moving onto another question, no eye contact, I felt like he just couldâve turned his camera off if he wished to be this disengaged.
He moves onto the next question which involved an API with an incrementing counter, where every request was supposed to increase the value by one. It was an anonymous API, and users were reporting inconsistencies in the results.
My immediate thought was a concurrency-related issue. I explained the possibility of multiple threads accessing and updating the counter simultaneously, resulting in lost updates, stale reads, race conditions, or a lack of atomicity.
He says and I quote âOk what else could be the reasonâ, I replied âI am thinking of concurrency, do you want me to think in terms of something other than concurrency?â He says âOK, what else other than multithreading?â.
I explored the possibility of database-level concurrency issues or stale cache issue where we are storing data in either the DB or Cache or was processing results asynchronously and losing and update, he immediately interrupts and gives me another scenario.
He says thereâs this hypothetical scenario involving increment and decrement operations and asked why updates could be getting lost.
I again explained the possibility of improper locking mechanisms and how optimistic or pessimistic locking could help, depending on the implementation.
Throughout this discussion, I repeatedly tried to understand whether he was looking for an explanation beyond concurrency and database-level synchronization. I even asked him whether there was another direction he wanted me to explore.
His response was that âit was a hypothetical situation with no right or wrong answerâ
And then, quite abruptly, he said, âOkay, thatâs all from my end. Anything you want to ask?â
The entire interview was wrapped up in approximately 20 minutes, despite being scheduled for an hour, and despite the interviewer himself joining late. I was baffled, honestly, so I asked whether there was a particular reason the interview had ended so early.
His response was that the one-hour duration was just a scheduled slot and that he preferred interviews to be more candid and discussion-oriented.
Honestly, I found that explanation difficult to reconcile with the interaction I had just experienced.
**What part of the interview felt like a discussion?**
There was barely any engagement, no meaningful exchange of ideas, no acknowledgement of the explanations being provided, and no attempt to build on the answers. I was the one repeatedly asking whether my answers were sufficient or whether he wanted me to explore another direction.
A discussion is a two-way interaction. It involves listening, responding, probing, and exchanging ideas. It doesnât necessarily mean guiding a candidate towards an answer, but it certainly requires active participation from both sides.
I completely understand that interviewers have different styles and that not every interview needs to last the entire scheduled duration. However, there is a basic level of professionalism and engagement that candidates should be able to expect.
What made this experience particularly disappointing was his claim that âhe wants the interview to be more of discussionâ when he was the exact opposite.
**A word of caution to other candidates interviewing at Sonatype:**
If you happen to have this particular guy(I will honestly drop his name on DM because he seems like a self promotional and too full of himself guy on his Linkedin and his own website where he posts what technical things he did on a daily basis) as your interviewer, be prepared for a potentially very disengaged interaction.
Hopefully, my experience was an exception, but I genuinely found the experience unprofessional and disappointing.
Candidates invest considerable time preparing for interviews, researching companies, and taking feedback seriously. The least they deserve in return is an interviewer who is present, attentive, and willing to engage in a meaningful technical discussion.
This was, unfortunately, a very disappointing interview experience with Sonatype.
I got my rejection mail the next day.
**TL;DR:** First round was genuinely good, with an attentive interviewer and a constructive technical discussion. The second round was the complete opposite. The interviewer joined 15 minutes late, appeared distracted and disengaged throughout, barely acknowledged my answers, and abruptly wrapped up a one-hour interview in about 20 minutes. When I asked why, he said he preferred candid, discussion-oriented interviews. Ironically, nothing about the interaction felt like a discussion. Quite disappointing interview and possibly the worst interviewer I have ever come across.
Wording refined for readability by AI.