Loading Question...
The first round was heavily conversational and voice-driven rather than a live coding round. I didn't have to write code or solve complex DSA problems during the call.
The AI interviewer focused on my resume, past projects, practical engineering decisions, core CS concepts, and communication skills. It also asked follow-up questions based on my responses to assess my technical understanding in depth.
The discussion focused on:
Preparation tip: Review every project on your resume and be ready to explain the architecture, your contributions, challenges, and technical decisions. Practice answering aloud in a clear, structured manner, as the round is conversational and limited to 25 minutes.
Last updated Oct 11, 2026
I was given a string-related DSA problem to determine whether a password was weak or strong. I had to solve the problem within the allotted 25 minutes.
After submitting my solution and passing all test cases, the AI interviewer asked detailed follow-up questions about my implementation, including:
The AI interviewer then modified the original problem and asked me to explain my approach to the updated requirements.
Additional follow-up: What would your approach be if passwords arrived as a continuous stream instead of being provided in a vector of passwords?
Overall, the round focused not just on solving the problem but also on understanding the reasoning behind my solution and adapting it to changing requirements.
The third round was scheduled with a senior engineer.
I completed my human interview today. Although the interview was scheduled for 20 minutes, it ended in approximately 10 minutes.
The interviewer asked me about my projects and open-source contributions, and I answered their questions.
I have mixed feelings about the interview because it ended much earlier than expected. However, the shorter duration alone doesn't necessarily indicate a positive or negative outcome.
Add a concise overview upfrontMake the interview timeline consistent