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 Software Engineer interview with coding, aptitude, technical, and fit stagesAmazon · Software Engineer · Online Assessment · Jul 2026

    My process began with an online assessment that combined coding and aptitude questions. After I cleared it, I had one or two technical interviews on data structures, algorithms, object-oriented programming, and general problem solving. The final round shifted to fit, with behavioral questions about communication, teamwork, and overall alignment. The experience was challenging because I was evalua…

  • The interview process felt intentionally intense and streamlined, but still brutal. It mixed behavioral and technical questions with artificial time pressure, like being given something massive to complete in about an hour as a deliberate stress test. It seemed designed to see whether I would break under constraints, and it matched what I had heard about high-attrition hiring models at companies…

  • The online assessment felt more demanding than a coding-only test. Along with two medium-to-hard DSA questions, it had an AI project-debug section and a working-style questionnaire. The follow-up sequence had three rounds on DSA, high-level design, and low-level design. The overall difficulty felt difficult. The tightly packed assessment and later rounds made the design portions feel especially h…

  • Amazon Software Engineer interview: assessment and waitlistAmazon · Software Engineer · Online Assessment · Jul 2026

    I took an online assessment with two DSA questions and multiple-choice scenarios about leadership qualities. After being shortlisted, I completed an online technical round with two DSA problems. Leadership was already part of the assessment rather than a separate afterthought, while the technical work felt straightforward by comparison. I was waitlisted rather than offered, so the result felt mix…

  • My process started with an online assessment, then a loop of about three back-to-back interviews. It felt difficult. After the assessment, I had a fully behavioral session with a bar-raiser-style focus. The next two interviews were technical. One leaned on classic DSA, and the other moved toward lower-level system design. Each had a walk-me-through-your-reasoning feel: reaching the right answer w…

  • I had three coding rounds with LeetCode-style medium problems, then a system-design round and a cultural-fit conversation. The interviewers were friendly and the environment was pleasant, which made the pressure easier to manage. Still, the process felt dated to me. LeetCode practice carried much of the load, and cultural fit was treated as a single conversation rather than something developed th…

  • Amazon Software Engineer interview: coding, repository debugging and two design questionsAmazon · Software Engineer · Online Assessment · Jul 2026

    My online assessment combined coding with questions about how I work. It included classic coding problems and AI-assisted project or debugging prompts where I traced issues through a realistic repository. There was also a leadership or fit component and a substantial system-design element. By then, I could see the assessment covered much more than standard LeetCode questions. Next came a recruite…

  • I entered a four-round process but did not clear the first round. It included one standard DSA question and one AI-assisted, repo-based coding task. I could produce a DSA solution, but edge cases, debugging, and time ran away from me. The repo task did not go well enough either, and I could feel the momentum slipping during the round. It did not strike me as unfair. I simply did not meet the bar…

  • Amazon Software Engineer interview: four friendly interviews over two daysAmazon · Software Engineer · Technical Screen · Jul 2026

    I completed four friendly Amazon interviews, each about an hour, over two days. The questions covered system design, LeetCode-style coding, behavioral topics, and my use of AI. The loop was long but not especially difficult. Because the tone stayed approachable, I could focus on explaining my thought process instead of only racing to write code. I left with a clearer sense of the balance they wan…

  • Amazon Software Engineer interview: four in-person behavioral and technical roundsAmazon · Software Engineer · Online Assessment · Jul 2026

    After finishing my online assessment, I heard back roughly a month later and moved into four in-person rounds. The process felt smooth, and everyone I met was professional and friendly. A lunch break in the middle helped me between interviews. One round was purely behavioral, while the others combined behavioral and technical components. The behavioral prompts were more situational than I expecte…

  • Amazon Software Engineer interview: four-interview loop and leadership principlesAmazon · Software Engineer · Online Assessment · Jul 2026
    Offer

    I took an online assessment and, about a week later, had four interviews in a single day. The recruiter stayed responsive throughout, which helped me understand what each round would look like. The onsite loop ran back to back and followed the Amazon loop format closely. I had coding-and-judgment moments mixed with Leadership Principles. One round was more team or hiring-manager focused, while an…

  • I went through a four-round loop spread across two onsite rounds. Each interview mixed behavioral questions with a technical segment, except for one that was behavioral-only. The technical topics included strings, priority queues, and object-oriented design. A bar-raiser-style round was part of the loop and felt notably harder than the others. Even with the mix of topics, the structure was consis…

  • Amazon Software Engineer interview: HackerRank OA and pending updateAmazon · Software Engineer · Online Assessment · Jul 2026
    In progress

    After applying, I took an Amazon online assessment on HackerRank. The DSA section was heavy on prefixes and patterns, with a problem that felt like something in the longest-happy-prefix family. The next part involved debugging code. I did well there, so the overall assessment felt manageable even though the DSA question itself was a grind. When I checked my DSA performance, the test coverage did…

  • Amazon Software Engineer interview: HackerRank, AI assistance and a next-day rejectionAmazon · Software Engineer · Online Assessment · Jul 2026

    I first took a HackerRank take-home exam and did not solve everything perfectly, which worried me early. The next step involved AI assistance, but the tool felt almost intentionally unhelpful. It did not seem to move me toward the answer even though I was supposed to be able to use it. I still advanced to an interview with LeetCode-style questions and discussion of my experience. The pace was qui…

  • Amazon's loop was four to five back-to-back interviews, roughly 45 to 60 minutes each. The panel included a potential hiring manager, one or two team members, a senior leader, and a bar raiser. The pace was relentless because I had to stay sharp across several perspectives. Leadership Principles were spread across the panel. Each interviewer owned a couple, and together they covered all of them.…

  • Amazon Software Engineer interview: LeetCode and leadership pressureAmazon · Software Engineer · Technical Screen · Jul 2026

    My first interview was about an hour and had two easy LeetCode-style questions. The final stage was tougher: two separate LeetCode sessions, a system-design session, and an LLD session. Leadership Principle prompts came up in every session, so it was never only about getting a solution. The technical questions were easy to medium overall, but the leadership questions were harder for me. I also lo…

  • I began with two practical programming questions that felt more like testing how I translate an idea into working code than trick problems. The first was straightforward math. The second was interactive: I had to work out what the interviewer wanted and implement several functions to reach the final behavior. The second question made the process difficult because it required more back-and-forth t…

  • Amazon Software Engineer interview: monitored OAs and three-engineer panel codingAmazon · Software Engineer · Online Assessment · Jul 2026
    Offer

    My first interaction was a phone screen, a precursor to a heavier assessment. I completed several webcam-monitored online assessments on coding, bug catching, and behavioral decision-making for culture fit. After clearing them, I had a panel interview with three engineers, taking turns one by one. Each interview had coding and behavioral parts, with segments of roughly 45 to 60 minutes. The OA in…

  • Amazon Software Engineer interview: organized coding and leadershipAmazon · Software Engineer · Online Assessment · Jul 2026

    I began with an online coding assessment on data structures, algorithms, and problem solving. After passing it, later interviews combined coding, design fundamentals, and Leadership Principles. Follow-up questions tested my thought process rather than only whether I reached a solution. Leadership discussion was woven into the technical evaluation, so it felt broader than a coding test. I did not…

  • Amazon Software Engineer interview: pressured DSA and leadership-principles loopAmazon · Software Engineer · Online Assessment · Jul 2026

    After the initial online assessment, I entered several technical interviews with a consistent structure: coding first, then strong pressure to connect my answers to Amazon Leadership Principles. The most intense round combined leadership-aligned evaluation with multiple DSA problems, turning it into a test of time and completeness rather than one neat solution. I also had a couple of medium codin…

  • I had a 30-minute recruiter phone screen about my background and resume. About a week later, I had an approximately one-hour technical video interview with a senior engineer. After introductions, I completed a live coding challenge in a shared editor. The round ended with system-design basics and questions about how my past projects worked in practice. It was average in difficulty: nothing entire…

  • Amazon Software Engineer interview: sliding window and a debugging leadership storyAmazon · Software Engineer · Technical Screen · Jul 2026

    I had a phone round with two focused prompts. One was a medium sliding-window problem, and I had to explain how I would approach it. The other was about leadership: describe a time I debugged an error, including the issue, how I researched and debugged it, and what I put in place to prevent it from recurring. It felt difficult because it paired a concrete algorithm with a detailed accountability…

  • The process started with a behavioral interview with a team manager, followed by several technical rounds. The overall difficulty felt average, and nothing about the flow seemed chaotic. The questions kept returning to my experience with hardware and operationalizing space systems. Rather than staying only at an algorithm level, the technical discussions asked how I had handled real operational c…

  • Amazon Software Engineer interview: streaming-system design in a four-round loopAmazon · Software Engineer · Technical Screen · Jul 2026

    My interview journey was straightforward in how the rounds were organized. After the early steps, I entered a loop with four interviews, each about an hour. It began with a system-design conversation, and later rounds included manager-style discussion plus bar-raiser and behavioral evaluation. The design prompt was to build a streaming application like Netflix or Amazon Prime Video, so the discus…

  • Amazon Software Engineer interview: technical and leadership roundsAmazon · Software Engineer · Other · Jul 2026

    My process had multiple technical rounds and a couple of structured behavioral rounds. One technical conversation mixed troubleshooting with leadership themes such as Bias for Action and GenAI fluency, so it was not solely about writing code. Another technical round focused more directly on coding problems. The hiring-manager round covered leadership principles including Earn Trust, Learn and Be…

  • Amazon Software Engineer interview: technical assessment and team roundsAmazon · Software Engineer · Online Assessment · Jul 2026
    Offer

    I applied online, completed a technical assessment, and then had a couple of interviews with people from the team I would work with. The process was simple and team aligned rather than chaotic. It had multiple rounds but did not feel like a prolonged gauntlet. The difficulty was easy, and it felt more like a check of fit and baseline skills than a difficult hiring process. Location: South Africa.…

  • Amazon Software Engineer interview: Top-K variation and a restaurant-manager problemAmazon · Software Engineer · Online Assessment · Jul 2026

    After an online assessment, I went through back-to-back interviews covering DSA, low-level and higher-level design, Leadership Principles, and a final bar raiser. There were a few unusual details. One round asked an AI-usage-style question. Another began with a hiring-manager version of a Top-K problem without API help. A technical prompt used a restaurant manager handling arriving groups, so I h…

  • Amazon Software Engineer interview: Two Sum and substring offerAmazon · Software Engineer · Online Assessment · Jul 2026
    Offer

    I received an OA with two DSA questions and behavioral questions. I then had one interview with two more DSA questions at easy to easy-medium difficulty: Two Sum and longest substring without repeating characters. The interview followed the same basic DSA pattern as the assessment, and the two questions were the kind of fundamentals I could work through directly. The process moved quickly and fel…

  • Amazon Software Engineer virtual onsite interview experienceAmazon · Software Engineer · Online Assessment · Jul 2026

    My process began with a recruiter screen, then moved quickly through an online coding assessment and a technical phone interview. The questions were practical but time-constrained, which made it harder to slow down and check every edge case. The final stage was a virtual onsite loop with multiple interviews. I had data-structures-heavy questions, system design, and a debugging-focused segment. Am…

  • Amazon Technical Program Manager interview: scheduling fell apartAmazon · Technical Program Manager · HR Screen · Jul 2026
    Rejected

    The process began smoothly but ended inconsistently. I had a recruiter phone screen to check cultural fit and whether the role matched my background. The planned next step was a loop of four or five interviewers using cases connected to Amazon Leadership Principles. In practice, communication was where it broke down. After recruiter contact, I did not hear about scheduling for some time and event…