Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

25 stories

Likes earn the author +10 XP for the first 3 likes each day

Amazon Development Center U.S.Software Engineer
Reported Aug 2026

Amazon Development Center U.S. Software Engineer Interview Experience: Book management and delivery-system design

My final interviews were face-to-face and covered several technical lenses. I had DSA questions, a low-level design round to design a book-management system, and a leadership and behavioral discussion tied to Leadership Principles. The technical rounds put a lot of weight on explaining trade-offs while coding and designing. One design prompt resembled an LRU cache, while another resembled an Uber…

Onsite0
Amazon Development Center U.S.Software Engineer
Reported Aug 2026

Amazon Development Center U.S. Software Engineer Interview Experience: onsite loop with STAR follow-ups

My process ran from recruiter submission to HR questions and then an onsite-style technical loop. The onsite included several live coding segments, system design, and behavioral questions about how I would work in the role. Each round mixed categories. Alongside live coding, I discussed system-design tradeoffs and architecture beyond implementation details. For behavioral questions, I used STAR s…

Onsite0
Amazon Development Center U.S.Software Engineer
Reported Aug 2026

Amazon Development Center U.S. Software Engineer Interview Experience: leadership-focused virtual ladder

I went through an extended interview path that felt like climbing an organizational ladder. After the initial recruiter screening, I had virtual rounds with senior engineering leaders: an engineering director, a senior product owner, and a senior software engineer. Amazon's Leadership Principles were a major part of the loop. The Bar Raiser was a distinct stage, and I could not treat the behavior…

HR Screen0
Amazon Development Center U.S.Software Engineer
Reported Aug 2026

Amazon Development Center U.S. Software Engineer Interview Experience: OA versus live DSA round

The OA mixed classic DSA with aptitude-style material. The coding problems ranged from easy upward, and there were also statistics-and-probability questions, including estimation tasks that moved quickly and made me question how confident I was in my answers. The live interview felt lighter and more straightforward than the OA. In the technical round, I solved two easy DSA questions on a platform…

Online Assessment0
Amazon Development Center U.S.Software Engineer
Reported Aug 2026

Amazon Development Center U.S. Software Engineer Interview Experience: DSA complexity and leadership principles

After the recruiter step, I had a one-on-one virtual technical interview with an engineer. We moved quickly from small talk to two DSA problems on a shared coding platform, and I had to state time and space complexity as I worked. The broader loop was technical first with Leadership Principles throughout. It included multiple DSA-focused interviews, low-level design, and a dedicated leadership-pr…

0
Amazon Development Center U.S.Software Engineer
Reported Aug 2026

Amazon Development Center U.S. Software Engineer Interview Experience: bamboozling OA and mixed loop

I started with an online assessment before moving into an all-live-interview loop. The OA was the first real shock. The questions did not feel impossible, but I got completely bamboozled and did not get far enough to move to the next step. The loop itself had about three rounds of roughly an hour each, mixing coding and behavioral questions. Coding felt easy to medium for me, but the behavioral s…

Online Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: leadership and hard DSA

The process felt brutally demanding and somewhat long because it paired Leadership Principles with deep DSA expectations. After an initial recruiter stage, I faced technical questions presented as DSA problems at a higher level than I expected. I received multiple DSA problems in one stretch. I solved only part of them; I could not reach working solutions for the rest. Throughout, the interviewer…

Technical Screen0
Amazon Development Center U.S.Customer Success Engineer
Reported Jul 2026

Amazon Development Center U.S. Customer Success Engineer interview: approachable coding and AI

The interviews did not feel especially hostile, and the pace was manageable. After applying, I completed an automated online assessment and then had rounds that mixed straightforward coding with behavioral questions. The live coding questions were more approachable than the horror stories I had heard. One involved finding duplicates and another resembled Longest Common Prefix. There was a lot of…

Online Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: design then manager rounds

I went through three rounds that moved from technical work to more managerial conversations. The first was system design: I was asked to design a streaming application like Netflix or Amazon Prime Video. I focused on structuring the design and its trade-offs, and that was the only technical round I cleared. The remaining rounds were managerial. They focused on how I work, how I think about delive…

Technical Screen0
Amazon Development Center U.S.Software EngineerIntern
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview experience: grid paths and RAG

My on-campus Amazon SDE Intern process began with an online assessment. It combined coding with a Leadership Principles work simulation and a feedback or workstyle component. Only some students from the campus drive were shortlisted for the OA. The coding included sorting IDs by frequency with smaller-ID tie-breaking, and an array-transformation minimum-cost problem based on greedy reasoning and…

RejectedOnline Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer Interview Experience: debugging under time pressure

One technical sequence began with a medium LeetCode-style problem and then switched to debugging a web application. The assistant I could use was tightly limited: it could read files and explain components, but it would not provide the answer. Understanding the bug mattered, but so did staying organized while navigating the codebase under time pressure. I could follow the logic, yet the debugging…

Online Assessment0
Amazon Development Center U.S.Software EngineerIntern
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: SDE Intern assessment mix

The SDE Intern process was described as a mix of coding ability, problem solving, computer-science fundamentals, and Leadership Principles fit. It began with an OA, then continued through rounds on leadership principles and core subjects, DSA, and more leadership-principle evaluation. The exact timeline could vary by country and hiring season, but the stated structure kept coding and fundamentals…

Online Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: compact linked-list screen

I had about two rounds, split between behavioral and technical work. The technical questions were LeetCode-style and mostly easy to medium, so I initially expected to move through them cleanly. I solved a couple of questions on a coding platform and then reached a single technical round with one linked-list problem. It required careful structural thinking rather than pattern recall. I did not get…

Technical Screen0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: timed first stage

The process had three stages and moved quickly from the first assessment into a work-style component. The opening stage had two parts: a couple of timed coding questions and then a workstyle assessment. I did not finish that first stage, so the process stopped there. I had to solve two coding problems within their time windows. I felt I was managing my time, but still could not make enough progre…

RejectedOnline Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Software Engineer interview at Amazon Development Center U.S.: interview experience

The loop had several distinct themes, and it was clear what each interviewer was assessing. Multiple technical rounds began with troubleshooting and GenAI fluency, then moved into coding problem-solving and the DSA-style reasoning Amazon looks for. Later rounds became more behavioral and principle-based. A hiring-manager-style discussion covered earning trust, learning curiosity, and operational…

0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: a GenAI round within the virtual loop

The process began with an online assessment containing coding challenges and a work simulation. The interviews that followed felt like an Amazon loop, combining technical evaluation with Leadership Principles rather than separating them. The virtual onsite consisted of several back-to-back interviews of about an hour each, including hiring-manager-type and bar-raiser-style discussions. Each inter…

0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: repository coding and interviewer connectivity issues

I had four roughly hour-long panel rounds, with Amazon Leadership Principles woven through technical discussion in each one. I had to connect my answers to impact and decisions instead of treating the behavioral material separately. The first technical round included two DSA questions, one of them repo-based within an existing codebase. I got the core solution underway but ran out of time while w…

0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: a structured coding and design loop

My process followed what felt like the classic Amazon sequence. A recruiter screen led to a take-home LeetCode-style coding assessment, followed by live coding. I then had a system-design interview with two separate design questions and finished with a behavioral interview about communication and collaboration. The structure was what I remembered most. The behavioral questions asked me to demonst…

Online Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: consecutive loop with bar raiser

After the online assessment, I went straight into a back-to-back loop that felt exhausting but focused. The interviews ran consecutively, and the bar-raiser-style behavioral round carried a lot of weight. It felt harder than the other behavioral conversations. The other rounds mixed technical work with behavioral prompts tied to how I handle real situations. Technical coverage included strings, d…

Online Assessment0
Amazon Development Center U.S.Software Engineer
Reported Jul 2026

Amazon Development Center U.S. Software Engineer interview: resilience under pressure

The interview loop felt brutal but streamlined. It mixed behavioral and technical questions, but the defining feature was heavy artificial time pressure used as a deliberate stress test. The questions made me feel as though they wanted to push me close to breaking, with the clock forcing me to show how I perform under strain. The technical difficulty was high, not only because of the problem itse…

0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP