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

  • ADCI - Karnataka Software Engineer Interview Experience: DSA, LLD, GenAI, and leadership principlesADCI - Karnataka · Software Engineer · Technical Screen · Aug 2026

    I had four rounds that stayed consistent from start to finish: a DSA-focused round, two LLD rounds, and a final leadership-principles and behavioral round. Leadership-principles questions also appeared throughout the technical discussions. One LLD round covered GenAI best practices, while the remaining LLD discussion focused on design tradeoffs. Across the process, the interviewers cared more abo…

  • ADCI - Karnataka Software Engineer Interview Experience: easy DSA and RAG project discussionADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026

    After I applied, I moved to an online assessment and then a technical interview. The assessment covered DSA and aptitude. In the live round, I solved easy DSA-style questions before the discussion shifted to my resume, especially a project where I had used a RAG model. The interview felt straightforward. I explained what I had built and how I approached it, and the DSA portion was more manageable…

  • The experience felt dated and generic. I went through technical rounds on systems and databases, along with the usual LeetCode-style questions available online. The behavioral rounds used stressful prompts to evaluate my social skills. It never felt tailored, and by the end it was not engaging enough to match the effort I had put in. I ended without an offer. What stayed with me was how standard…

  • ADCI - Karnataka Software Engineer Interview Experience: Fifty-minute DSA and behavioral roundADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026
    Rejected

    I started with an assessment and then moved to a first technical round, but failed after that. The round included a DSA question, a behavioral question, and a situational prompt. The whole interview lasted around fifty minutes. It was compact, with different types of questions coming back to back in a short window. The process was not long, but it clearly tested both coding fundamentals and how I…

  • My process had three rounds, and getting past the first one depended on solving both DSA questions. The second round had no clear right answer. They wanted to see whether I could follow the prompt and explain my reasoning. The third round was managerial. That structure made the stakes clear from the beginning. I could not treat the first round as a warm-up. The manager round shifted toward leader…

  • ADCI - Karnataka Software Engineer Interview Experience: GenAI coding to DSA and system designADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026
    Rejected

    My process began with an OA that included a hard LeetCode-style problem. The second round was a GenAI-related coding interview. After that came a technical screen with a high-level medium LeetCode question and leadership principles. The final loop was more DSA-heavy. It had three DSA questions followed by a system design round, so the last stage tested both algorithmic work and design thinking. I…

  • ADCI - Karnataka Software Engineer Interview Experience: graduate OA with a short first challengeADCI - Karnataka · Software Engineer · New Grad · Online Assessment · Aug 2026

    I was invited to an online assessment for graduates. What stood out was the time limit for the first programming challenge. The window to solve it felt absurdly short, so a large share of the time went to reading and understanding the prompt. The second test felt more reasonable by comparison. The content itself was not described as impossible, but the timing made the round stressful. I spent mos…

  • After I was shortlisted from an online assessment, I was called for an interview that felt friendly and focused on solving. The interviewer gave me two medium-level DSA problems, one on graphs and one involving a monotonic stack. I was comfortable enough to talk through my approach while working, and the problems covered a useful mix of techniques rather than one narrow topic. I did not get an of…

  • ADCI - Karnataka Software Engineer Interview Experience: hard DSA after the online assessmentADCI - Karnataka · Software Engineer · HR Screen · Aug 2026

    The process started normally: I applied, a recruiter reached out for a brief HR-style introduction, and then I took a one-hour online assessment. The later rounds included two DSA coding interviews, one system-design interview, one behavioral or leadership-style question they called BQ, and several team-matching rounds. The DSA portion was much harder than I expected. The problems felt close to L…

  • ADCI - Karnataka Software Engineer Interview Experience: House Robber and leadership principlesADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026

    I started through an on-campus opportunity with an OA that mixed fundamentals and personality fit. It included two DSA questions and behavioral questions, followed by two interview rounds. The first interview began with a project discussion and moved to one low-level design question. The second was more coding-heavy: two DSA problems, House Robber 1 and House Robber 3, followed by questions tied…

  • My interviews involved several screening and loop conversations before the full evaluation. I began with a hiring-manager screening call, then spoke with an engineering director, a senior product owner, a senior software engineer, and a pair of Bar Raisers before a final hiring-manager round. The sequence was structured and layered. It was difficult overall, but each conversation seemed intended…

  • My loop mixed technical work and design in a consistent flow. I had two technical rounds, then a system-design round, followed by a one-on-one conversation with a manager. The technical rounds were LeetCode-style problem solving. The system-design round was about designing large-scale systems and how I would structure the approach, rather than any one algorithm. The manager conversation stayed fo…

  • ADCI - Karnataka Software Engineer Interview Experience: metrics monitoring designADCI - Karnataka · Software Engineer · HR Screen · Aug 2026
    Offer

    After the recruiter screen, the rest of my loop took almost a month, which felt longer than I expected. After the initial phone conversation, I had two technical interviews centered on data structures and algorithms. One covered merging overlapping intervals, and the other asked for the minimum number of meeting rooms. The final interview was system design. I had to design a scalable metrics moni…

  • ADCI - Karnataka Software Engineer Interview Experience: OA timing disrupted performanceADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026
    Rejected

    I started with an online coding test and received an HR set of questions soon after submitting it. Then I had a face-to-face technical round that mixed coding and system design. That technical part included three coding questions and system-design discussion, followed by a manager round. The assessment phase threw me off more than the later stages. The OA questions did not seem impossible, but th…

  • Rejected

    The interview was essentially one round, and I did not get past it. It was unpleasant in the moment, and the feedback suggested that the decision was made quickly. The questions were specific. I realized I should have prepared more deeply for VIM because they asked me many questions about it and I did not handle that line of questioning well. The interviewer presented the process as fair, but I c…

  • ADCI - Karnataka Software Engineer Interview Experience: onsite coding and Bar Raiser gapADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026

    I began with a straightforward OA and then moved to onsite interviews. The coding rounds were easier than I expected, with LeetCode medium or medium-hard style problems. The Bar Raiser round was different. It felt more complicated and demanded much more preparation than the coding rounds. I could not turn my onsite coding performance into enough strength in the Bar Raiser evaluation. I did not re…

  • ADCI - Karnataka Software Engineer Interview Experience: Probability, estimation, and confidenceADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026
    Offer

    The process was heavily driven by an OA across three rounds, ranging from easy to medium. Then came an interview step that reviewed the code I had written in the OA, almost like a code-review session, for about 45 minutes. It felt very easy compared with typical interview loops. The questions leaned heavily on probability and statistics estimation. I had to solve them quickly, in roughly 30 minut…

  • After the recruiter started arranging a phone interview, the company went quiet. The recruiter said they would set up the next step, but it never happened. The difficulty was described as very difficult, although the larger issue was not the technical bar. It was the lack of professional follow-through. I never reached a meaningful later stage because the process did not continue. I was not selec…

  • My process started with an online assessment that I completed in about three days. The HR contact asked when I could finish it, so timing mattered from the start. After that, I had a phone screen with behavioral questions and LeetCode. A couple of days later, I had the virtual onsite. It included more LeetCode, OOD, and system design. When I reported the experience, I had just completed the phone…

  • ADCI - Karnataka Software Engineer Interview Experience: rain fill, LRU, and delivery-service designADCI - Karnataka · Software Engineer · Technical Screen · Aug 2026
    Offer

    My interview focused on a couple of familiar technical questions. One was a straightforward "fill rain" problem. The design portion came afterward. One prompt felt close to an LRU cache, and the higher-level task was to design a delivery service similar to Uber or DoorDash. The conversation was practical. I reasoned through the core logic first, then moved into system-level thinking for the desig…

  • The experience was positive. The interviewers were genuinely nice, and the technical portion felt manageable because I had practiced the areas they emphasized, especially leadership principles. The recruiter gave me an interview prep package. Reading it and preparing strong examples mattered a great deal, and the interview did not try to catch me off guard. I received an offer. I connected the ou…

  • The questions themselves were mostly normal interview questions. What wore me down was the process: my interviews were rescheduled three times, and the changing schedule was stressful. Even with that disruption, the content was not out of line. I got LeetCode-medium-level coding questions and behavioral questions, with nothing especially novel or unfair for an SDE role. I did not get the offer. T…

  • ADCI - Karnataka Software Engineer Interview Experience: rescheduled campus loopADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026

    This started as an on-campus opportunity. The online assessment had two DSA questions and behavioral questions. After that, I had two interview rounds. The first was a project discussion plus an LLD question. The second had two DSA questions and leadership-principles questions. The questions themselves sounded fairly standard, but my interviews were rescheduled several times. That made the loop f…

  • My first assessment round involved difficult coding with limited time. I remember occasional helpful hints, but it was still very hard to finish under the clock. The questions grew harder as the round went on, which made the final part the most stressful. I was also frustrated that there was not more real-time guidance from an interviewer while I worked. I did not complete the full coding portion…

  • I went through technical rounds on systems and database knowledge, along with the usual LeetCode problems you see online. There were also behavioral rounds with stressful questions meant to evaluate social and communication skills. It felt boring and outdated to me, and I did not get an offer. I was disappointed by more than the outcome. The process did not bring anything new even though I had pu…

  • I went through a three-round structure with clear time blocks: a recruiter screen, a one-hour technical screen, and a final loop made up of five interviews. The technical screen was tightly scheduled. It began with a short introduction, moved into behavioral questions, then a dedicated coding segment, and finished with a brief period for my questions. I did not receive an offer. What I remember m…

  • ADCI - Karnataka Software Engineer Interview Experience: two 60 minute in person roundsADCI - Karnataka · Software Engineer · HR Screen · Aug 2026

    I started with HR questions soon after applying, then moved into tightly scheduled in person sessions. The loop had two back to back rounds: one with a hiring manager and one with an engineer. Each lasted about 60 minutes. The first 15 minutes of each were behavioral, and the remaining time was for DSA. The DSA portion carried the usual expectation to explain my thinking clearly. The format place…

  • ADCI - Karnataka Software Engineer Interview Experience: Two coding questions per roundADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026

    I started with an online assessment containing two coding questions. Within a few days I was selected for the next round, a computer-fundamentals MCQ with about nine sections. After clearing it, I received an interview invitation for two technical rounds. Each technical round had two questions. The topics ranged from basic math to graphs, trees, and HashMap-related problems. The format was very f…

  • I think my loop followed a classic coding-and-design structure, but the outcome went against me. I went through an assessment and several later stages. By the final onsite setup, it felt as though I was competing against other interviewers' question sets. At the onsite stage, I had the impression that some candidates got standard LeetCode questions while others got harder, less familiar variants.…

  • ADCI - Karnataka Software Engineer Interview Experience: Virtual DSA OA and timed Zoom roundADCI - Karnataka · Software Engineer · Online Assessment · Aug 2026

    I was invited to a virtual OA with multiple DSA problems that went from easy to harder at the end. After that, the process had two timed parts: a Zoom session with a LeetCode-medium block followed by behavioral questions. The coding portion lasted about 30 minutes, and the behavioral portion took another 30. The behavioral questions were a real shift in pace immediately after the technical sectio…