The interview process consists of two stages. The first stage is a technical call with a Senior Software Engineer (SSE), where general questions are asked to assess your technical knowledge. The second round of the interview is quite extensive and includes coding, system design, and behavioral assessments. During the coding segment, you will be presented with an ASP.NET project and asked to review it as if you were handling a pull request (PR). You should discuss all the issues you identify in the code and suggest improvements. There is no need to write any code; you will just be talking about the issues. In the system design portion, you will be tasked with designing a system that allows a customer to submit an order to a restaurant. The behavioral questions will primarily focus on your soft skills.

It was a single interview, long video call. After introductions, the lead engineer dove into questions about my last project. I described building a microservices architecture, but they pushed deeper, asking why I chose certain design patterns. Then came the coding challenge. They wanted a solution to a sorting problem but expected a time-efficient approach. I started explaining my plan, conscious of the clock ticking, and shared my screen to code in real time. Halfway through, I hit a snag with an off-by-one error. The interviewers nodded, and we moved to system design part. The final round was behavioral questions.

1st stage interview with internal recruiter. 2nd stage interview with hiring manager. Had to present a recent project I worked on recently, talk about learnings, challenges etc. This was followed by a leet-code styled tech test.