The process felt unusually disorganized and frustrating from the start. I was asked to join the interview at their office premises, and once I got there, the questions didn’t feel relevant to what I thought the role required. A lot of the discussion leaned toward definitions—answering in a very textbook way—yet I couldn’t tell what they were actually trying to evaluate.
The focus kept drifting toward how AWS works internally and specific steps, but the way they framed questions made it hard for me to connect my answers back to the real expectations. Difficulty aside, the bigger problem was the lack of clarity about what they wanted from me.
2 months ago
Average Negative Bangalore Rural
My interview itself felt like it went well. It was scheduled for June 9, and I felt the conversation matched my background and came across as productive.
But communication after the interview was where everything fell apart. I didn’t receive any update for several weeks, and I tried reaching HR multiple times by phone without getting a response. Eventually, after following up via text on July 3 with an HR representative, I was told I hadn’t been shortlisted.
2 months ago
Average Neutral Bangalore Rural
My first interview started with a DSA round that felt like a LeetCode-style problem, specifically interval-related, around medium to hard. We also tal…
4 months ago
Average Negative Bengaluru
My process ended up being five technical rounds, and by the end I could feel how tightly everything was being measured. The first two rounds were codi…
5 months ago
Average Positive San Josecito, Heredia
I started with scheduling that went quickly, and the first interview was with two members of the team. It was quite technical: they gave me a bit of c…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Rounds
The interview process typically consists of multiple technical rounds, often including coding assessments, system design discussions, and behavioral evaluations. Candidates should be prepared for a combination of live coding, whiteboarding, and discussions about their past projects and experiences.
Interviews emphasize technical depth, often involving DSA problems, cloud architecture, and practical application scenarios. Candidates should expect a range of difficulty from easy to medium-level problems, with some rounds focusing on specific technologies like AWS, SQL, or CI/CD processes.
Data structuresAWSCI/CD
Communication & Manager Interaction
Candidates may experience varying degrees of communication style, particularly during manager interviews, which can feel more directive and less conversational. It's important to be prepared for interruptions and to clearly articulate thoughts under pressure.
The interview timeline can be lengthy, often stretching over several weeks or even months, with candidates frequently reporting delays in communication and updates. Staying proactive in following up may be necessary to avoid feeling left in limbo.
TimelineFollow-upCommunication delays
Assessment of Fit & Culture
While technical skills are heavily evaluated, there is also a focus on cultural fit and alignment with team values, particularly during behavioral interviews. Candidates should be ready to discuss their experiences in a way that connects to the company's mission and teamwork.
Cultural fitBehavioral questionsTeam alignment
Feedback & Closure
Candidates often report a lack of clear feedback or closure after the interview process, which can lead to frustration. It's advisable to seek constructive feedback where possible to understand areas for improvement.