Katkat

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 Development Center U.S. Software Engineer Interview Experience: debugging under time pressureAmazon Development Center U.S. · Software Engineer · Online Assessment · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview experience: grid paths and RAGAmazon Development Center U.S. · Software Engineer · Intern · Online Assessment · Jul 2026
    Rejected

    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…

  • Amazon Development Center U.S. Software Engineer Interview Experience: Queue with two stacksAmazon Development Center U.S. · Software Engineer · Online Assessment · Jul 2026

    After applying, I completed an online assessment with two algorithm-focused problems. One was a sliding-window task and the other involved binary search. It felt less like vague theory and more like recognizing the right pattern and implementing it within the time limit. After passing, I moved to coding-first stages. In one round, I implemented a queue using two stacks, working through the mechan…

  • 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…

  • Amazon Development Center U.S. Software Engineer interview: a structured coding and design loopAmazon Development Center U.S. · Software Engineer · Online Assessment · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview: compact linked-list screenAmazon Development Center U.S. · Software Engineer · Technical Screen · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview: consecutive loop with bar raiserAmazon Development Center U.S. · Software Engineer · Online Assessment · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview: design then manager roundsAmazon Development Center U.S. · Software Engineer · Technical Screen · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview: leadership and hard DSAAmazon Development Center U.S. · Software Engineer · Technical Screen · Jul 2026

    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…

  • 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…

  • Amazon Development Center U.S. Software Engineer interview: resilience under pressureAmazon Development Center U.S. · Software Engineer · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview: SDE Intern assessment mixAmazon Development Center U.S. · Software Engineer · Intern · Online Assessment · Jul 2026

    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…

  • Amazon Development Center U.S. Software Engineer interview: timed first stageAmazon Development Center U.S. · Software Engineer · Online Assessment · Jul 2026
    Rejected

    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…

  • Amazon DSP Software Engineer interviewAmazon DSP · Software Engineer · Online Assessment · Jul 2026

    The process started with an online assessment containing two coding problems and multiple test cases. I passed some cases right away and did better on the second problem. Then I had two coding rounds: graphs and arrays in one, linked lists and binary search trees in the other. There was also a behavioral section on situations and workplace fit, spread across multiple rounds over a couple of days.…

  • Amazon DSP Software Engineer Interview Experience: coding question followed by web debuggingAmazon DSP · Software Engineer · Technical Screen · Jul 2026

    I expected an ordinary LeetCode-style technical session. It opened with a medium problem, then changed into a web-app debugging exercise. The available AI assistant could inspect project files and describe what parts did, but it could not give me the solution. That made the interview more about diagnosis than implementation. I had to interpret the codebase, use the assistant to understand its mov…

  • The loop had no bar raiser, which made it look simpler on paper. Most rounds were DSA with a smaller set of low-level, product-style questions. The OA involved simulation-like grouping and sorting. In the live rounds, I found a median in an integer stream and identified the K most frequent elements in a stream. The low-level portion included implementing a sliding-window rate limiter. It felt str…

  • I had an intense take-home stage. A home test split time between a HackerRank/LeetCode-style coding problem and a separate debugging task in what looked like a full-stack repository. In the debugging portion, an API call behaved unexpectedly. I had to find the bug and make every test pass, where small mismatches could break the result. The coding prompt was also time-boxed and seemed designed to…

  • Amazon DSP Software Engineer interview experience: leadership principles across roundsAmazon DSP · Software Engineer · Technical Screen · Jul 2026

    Leadership principles became the center of my loop, even though coding was still part of it. I went in expecting generally easy-to-medium LeetCode-style questions, but the interviewers pressed much harder on leadership-principle stories than I expected. Across several rounds, there was a block of leadership-principle drilling followed by coding questions in that same LeetCode vein. The behavioral…

  • Amazon DSP Software Engineer interview experience: OA, fundamentals, and behavioral fitAmazon DSP · Software Engineer · Online Assessment · Jul 2026

    I started with an online assessment that mixed coding and aptitude questions. After I cleared it, I was invited to one or two technical interviews on fundamentals: data structures, algorithms, object-oriented programming, and broader problem solving. The final step included behavioral questions about communication, teamwork, and fit for a software development engineer track that had an intern-lik…

  • Amazon DSP Software Engineer Interview Experience: Patient queue-with-two-stacks discussionAmazon DSP · Software Engineer · Online Assessment · Jul 2026

    My process began with an OA containing algorithm practice. One problem was a relatively approachable sliding-window task, and the other involved binary search. I then had a live technical interview where I implemented a queue using two stacks. The questions were technical and the session was back to back, but the interviewers were patient. They listened while I fully explained my reasoning instea…

  • Amazon DSP Software Engineer interview: coding, design, and behavioral sequenceAmazon DSP · Software Engineer · Online Assessment · Jul 2026

    After recruiter screening, I completed a take-home LeetCode-style assessment, a live coding interview, a system design segment with two design questions, and a behavioral discussion about communication and collaboration. Coding came first in the live stages, while behavioral evaluation was a structured test of fit. The process also looked at work style and how I explained my thinking, not just wh…

  • This was a four-round process, but I did not pass the first round. It paired a classic DSA problem with an AI-assisted coding task in a repo-style setup. I could write a DSA solution, then got caught on edge cases without enough time to debug it properly. The repo task also felt like a race against the clock. I tried to adapt, but timing pressure and the need to be precise worked against me. I di…

  • Amazon DSP Software Engineer interview: DSA screens and lost confidenceAmazon DSP · Software Engineer · Technical Screen · Jul 2026
    Rejected

    I started with a recruiter and then had a technical screen focused on problem solving and communication. I was asked several DSA-style questions, and the interviewer cared about how I handled them as much as whether I reached an answer. I solved only a couple, while the rest did not click, so the session felt difficult and lengthy. In a separate, lighter coding-focused screen with more recognizab…

  • Amazon DSP Software Engineer interview: DSA-heavy assessmentAmazon DSP · Software Engineer · Online Assessment · Jul 2026
    Offer

    I applied, completed a technical assessment, and then interviewed with several team members. The OA included two DSA-style questions and a behavioral or work-style component. I remember Two Sum and a longest-substring-without-repeating-characters question. The later technical interviews used similar easy-to-medium DSA questions. I made it through the process and was selected and accepted. Even so…

  • I started with an online assessment containing coding challenges and a work-style simulation tied to Amazon Leadership Principles. After a recruiter-style prelude, I had a full loop of four back-to-back hour-long conversations with engineers, a senior leader, and a Bar Raiser. Different interviewers appeared to be assessing different principles, so behavioral evaluation was part of the whole day.…

  • Amazon DSP Software Engineer interview: GenAI and debuggingAmazon DSP · Software Engineer · Other · Jul 2026

    The loop put GenAI alongside the usual Amazon evaluation. One troubleshooting conversation was framed around leadership principles such as Bias for Action, and another tested my GenAI fluency. A separate round went back to traditional coding, where I had to show a structured approach while tying my answers to leadership principles. One technical portion was not a simple blank-page coding exercise…

  • Amazon DSP Software Engineer interview: ML, CS, and HR breadthAmazon DSP · Software Engineer · Online Assessment · Jul 2026

    I went through two rounds. The first was a technical assessment, followed by an HR round. The technical questions were mid-to-difficult and covered ML concepts as well as computer-science fundamentals, so it was not just DSA trivia. HR reviewed my resume and asked HR questions. That made the process feel like an attempt to connect my background and projects to how I would work day to day. The int…

  • Amazon DSP Software Engineer interview: OA and three closely grouped interviewsAmazon DSP · Software Engineer · Online Assessment · Jul 2026

    The process became a tight loop of back-to-back interviews, and I could feel the expectation that I keep pace. I started with an online assessment and then moved directly into three interviews that were scheduled close together. One interview was entirely behavioral, while the other two were technical. The technical questions covered core DSA and moved into low-level and design-related territory.…

  • Amazon DSP Software Engineer interview: one HackerRank-to-linked-list roundAmazon DSP · Software Engineer · Online Assessment · Jul 2026
    Rejected

    After clearing an online HackerRank coding round, I had a single one-hour technical interview with one senior software engineer. They asked one linked-list question. The conversation was straightforward, and I felt reasonably prepared, but I was rejected after that round. It was not chaotic or unfair, just unusually compact. My takeaway was that a smooth process and an in-bounds question still le…

  • The loop felt brutally hard and unusually streamlined, as though speed and pressure mattered more than comfort. It mixed behavioral and technical questions, but artificial time pressure dominated the experience. The setup was a deliberate stress test. There was an hour-like constraint for a large project, and it felt as though the goal was to see whether I would break under that pressure. The pro…