real interview stories, told over a cup of tea ♡
Amazon Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
396 results
- Amazon DSP Software Engineer interview with four coding loop roundsAmazon DSP · Software Engineer · Technical Screen · Aug 2026
The process followed a familiar Amazon pattern: a recruiter screen, then a time-boxed technical screen with behavioral questions first and a dedicated coding block after that. It ended with time for my questions. The final loop had four technical-style rounds. I solved data structures and algorithms problems in a shared coding environment while explaining my reasoning and trade-offs. Every round…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: 66% OA resultAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Aug 2026Rejected
After applying, I moved to an OA early in August, and it got difficult quickly. The experience was genuinely bamboozling. It was not one question that threw me off. The whole assessment did. I finished at about 66% overall and did not progress. I did come away with a clearer picture of the next stage. The usual path after the OA was a loop of three rounds, about an hour each, with coding and beha…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: coding plus leadership-principle follow-upsAmazon Kuiper Commercial Services · Software Engineer · HR Screen · Aug 2026
My path began with a recruiter screen and then a technical screening. That screen had a short introduction, behavioral questions, a coding segment, and time at the end to ask about Amazon. The final loop was much longer. I had multiple one-hour interviews with different people, each mixing live coding and behavioral questions. In the coding rounds, I solved data structures and algorithms problems…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: Director-to-bar-raiser loopAmazon Kuiper Commercial Services · Software Engineer · HR Screen · Aug 2026
The process began with a recruiter and moved into a long loop with several people. After the recruiter screen, I spoke with an engineering director, then a senior product owner and a senior software engineer. Those rounds focused on fit and how I think through problems rather than gotchas. What stood out was the sequence of people. I then had a pairing stage with two bar raisers and finished with…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: DSA, GenAI, and bug findingAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Aug 2026
I began with resume shortlisting and then moved quickly to an OA. The assessment leaned heavily on DSA patterns, but it was not only about memorized tricks. It also touched broader topics such as GenAI and how it appears in projects. I remember questions involving arrays, stacks, and subsequence-style challenges. Afterward, I had a virtual screening that mixed finding bugs in code with LeetCode-s…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: leadership principles in the final roundAmazon Kuiper Commercial Services · Software Engineer · Aug 2026
The loop had four structured rounds: DSA first, then two lower-level-design rounds. One LLD discussion included gen-AI best practices, and leadership and behavioral questions appeared throughout the loop. The final behavioral and Leadership Principles round had the highest bar. I needed to tie responses closely to specific LP themes across questions and also be ready to explain LeetCode-medium so…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: online coding to face-to-face designAmazon Kuiper Commercial Services · Software Engineer · Online Assessment · Aug 2026
I began with an online coding test, followed immediately by HR-style questions after I submitted the result. From that recruiter and HR step, I moved into a face-to-face technical interview that mixed coding and system design. The technical stage had several coding questions alongside design topics, and I then finished with a manager round. It felt average in difficulty because I had to handle de…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: two 30-minute DSA questionsAmazon Kuiper Commercial Services · Software Engineer · Technical Screen · Aug 2026Rejected
I hit a heavy DSA gate early. I was given two DSA questions with 30 minutes for each one. The round moved quickly, and as soon as I reached the first problem, I realized I was not going to get through that stage. Beyond writing code, I was asked about the time complexity of my solutions and how I would optimize them. That made it difficult because a working solution was not enough. They also want…
- Amazon Kuiper Commercial Services Software Engineer Interview Experience: two DSA problems and embedded contextsAmazon Kuiper Commercial Services · Software Engineer · Aug 2026
My first step was a one-on-one virtual technical interview with an engineer. After a quick introduction, I solved two DSA problems on a shared coding platform and explained my approach, including time and space complexity, as I worked. I expected a straightforward phone screen, but the questions were tied to embedded and real-world software contexts. We also went through projects I had worked on,…
- Amazon Kuiper Commercial Services Software Engineer interview with two modesAmazon Kuiper Commercial Services · Software Engineer · Technical Screen · Aug 2026
I had back-to-back interviews with the hiring manager and then an engineer from the team. Both were 60 minutes and combined behavioral and technical evaluation. For the first 15 minutes of each conversation, the questions were behavioral. The rest shifted to DSA. I could not settle into just one mode because I had to switch quickly from explaining past choices to solving problems with standard al…
- Amazon Services Software Engineer Interview Experience: Calculator prompt without requirementsAmazon Services · Software Engineer · HR Screen · Aug 2026Rejected
The process was frustrating. In one early call, the hiring manager seemed to have reviewed my resume around the time of the interview. They asked roughly seven or eight questions, with follow-ups when an answer prompted more curiosity, but the process still felt uneven and ended with a quick rejection signal. Another stage was a video phone screen with Leadership-Principles behavioral questions a…
- Amazon Services Software Engineer Interview Experience: Leadership Principles and tradeoffs under uncertaintyAmazon Services · Software Engineer · HR Screen · Aug 2026
After a recruiter conversation, I moved into the main loop with several interviewers. The behavioral portion was closely tied to Amazon's Leadership Principles, and each interviewer focused on a different part of my background. Technical discussions mixed LeetCode-style coding with open-ended questions about how I made decisions when requirements or information were incomplete. The loop included…
- AWS Offer After Four Onsite RoundsAmazon · Software Engineer · New Grad · Onsite · Aug 2026Offer
Timeline: July 24: HR reached out on LinkedIn; I applied. July 31: OA. August 24: Survey. September 4: BOS onsite. September 10: Verbal offer. Four back-to-back onsite rounds. First round The interviewer asked two behavioral questions: one about doing something outside my area of responsibility, and one about helping a peer who was struggling. The coding question was similar to LeetCode 1152, but…
- Binary Swaps and a Django Post FixAmazon · Software Engineer · New Grad · Online Assessment · Aug 2026
I took the online assessment. It had two parts. DSA: minimum adjacent swaps for a binary array Given an array containing only 0s and 1s, rearrange it so that all 0s are at one end and all 1s are at the other. Either ordering was allowed: 000...111 or 111...000. In one move, I could swap two adjacent elements. I had to return the minimum number of moves required. For [0, 1, 0, 1], the answer was 1…
- Boomerang Loop With a Surprise ML Platform System DesignAmazon · Software Engineer · Onsite · Aug 2026Rejected
HR reached out about a boomerang interview, two rounds. Round 1: 20 minutes of behavioral questions, 30 minutes of coding. The questions weren't hard, but there were two of them. The first one gave me a graph and asked me to print the shortest path — not hard, but the messed up part was there was no problem description, I had to guess it myself, and there was also some distracting code mixed in t…
- BQ Plus Two Coding Questions in a Referral VOAmazon · Data Engineer · Technical Screen · Aug 2026
Last week's Amazon VO, done through a referral, was BQ plus two coding questions. First the BQ part: How do you handle it when you run into difficulties at work? When your team runs into difficulties, how do you encourage them and come up with a way to solve it? Why did you choose Amazon? Coding part: Coding 1: You're given a string array words. Each word can be written as the concatenation of th…
- Deep Leadership Follow-ups, SQL, and Data VisualizationAmazon · Business Intelligence Engineer · Technical Screen · Aug 2026Rejected
I am sharing the BIE phone interview that I just failed. I hope it can help everyone. A senior DE interviewed me and brought along a junior AE. Leadership BQ They first looked at my resume and asked about projects I had done and about leadership. The questions went very deep. After one A/B test, did I run any other tests? What kind of trade-off led to not launching? Which team did I work with? Wa…
- Four Interviews with a Train Fare Calculator and Sliding Window MaxAmazon · Software Engineer · Onsite · Aug 2026
Interview #1 — LP + DSA/OOP Leadership Principles behavioral interview, about 10–15 minutes. Then the design question: a train fare calculation system. There is one train line, G → U → H → K → I, and the fare between every two adjacent stations is 1 (for example, G to I costs 4). Implement calculateFare(start, stop) to compute the fare between two stations. Think about OOP/LLD design: where does…
- Leadership Principles and a Timestamp-Based LRU-Style ObjectAmazon · Software Engineer · Technical Screen · Aug 2026Rejected
A female PM and an SDE interviewed me. They began with Leadership Principles questions: Tell me about a time when you needed to take responsibility or ownership. Tell me about a time when you faced a challenge. These were standard Leadership Principles questions. The follow-ups were about AI and impact: how many people used what I built, what my manager's reaction was, and related points. Then I…
- Passing the SDE II Phone Screen After Leadership and Palindrome QuestionsAmazon · Software Engineer · Technical Screen · Aug 2026In progress
I interviewed for the Amazon SDE II position on August 29, 2026. The technical phone screen lasted about an hour. Interview Questions Behavioral: 3 behavioral questions The questions were primarily focused on Amazon Leadership Principles, especially Ownership and Dive Deep I would recommend preparing specific STAR-format examples from your past projects and being ready for follow-up questions. Co…
- Phone Screen, Virtual Onsite, and Bar RaiserAmazon · Frontend Engineer · New Grad · Onsite · Aug 2026In progress
Amazon 2026 New Grad Timeline and Interview Experience Role: Frontend Engineer, or perhaps Full Stack Engineer. During the interview, the hiring manager said there could be an opportunity to move toward full-stack work within the team later. I just finished interviewing for an Amazon Frontend Engineer role this week. I wanted to share the full process, the interview content, and the resources I u…
- Three Rounds, Rejected in Five Business DaysAmazon · SDE 1 · Onsite · Aug 2026Rejected
Amazon SDE 1 three-round interview experience: ultimately rejected. Round 1: Coding He first had me do a self-introduction, briefly going over my career plans, and then we moved into the coding part. Q: Design a file search API backend that supports recursive subdirectory search. There are a few edge cases to watch out for here. If the input directory is null or not a directory, the output should…
- Two Leadership Principles and Two Whiteboard ProblemsAmazon · Software Engineer · Technical Screen · Aug 2026In progress
Before the interview, the recruiter scheduled a call and said the interview would focus mainly on two Leadership Principles. The recruiter suggested preparing the related behavioral questions in advance using the STAR format. The first behavioral portion stayed mostly around those two Leadership Principles. After the first question, the interviewer dug further into the trade-off, so that discussi…
- A Segmented-Array OA Problem That Even ChatGPT Couldn't SolveAmazon · Software Engineer · Online Assessment · Jul 2026Rejected
I got Amazon's OA and started it one day right after waking up from a nap. I wasn't in a good state though, and I ended up getting a rejection. Question 1 Coding, 40 minutes. I wrote one version and only passed 4 cases — the other hidden cases threw some memory errors. It wasn't until after it ended that I realized there must have been a space constraint, which is why I was getting those memory-r…
- ADCI - Karnataka Customer Success Engineer interview: AI topics and approachable codingADCI - Karnataka · Customer Success Engineer · Technical Screen · Jul 2026
The interview felt easy and straightforward. Questions focused mostly on general behavioral and AI-related topics, and the coding did not feel overwhelming. For coding, I was asked to find duplicates and solve longest common prefix. The rest of the discussion was about how I thought and explained my reasoning, rather than difficult algorithm tricks. I did not receive an offer, but the experience…
- ADCI - Karnataka Network Engineer interview: technical, program-manager and Bar Raiser roundsADCI - Karnataka · Network Engineer · Technical Screen · Jul 2026
The process took about a week, close to five business days. It moved briskly from technical interviews through a program-manager conversation and a Bar Raiser round. I felt they were assessing more than one kind of ability. The technical rounds followed familiar Amazon interview patterns. The Bar Raiser made the assessment feel more calibrated, as though they were checking whether my leadership a…
- ADCI - Karnataka Software Engineer assessment: DSA and AI debuggingADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026
The online assessment was the main part of my process. It had four pieces: a medium-to-hard DSA problem, a work-simulation task involving a website bug that I had to solve with AI, and two behavioral sections. The simulation changed the feel of the assessment. It was not only about writing correct code. I had to work out what the system was doing and use AI as part of the debugging process. The b…
- ADCI - Karnataka Software Engineer Interview Experience: a Java, React, SQL, and DevOps assignmentADCI - Karnataka · Software Engineer · Take-home Project · Jul 2026Rejected
My path began with an assignment that mixed Java depth, React, some SQL, and a smaller DevOps component. It was substantial and felt designed to test end-to-end reasoning rather than isolated coding. The next step was a paper-based written problem-solving round. I was rejected there, and I felt circumstances played a part alongside technical ability. I had traveled a long way for the interview an…
- ADCI - Karnataka Software Engineer interview experience: assessment through virtual onsiteADCI - Karnataka · Software Engineer · Online Assessment · Jul 2026Offer
I started with an online assessment and then moved into a virtual onsite. The onsite mixed coding, system design, and behavioral questions, along with discussion of my past experience and projects. Each round had a clear purpose even where the topics overlapped. Coding required the most active problem-solving. In system design, I had to explain tradeoffs and work through how I would tackle a larg…
- ADCI - Karnataka Software Engineer Interview Experience: easy-to-medium coding with intense LP drillingADCI - Karnataka · Software Engineer · Technical Screen · Jul 2026
The interview began with LeetCode-style problems that were easy to medium, then became more intense through Leadership Principle drilling. About half the time went to LP follow-ups, while the other half went to coding-style questions in the usual LeetCode rhythm. That pattern repeated across two rounds. I was not answering leadership questions once and moving on. I had to explain how I would thin…
