READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 24 of 153
Interview experiences · Amazon
Amazon Project Manager interview with a timed AI-led Leadership Principles screening
My process started with a recruiter email screen, followed soon by a recorded, timed virtual interview led by AI. A virtual interviewer asked behavioral questions tied to Amazon's Leadership Principles. I answered on camera and had to handle follow-up prompts while the clock kept moving, which made it feel more pressured than a normal screen. About a week later, I had a one-hour video interview w…
Interview experiences · Amazon
Amazon Robotics Engineer interview: AI-assisted code modification and DSA
My loop had two main rounds. The first focused on generative AI: I received a coding question and then had to modify the code using any AI model. The second was still heavy on DSA, but I was not asked to use AI for that round. The overall difficulty felt easier. What made the process different was the explicit requirement to use AI for code modification instead of treating it as optional. I felt…
Interview experiences · Amazon
Amazon SDE 1 Interview Experience — Three Rounds, Rejected in Five Business Days
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…
Interview experiences · Amazon
Amazon SDE Intern Interview Experience — Coaching a Mock VO With BQ, Morse Code, and a Word Break II Follow-up
Last week I ran a mock/practice VO (virtual onsite) session for someone prepping for their Amazon interview for the 2026 SDE intern role. It 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 motivate them and come up with a way to solve the problem? Why did you choose Amazon? Then th…
Interview experiences · Amazon
Amazon Senior Applied Scientist Interview Experience — Passed the Tech Screen Despite an Unfinished Graph Question
An Amazon recruiter found me on a job site and had me apply for a senior applied scientist role. The recruiter met with me first and walked me through the general shape of the tech screen — ML breadth plus coding. ML Breadth. The interviewer was pretty nice. This part asked a lot of fundamental questions, like: 1) What is a p-value? 2) What is overfitting and underfitting, and how do you address…
Interview experiences · Amazon
Amazon Senior Software Engineer Interview Experience — Five-Round L6 Onsite, No Breaks, One Rough HM
Just finished interviewing this week. Not a great experience. The whole process was rocky — I got switched between teams for matching several times, and there were two months between the phone screen and the onsite. Security & Service org. It felt like they wanted to go through the motions without actually wanting to hire me. The third round with the HM in particular was a really bad experience,…
Interview experiences · Amazon
Amazon Senior Software Engineer Interview Experience — Five Rounds, No Breaks, and a Gum-Chewing Hiring Manager
Just finished interviewing this week. Not a great experience. The whole process was rocky — I got re-matched to a different team several times, and there were two months between the phone screen and the onsite. Security & Service org. It felt like they just wanted to go through the motions, not like they actually wanted to hire me. Round three with the hiring manager was especially bad — I've nev…
Interview experiences · Amazon
Amazon Senior Software Engineer Interview Experience — L6 Phone Screen With an Impatient Interviewer, LCA Follow-up Stuck
The interviewer was impossible to find anywhere online, I couldn't find a thing about him and I'm speechless. BQ: 1. How do you evaluate customer experience? 2. A major unexpected obstacle. For the first one, I think the point of the question was the evaluation part, and my story was just directly collecting feedback, which he wasn't happy with 😭 For the second one, he felt the obstacle wasn't ma…
Interview experiences · Amazon
Amazon Senior Software Engineer (L5) Interview Experience — Four Onsite Rounds, Rejected After the System Design Round
Timeline: referral, then a recruiter call two weeks later that set up the phone screen for a week after that, then the onsite (four rounds) a week after that, and a rejection two days after the onsite. Overall impression: the coding difficulty wasn't that high, basically all LeetCode Medium, and every round asked Leadership Principles (LP) questions. I think what got me in the end was System Desi…
Interview experiences · Amazon
Amazon Senior Software Engineer (L6) Interview Experience — a Vague LockingTree Screen That Ran Long
I interviewed for L6 last Friday — I'm probably 80% sure I failed. It was with the Aurora team, and the interviewer ran the whole thing. The interview was scheduled for one hour, but I got tortured for an hour and a half. Right off the bat the guy spent about 10 minutes introducing himself, then had me talk about a time I both challenged and simplified a system — the scope needed to be big enough…
Interview experiences · Amazon
Amazon Senior+ Data Scientist Interview Experience — L5 Technical Screen, Rejected Over the BQ Round
In 2026 there have been almost no Amazon DS interview write-ups here on 1point3acres — I'm starting to wonder if they're on a hiring freeze. I'm writing one up so people have something to reference. Around mid-March I had applied to 2 AS (Applied Scientist) roles. A recruiter reached out to me on LinkedIn and scheduled a recruiter call a few days later. On that call they told me AS roles are most…
Interview experiences · Amazon Services
Amazon Services Software Engineer Interview Experience: Calculator prompt without requirements
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…
Interview experiences · Amazon Services
Amazon Services Software Engineer Interview Experience: Leadership Principles and tradeoffs under uncertainty
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…
Interview experiences · Amazon
Amazon Software Engineer internship interview: leadership principles and FBA pitch
For this internship role, I had two one-hour interviews focused on Amazon’s Leadership Principles. Questions covered delivering results, earning trust, diving deep, and ownership. The interviews also reflected that the position was sales-oriented. There was a simulated customer pitch about adopting Amazon FBA. The difficulty felt easy, and the process was driven by the principles, with the sales…
Interview experiences · Amazon
Amazon Software Engineer interview
This was an online virtual loop focused on data-center work, with several rounds over a couple of days. Each round mixed situation-based and behavioral prompts with technical discussion relevant to that environment. The interviewers ranged from manager to principal and staff engineer. The individual questions felt average in difficulty, but the multi-day schedule and seniority of the interviewers…
Interview experiences · Amazon
Amazon Software Engineer interview: a high-pressure technical and behavioral process
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…
Interview experiences · Amazon
Amazon Software Engineer interview: AI coding assessment
My Amazon process began with online tasks before the more traditional interviews. The DSA portion used something like a house-robber II problem, so it felt more focused on dynamic-programming trade-offs than a simple brute-force solution. The assessment also had an AI-based coding round. I was given a code repository and an AI model with guardrails, then had to work from failing test cases to und…
Interview experiences · Amazon
Amazon Software Engineer interview: AI debugging and design rounds
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…
Interview experiences · Amazon
Amazon Software Engineer interview: assessment and waitlist
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…
Interview experiences · Amazon
Amazon Software Engineer interview: behavioral bar-raiser, DSA, and low-level design
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…
Interview experiences · Amazon
Amazon Software Engineer interview: brain teasers and OA rejection
The process began with online recruitment quizzes or an OA, and those early steps set the tone. One path was packed with brain-teaser-style questions that did not match the job I was applying for. It made the process feel disrespectful of my time. In another attempt at the same general funnel stage, I submitted OA solutions and received a rejection a few days later. That assessment was more typic…
Interview experiences · Amazon
Amazon Software Engineer interview: coding, repository debugging and two design questions
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…
Interview experiences · Amazon
Amazon Software Engineer interview: coding rounds, system design, and a narrow-feeling evaluation
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…
Interview experiences · Amazon
Amazon Software Engineer interview: DSA edge cases and an AI-assisted repository task
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…