The most surprising part of my experience was how time and scheduling pressure shaped the interview day. I was told the evaluation was broken into clear areas—coding, behavior, system design, and bar-raiser—but the reality felt more blended, with not enough time to fully address any one topic. One interview run dragged into a compressed session where I had to juggle multiple coding problems quickly, and I also lost time during the system design discussion when the interviewer arrived late.
Later, I had a day where interviews were effectively stacked in the morning and afternoon. The interviewers would bring rough prompts with vague edges, and I had to straighten out the missing details on the fly and verify my answers as I went. Even when I understood what they were aiming for, that “figure out the vague parts” style made the pacing feel even tighter.
9 months ago
Difficult Neutral India
Recruiter communication was the part that defined my experience early on, and not in a good way. I went through an interview process that felt very similar to Amazon’s style—leadership principles were a major thread in the questions, and the tech portion leaned toward hard DSA problems where time complexity mattered.
The interviews themselves came with a lot of “think deeply” pressure: it wasn’t just about getting to an answer, it was about demonstrating how I reasoned through difficult cases and how I handled trade-offs in my approach. Even with that, what threw me off was how the process didn’t feel smooth from a logistics standpoint, and I didn’t get a clear follow-up after I finished.
10 months ago
Easy Positive China
After a resume screen, my interview loop moved straight into technical rounds. The day I went in, I had multiple back-to-back interviews where I kept …
11 months ago
Difficult Positive Seattle, WA
My process felt like a pretty standard tech-leaning loop with a few distinct checkpoints. After recruiter outreach and an initial pass, I moved into a…
> 1 year
Average Positive Singapore
My process started more conversationally than I expected. After an HR conversation on a video call, I had a hiring manager discussion where we talked …
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 & Flow
The interview process is typically structured with multiple back-to-back rounds, including coding, system design, and behavioral interviews, often leading to a compressed schedule that can feel chaotic. Candidates should prepare for a mix of technical and conversational styles, with a focus on problem-solving and design discussions.
Candidates can expect a strong emphasis on data structures, algorithms, and system design, with interviewers valuing the reasoning and thought process behind solutions rather than just correct answers. Be prepared for coding challenges that may include edge cases and require clear explanations of your approach.
Data structuresAlgorithmsSystem design
Behavioral & Leadership Principles
Behavioral interviews often incorporate leadership principles similar to those used at Amazon, focusing on how candidates align with the company's values and culture. Candidates should be ready to discuss past experiences and demonstrate their thought processes using frameworks like STAR.
Many candidates reported inconsistent communication from recruiters throughout the process, leading to uncertainty and frustration regarding interview outcomes. It's advisable to seek clarity on timelines and feedback after each stage to manage expectations.
The interview atmosphere can vary significantly, with some candidates experiencing a supportive and conversational tone while others felt the process was more adversarial or chaotic. Candidates should be prepared for different interviewer styles and adjust their approach accordingly.
While many candidates did not receive offers, they often reflected positively on the thoroughness of the process and the opportunity to showcase their skills. It's important to view the experience as a learning opportunity, regardless of the outcome.