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
- Software Engineer interview at ADCI - Karnataka: DSA and Leadership PrinciplesADCI - Karnataka · Software Engineer · Jul 2026Offer
I had one direct interview round with two LeetCode-based DSA questions. One was an array problem in the style of classic book allocation; the other combined math and arrays. I needed to show sound fundamentals and a clear implementation. Amazon Leadership Principles were not an afterthought. They were woven into how I explained decisions, tradeoffs, and reasoning. The conversation was technical,…
- Software Engineer interview at ADCI - Karnataka: networking depthADCI - Karnataka · Software Engineer · Jul 2026
A phone screen began with my ongoing work and projects, but every answer led to deeper follow-up. I used STAR-style stories to keep the conversation structured as the interviewer drilled into my experience. The technical part covered TCP/IP and routing topics including OSPF and BGP. The interview assessed both how I described impact and ownership and whether I could reason through practical netwo…
- Software Engineer interview at Amazon AdvertisingAmazon Advertising · Software Engineer · Jul 2026Rejected
This four-round loop was about DSA execution and being thorough with edge cases. Early on, I saw ordinary algorithm questions alongside an AI-assisted, repo-based coding task. I could usually find the central DSA idea, but I did not get all the edge cases right or leave enough time to debug. The later rounds kept the same theme, with coding problems at different levels and behavioral moments mixe…
- Software Engineer interview at Amazon Advertising: interview experienceAmazon Advertising · Software Engineer · Jul 2026
The process had three stages and placed Amazon leadership principles alongside coding. I did not complete the first stage. It began with two coding questions under set time limits and then moved to a workstyle assessment. The later format, as I understood it from the process, involved one or two technical rounds with DSA-heavy problems and leadership-principle prompts throughout. In my own DSA-fo…
- Software Engineer interview at Amazon Advertising: Leadership PrinciplesAmazon Advertising · Software Engineer · Jul 2026
The process covered several technical levels, bar-raiser-style evaluation, and a program-manager round. Expectations were communicated clearly, and Amazon Leadership Principles were central even during technical discussions, where impact and ownership still mattered. The full process took nearly a week in business-day terms. I did not receive an offer, but the structure stayed consistent enough t…
- Software Engineer interview at Amazon Development Center U.S.: interview experienceAmazon Development Center U.S. · Software Engineer · Jul 2026
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…
- Software Engineer interview at Amazon DSP: four DSA roundsAmazon DSP · Software Engineer · Jul 2026
I went through four rounds that mixed DSA and behavioral evaluation. The first included two medium-hard questions with DP and graph themes, plus project discussion. The second had two easier-medium DP and string questions with more behavioral material. The third included one easy sliding-window-style problem. Although I felt some answers were reasonable, I did not make it past the earlier cutoff.…
- Software Engineer interview at Amazon DSP: interview experienceAmazon DSP · Software Engineer · Jul 2026
I had four interview rounds, each about an hour long, with people from different countries. The sessions were respectful and organized, mixing technical material with behavioral evaluation. Amazon Leadership Principles were central, and I needed concrete examples rather than general statements. The loop included several DSA-focused rounds with leadership-principle questions throughout. There was…
- Software Engineer interview at Amazon DSP: principle-driven loopAmazon DSP · Software Engineer · Jul 2026
My interview flow started with a recruiter screen, then an online assessment and technical interviews. Coding and behavioral evaluation were tied closely to Amazon Leadership Principles, particularly how I described ownership, impact, and decisions. GenAI concepts also appeared. The process was organized and serious, but I did not receive an offer. I understood the material, yet I could not turn…
- Software Engineer interview at Amazon: leadership narrative challengeAmazon · Software Engineer · Jul 2026
My three-round loop had two DSA rounds and a Leadership Principles round. The first DSA round included two medium LeetCode questions. The second had one medium and one hard question involving DP and graphs. The Leadership Principles interview was harder for me than DSA because it required a convincing narrative about how I would operate under Amazon's values. I did not receive an offer. The proce…
- Software Engineer interview at Amazon: networking follow-upsAmazon · Software Engineer · Jul 2026
A phone screen began with my current experience and projects, then each response drew deeper questions. I used STAR structure for behavioral answers as the interviewer pressed past surface-level descriptions. Technical discussion covered TCP/IP and routing topics, including OSPF and BGP. It was an engaging but difficult conversation because of the depth expected in both storytelling and networkin…
- Software Engineer interview at Prime Video: three coding roundsPrime Video · Software Engineer · Jul 2026
The process was predictable: three medium LeetCode coding rounds, then system design and a cultural-fit conversation. The interviewers were pleasant, and the atmosphere did not feel adversarial. Still, I saw the format as dated. I kept questioning the use of LeetCode tasks as a proxy for real engineering ability and whether the culture-fit conversation added something meaningful to the coding sig…
- Solutions Architect interview at Amazon Web Services: withdrew after technical roundAmazon Web Services · Solutions Architect · Jul 2026Withdrew
I entered through a referral and passed an initial assessment. That led to a recruiter phone screen and then a technical interview, so the process moved forward quickly once I cleared the test. I withdrew after the technical round and did not experience the full multi-round loop. The early funnel felt normal: assessment, recruiter call, then technical screen. Since I chose to step away, I cannot…
- ADCI - Karnataka Network Engineer Interview Experience: online tasks and video promptsADCI - Karnataka · Network Engineer · Online Assessment · Jun 2026
This did not feel like a normal series of recruiter calls and technical interviews. I applied online, and the later steps were mainly online tasks: watching videos, answering questions, and completing work prompts rather than participating in live interviews. I was surprised by how little in person style interviewing there was. After I finished the tasks, I received an email a few days later sayi…
- ADCI - Karnataka Software Engineer four-hour loop and shadow-deployment designADCI - Karnataka · Software Engineer · HR Screen · Jun 2026Offer
The process began with an HR screening that included two LeetCode questions, then an HR manager screening. After that came four hour-long loop interviews, so it felt like a full interview day rather than a brief conversation. The loop included three medium LeetCode questions and one system-design interview. The design topic was shadow-deploying test software to millions of users. It made me think…
- ADCI - Karnataka Software Engineer four-interview leadership and GenAI loopADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
After an initial recruiter touchpoint, I went through a four-interview loop built around Amazon-style leadership principles. Three interviews were with people from the team I might have joined, and the last was with a bar raiser from another organization. Two interviews were coding-focused. One was LeetCode style and another leaned into system design. I also had a general GenAI round, so it was n…
- ADCI - Karnataka Software Engineer interview experienceADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
The process began with online recruitment quizzes full of brain-teaser-style questions that felt irrelevant to the Software Engineer job. I was frustrated because I was not applying to solve riddles. Even at that early stage, the tone affected how I saw everything afterward. It felt disrespectful to my time and did not give me confidence in the evaluation. I did not receive an offer. The difficul…
- ADCI - Karnataka Software Engineer Interview Experience: about three months from assessment to decisionADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
My path began with an online assessment, followed by a recruiter call that set up an onsite loop. The onsite had three consecutive stages: a bar raiser loop, a DSA focused loop, and an LLD focused loop. The full timeline, from the assessment to the final decision, was about three months, far longer than I expected. The interviews felt as though they covered the usual breadth: leadership judgment…
- ADCI - Karnataka Software Engineer Interview Experience: DSA, design, and bar raiserADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
The loop began with demanding technical rounds. I had to work through two LeetCode DSA problems, one medium and one hard. Getting the solution to work was only part of it: I had to explain my thinking, analyze time and space complexity, cover edge cases and optimizations, and discuss alternative approaches and trade offs. Next came system design for a scalable, distributed Amazon style service. W…
- ADCI - Karnataka Software Engineer Interview Experience: four back-to-back onsite roundsADCI - Karnataka · Software Engineer · Onsite · Jun 2026
After the initial recruiter interactions, I had an onsite loop with four back-to-back rounds in one day. It was intense but clearly structured: two coding-heavy rounds with senior engineers, one hiring-manager round, and one behavioral round with a bar raiser. Leadership principles and data-structures topics appeared repeatedly through the day, so I could not really separate the behavioral piece…
- ADCI - Karnataka Software Engineer Interview Experience: Guided online testADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026Rejected
Someone from the hiring side contacted me through LinkedIn, and after I applied, the process began with an online test. The questions resembled HackerRank problems, but they came with a few videos that explained the reasoning and approach the company expected. The difficulty felt average. This stage seemed to be testing how I reasoned rather than brute-force coding. I did not receive an offer, th…
- ADCI - Karnataka Software Engineer Interview Experience: Recruiter call and codingADCI - Karnataka · Software Engineer · HR Screen · Jun 2026
My first substantive conversation was a phone interview over Chime with a recruiter. It began casually enough that I thought it might remain a relaxed chat. Instead, it quickly shifted into behavioral questions about how I had handled situations, along with one easy LeetCode coding problem. The difficulty was average, but the timing and change in tone caught me off guard. I did not receive an off…
- ADCI - Karnataka Software Engineer interview: architect-level questionsADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
I applied through the Amazon job portal and got an HR call. After that, I went through five technical rounds in total: one described as a screening round and the rest scheduled as technical interviews. The early questions felt aimed at architect-level depth even though I was applying as a developer with four years of experience. The first two rounds were the hardest, and the questions pushed beyo…
- ADCI - Karnataka Software Engineer interview: four rounds in two daysADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026Offer
I applied through Amazon Careers without a referral. A recruiter reached out, then I completed an OA. About a month later, I was scheduled for four rounds across two days. The pace was intense. Each interview included 30 minutes of behavioral discussion and 30 minutes of coding. Coding and system-design content were spread across the four interviews, while the overall format stayed consistent fro…
- ADCI - Karnataka Software Engineer interview: four-round design loopADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
After I cleared the online assessment, I entered the Amazon loop. It had four rounds: two coding interviews, a behavioral interview focused heavily on Amazon Leadership Principles, and a final hiring-manager round that combined coding with high-level design. The first coding round had two LeetCode medium problems. The second moved to a hard problem, with the same expectation that I write clean co…
- ADCI - Karnataka Software Engineer interview: OA and leadership principlesADCI - Karnataka · Software Engineer · Online Assessment · Jun 2026
My process started with an online assessment, and it took a long time before I even reached the interview stages. After the OA, I had two interviews, each about 60 minutes. Across the process, I heard that both LeetCode-style problems and leadership principles were part of the evaluation. That meant my prep could not just be DSA. I also had to have specific stories ready for leadership-principle…
- ADCI - Karnataka Software Engineer silicon-team domain, design, and C roundsADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
I interviewed for the silicon team. The loop was clear about what each round covered, and each interview lasted about 50 minutes. The first round focused on domain-specific knowledge. The second moved to system design, and the third covered C coding. The overall difficulty was average, and I did not receive an offer. What I remember is how deliberately the responsibilities were separated: domain…
- ADCI - Karnataka Software Engineer technical phone screen before loopADCI - Karnataka · Software Engineer · Technical Screen · Jun 2026
The process began with a phone screen that lasted about an hour or more. It was mostly technical questions. After I cleared that step, I moved into the loop interview. The loop was the next stage after the initial screen. Difficulty was average, and I did not receive an offer. The first call set the tone because it tested technical thinking right away rather than serving as a casual introduction.…
- Amazon Account Executive interview experience: unannounced Excel taskAmazon · Account Executive · Jun 2026
A recruiter contacted me about a different account-management role. The email said the interview would be competency based and focused on Amazon Leadership Principles. There was not supposed to be an HR prescreen, and the confirmation did not suggest a complicated set of materials. On the day, the format changed in a frustrating way. I was suddenly given an Excel-sheet task without advance notice…
- Amazon Advertising Software Engineer Interview Experience: four demanding loop roundsAmazon Advertising · Software Engineer · Online Assessment · Jun 2026
The process started with an online assessment and moved into four rounds: coding, deeper technical design, Leadership Principles, and another design round. The coding interview had two DSA problems, one medium and one hard. I had to solve them optimally, explain my approach, cover time and space complexity, edge cases, optimizations, alternatives, and trade offs. The design work covered an Amazon…
