READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 20 of 153
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview: design then manager rounds
I went through three rounds that moved from technical work to more managerial conversations. The first was system design: I was asked to design a streaming application like Netflix or Amazon Prime Video. I focused on structuring the design and its trade-offs, and that was the only technical round I cleared. The remaining rounds were managerial. They focused on how I work, how I think about delive…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview experience
Recruiter outreach turned into a marathon. After the initial steps, I was scheduled for an onsite-style block of back-to-back interviews. I did four rounds in one day with senior engineers, followed by additional conversations about leadership and design. The day opened with coding and problem solving. For DSA questions, the interviewer cared about how I explained edge cases aloud. In one interva…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: bamboozling OA and mixed loop
I started with an online assessment before moving into an all-live-interview loop. The OA was the first real shock. The questions did not feel impossible, but I got completely bamboozled and did not get far enough to move to the next step. The loop itself had about three rounds of roughly an hour each, mixing coding and behavioral questions. Coding felt easy to medium for me, but the behavioral s…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: Book management and delivery-system design
My final interviews were face-to-face and covered several technical lenses. I had DSA questions, a low-level design round to design a book-management system, and a leadership and behavioral discussion tied to Leadership Principles. The technical rounds put a lot of weight on explaining trade-offs while coding and designing. One design prompt resembled an LRU cache, while another resembled an Uber…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: coding, design, and Leadership Principles
This Amazon process felt like a full technical deep dive rather than a quick screen. After applying, I had multiple live rounds combining coding, system design, and detailed behavioral questions about Leadership Principles. The coding work required more than an optimal LeetCode style solution. I had to explain my thought process, edge cases, time and space complexity, alternative approaches, and…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: debugging under time pressure
One technical sequence began with a medium LeetCode-style problem and then switched to debugging a web application. The assistant I could use was tightly limited: it could read files and explain components, but it would not provide the answer. Understanding the bug mattered, but so did staying organized while navigating the codebase under time pressure. I could follow the logic, yet the debugging…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: DSA complexity and leadership principles
After the recruiter step, I had a one-on-one virtual technical interview with an engineer. We moved quickly from small talk to two DSA problems on a shared coding platform, and I had to state time and space complexity as I worked. The broader loop was technical first with Leadership Principles throughout. It included multiple DSA-focused interviews, low-level design, and a dedicated leadership-pr…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview experience: grid paths and RAG
My on-campus Amazon SDE Intern process began with an online assessment. It combined coding with a Leadership Principles work simulation and a feedback or workstyle component. Only some students from the campus drive were shortlisted for the OA. The coding included sorting IDs by frequency with smaller-ID tie-breaking, and an array-transformation minimum-cost problem based on greedy reasoning and…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: leadership-focused virtual ladder
I went through an extended interview path that felt like climbing an organizational ladder. After the initial recruiter screening, I had virtual rounds with senior engineering leaders: an engineering director, a senior product owner, and a senior software engineer. Amazon's Leadership Principles were a major part of the loop. The Bar Raiser was a distinct stage, and I could not treat the behavior…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: OA versus live DSA round
The OA mixed classic DSA with aptitude-style material. The coding problems ranged from easy upward, and there were also statistics-and-probability questions, including estimation tasks that moved quickly and made me question how confident I was in my answers. The live interview felt lighter and more straightforward than the OA. In the technical round, I solved two easy DSA questions on a platform…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: onsite loop with STAR follow-ups
My process ran from recruiter submission to HR questions and then an onsite-style technical loop. The onsite included several live coding segments, system design, and behavioral questions about how I would work in the role. Each round mixed categories. Alongside live coding, I discussed system-design tradeoffs and architecture beyond implementation details. For behavioral questions, I used STAR s…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Interview Experience: Queue with two stacks
After applying, I completed an online assessment with two algorithm-focused problems. One was a sliding-window task and the other involved binary search. It felt less like vague theory and more like recognizing the right pattern and implementing it within the time limit. After passing, I moved to coding-first stages. In one round, I implemented a queue using two stacks, working through the mechan…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview: leadership and hard DSA
The process felt brutally demanding and somewhat long because it paired Leadership Principles with deep DSA expectations. After an initial recruiter stage, I faced technical questions presented as DSA problems at a higher level than I expected. I received multiple DSA problems in one stretch. I solved only part of them; I could not reach working solutions for the rest. Throughout, the interviewer…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview: repository coding and interviewer connectivity issues
I had four roughly hour-long panel rounds, with Amazon Leadership Principles woven through technical discussion in each one. I had to connect my answers to impact and decisions instead of treating the behavioral material separately. The first technical round included two DSA questions, one of them repo-based within an existing codebase. I got the core solution underway but ran out of time while w…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview: resilience under pressure
The interview loop felt brutal but streamlined. It mixed behavioral and technical questions, but the defining feature was heavy artificial time pressure used as a deliberate stress test. The questions made me feel as though they wanted to push me close to breaking, with the clock forcing me to show how I perform under strain. The technical difficulty was high, not only because of the problem itse…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview: SDE Intern assessment mix
The SDE Intern process was described as a mix of coding ability, problem solving, computer-science fundamentals, and Leadership Principles fit. It began with an OA, then continued through rounds on leadership principles and core subjects, DSA, and more leadership-principle evaluation. The exact timeline could vary by country and hiring season, but the stated structure kept coding and fundamentals…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer interview: timed first stage
The process had three stages and moved quickly from the first assessment into a work-style component. The opening stage had two parts: a couple of timed coding questions and then a workstyle assessment. I did not finish that first stage, so the process stopped there. I had to solve two coding problems within their time windows. I felt I was managing my time, but still could not make enough progre…
Interview experiences · Amazon
Amazon Development Center U.S. Software Engineer Java Spring Boot debugging loop
After a recruiter call, I had a technical phone screen of about an hour with practical engineering questions. Once I cleared it, I entered the loop. The loop combined coding, systems thinking, and Amazon Leadership Principles. I solved LeetCode-style problems, discussed system design, and completed a STAR-format behavioral round. In one round, I used an AI-enabled setup to debug code in a Java/Sp…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview
The process started with an online assessment containing two coding problems and multiple test cases. I passed some cases right away and did better on the second problem. Then I had two coding rounds: graphs and arrays in one, linked lists and binary search trees in the other. There was also a behavioral section on situations and workplace fit, spread across multiple rounds over a couple of days.…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: coding, design, and behavioral sequence
After recruiter screening, I completed a take-home LeetCode-style assessment, a live coding interview, a system design segment with two design questions, and a behavioral discussion about communication and collaboration. Coding came first in the live stages, while behavioral evaluation was a structured test of fit. The process also looked at work style and how I explained my thinking, not just wh…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: debugging pressure during DSA and an AI-assisted repository task
This was a four-round process, but I did not pass the first round. It paired a classic DSA problem with an AI-assisted coding task in a repo-style setup. I could write a DSA solution, then got caught on edge cases without enough time to debug it properly. The repo task also felt like a race against the clock. I tried to adapt, but timing pressure and the need to be precise worked against me. I di…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: DSA-heavy assessment
I applied, completed a technical assessment, and then interviewed with several team members. The OA included two DSA-style questions and a behavioral or work-style component. I remember Two Sum and a longest-substring-without-repeating-characters question. The later technical interviews used similar easy-to-medium DSA questions. I made it through the process and was selected and accepted. Even so…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer interview: DSA screens and lost confidence
I started with a recruiter and then had a technical screen focused on problem solving and communication. I was asked several DSA-style questions, and the interviewer cared about how I handled them as much as whether I reached an answer. I solved only a couple, while the rest did not click, so the session felt difficult and lengthy. In a separate, lighter coding-focused screen with more recognizab…
Interview experiences · Amazon DSP
Amazon DSP Software Engineer Interview Experience: back-to-back behavioral and DSA sessions
My loop had two back-to-back sessions that were intense but well paced. Early in the first session, the interviewer focused heavily on behavioral stories, then the rest moved into DSA problem solving. The second session followed a similar structure, so I had to alternate between explaining my approach and demonstrating it through coding. I had time to solve DSA questions in each session, but the…