READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 21 of 153
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: coding question followed by web debugging
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: DSA and rate limiter
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: DSA, system design, and GenAI projects
The process was clear after the initial recruiter coordination. After applying, I had an online coding test on a coding platform, followed quickly by HR-style questions and then a face-to-face technical round with a mix of topics. The technical part drove the process. I had multiple coding questions, including DSA-focused work, and at least one session that combined system design with coding. Acr…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: exhaustive leadership and product loop
The journey involved many people, each testing a different angle of the same skill set. Before the main loop, I had a recruiter screen and a pre-interview check with the hiring manager. I then had technical and product-adjacent conversations with an engineering director, a senior product owner, and senior engineers. The final stretch included Bar Raiser-style interviewers and a hiring-manager con…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: Full-stack debugging home test
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview experience: leadership principles across rounds
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: Mid-60s score on the OA
The online assessment was the hardest gate for me. I had applied earlier in the summer and moved forward to the OA near the start of August. The coding questions threw me off. They did not seem impossible, but I struggled enough to score around the mid-60s overall, and that ended the process for me. From what I saw, people who cleared the OA went into a short, structured technical loop with codin…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview experience: OA, fundamentals, and behavioral fit
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: Patient queue-with-two-stacks discussion
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: timed OA with debugging and work hypotheticals
The online assessment was where I really struggled. I received an invitation to an OA for graduates, and the first programming task had an absurdly short time limit. A large part of it went just to reading and understanding the question. The second test was more reasonable, but the first hurdle had already changed my pace. In a similar OA setup, there was a standard DSA test, an AI-assisted codin…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: four back-to-back conversations with a Bar Raiser
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.…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: GenAI and debugging
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: ML, CS, and HR breadth
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: OA and three closely grouped interviews
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.…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: OA coding and leadership assessment
I received the online assessment about a week after applying, before any loop interviews. It took longer than I expected because it packed in a lot, including video material explaining the kind of reasoning and approach they wanted. The OA had standard coding challenges focused on algorithms and data structures, along with a leadership-assessment component. I had heard that leadership principles…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: one HackerRank-to-linked-list round
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: pressure-focused technical and behavioral loop
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…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: three-month onsite wait
My Amazon DSP process slowed down after the OA. It took around three months to hear about an onsite at the New York office, where I had an SWE round and a managerial round back to back. The initial assessment had two coding problems, one algorithmic and one mathematical, plus a short work-style survey. After that screen, I completed a 45-minute phone interview focused on behavioral questions and…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview with four coding loop rounds
The process followed a familiar Amazon pattern: a recruiter screen, then a time-boxed technical screen with behavioral questions first and a dedicated coding block after that. It ended with time for my questions. The final loop had four technical-style rounds. I solved data structures and algorithms problems in a shared coding environment while explaining my reasoning and trade-offs. Every round…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer technical loop with leadership-principle bar raiser
After a recruiter conversation, I had a roughly hour-long technical phone screen. Once I cleared it, the process moved into scheduled loop interviews. It was structured, but intense. The loop combined coding with Amazon-style leadership discussions. I had two coding-heavy sessions: one began at medium LeetCode difficulty and another went into harder territory. There was also a system-design discu…
Interview experiences · Amazon
Amazon Economist Summer Intern Interview Experience — Two Case+BQ Rounds, No Coding This Year
During this application season I also interviewed for the Amazon economist summer intern role, so I'm writing up my experience here to share with anyone who needs it. Timeline: Mid-January 2025: had a senior refer me 03/04/2025: HR reached out 03/26/2025: first round 03/28/2025: got the email that I passed the first round 04/16/2025: second round 04/16/2025: two hours later that same day, heard I…
Interview experiences · Amazon
Amazon Frontend Engineer (SDE I) Interview Experience — One DSA Round, Two Mediums, Rejected
I applied through a LinkedIn post for SDE I (Frontend). HR contacted me over a call and we discussed the further rounds. Round 1 (PS-DS Round) (1hr) Two DSA medium questions were asked, and I was able to solve both of them within the time limit (~40 mins). The interviewer was helpful and provided hints. Q1. Lowest Common Ancestor of a Binary Search Tree Q2. Ones and Zeroes Explain brute force, th…
Interview experiences · Amazon
Amazon Intern Data Scientist Interview Experience — Passed the Technical Loop, Now in Team Matching
I'm a third-year PhD student in Econometrics and Quantitative Economics, working in Finance, Public Finance, and IO. I applied to Amazon pretty late this year, and since I was extremely busy this semester, I took the last possible deadline at every stage. I finally got the email confirming I'd passed the final technical interview on April 10, and I'm now officially in the team-matching phase. I w…
Interview experiences · Amazon
Amazon Intern Data Scientist Interview Experience — Two Back-to-Back Virtual Onsite Rounds
This interview was purely a case of getting lucky. I got the interview invite on 4/12, then had two VO (virtual onsite) rounds back to back on 4/22, with no break in between. Both interviewers held PhDs. VO1 Standard LP (Leadership Principles) questions, and then they dug into a lot of detail based on my answers. Tell me about a most recent project Calculated risk A time you needed to extend a de…