The interviewer informed me that this round would consist of two parts: the first half would focus on Leadership Principles (LP), and the second half would be a coding challenge. The LP round went well, and soon, I moved on to the coding part. The problem was similar to detecting a cycle in a graph. I began by explaining my approach, thinking out loud. To my surprise, the interviewer asked me to code the entire solution first and review it later. This caught me off guard, and for a moment, I felt unsettled. When I finally started coding, my mind went blank. However, I decided to take small steps and began coding the parts I was confident about. Gradually, I managed to piece together an almost correct solution. Next, I started the dry run. After testing the code with basic cases, I was convinced it was correct. But then, the interviewer introduced a test case that was completely unexpected—and my solution failed.
Interview by recuriter, Phone interview over Chime with one easy Leet code problem and 2 behavioral questions. Although the interviewer was very casual at the start of the conversation, it quickly changed into behavioral questions at the start.
Interview questions [1]
Question 1
Encoding optimization algorithm and talk about a project you did recently.
First round is just leet code coding which screens through AI before going into live coding. Pretty simple and straighforward. Not too tough. Recruiter walks through it pretty nicely. Not sure how many rounds there are exactly
After submitting my application for the Software Engineer position, I received an invitation to complete an automated Online Assessment (OA). The assessment consisted of standard coding challenges, primarily focusing on algorithmic and data structure problems. Unfortunately, a few days after submitting my solutions for the assessment, I received an email informing me that I would not be moving forward in the interview process and was rejected.