My technical rounds were very backend-leaning and practical. I sat through questions centered on the framework I’d been working with and MongoDB, and the interviewer also pulled in topics connected to my projects and how I communicated while discussing them. SQL came up too, so it wasn’t purely NoSQL.
There was also a round where the coding portion was more like basic exercises—things like finding the largest and smallest values, checking Armstrong numbers, and working through prime number logic. I paired that with SQL query questions such as finding the second largest value, and I had to explain a project while answering cross-questions that tied back to what I’d described. The difficulty felt moderate overall, and the biggest thing I noticed was how much they wanted me to connect coding to the data layer and to my real experience.
10 months ago
Average Negative Hyderābād
My experience was smooth technically at first, but it turned into a frustrating communication and timing problem. I went through a three-round process where the first two were technical and the third was cultural. After I cleared the technical rounds, I received an email saying I’d passed and that I needed to upload documents.
I was told to join within a week, even though there wasn’t an offer letter in hand. Right before my start date, HR informed me the client had closed the position and that my offer was no longer considered. A similar story also happened around an accepted offer: after months of interviews and even a client meeting, the client team ultimately decided not to proceed after a requirements shift they cared about—specifically AWS experience—even though everyone had already known my level. The final feeling both times was shock and disbelief; I’d put in the effort for a path that looked solid, then it was reversed because the client decision landed at the worst possible moment.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
