READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 27 of 153
Interview experiences · Amazon
Amazon Software Engineer interview: organized coding and leadership
I began with an online coding assessment on data structures, algorithms, and problem solving. After passing it, later interviews combined coding, design fundamentals, and Leadership Principles. Follow-up questions tested my thought process rather than only whether I reached a solution. Leadership discussion was woven into the technical evaluation, so it felt broader than a coding test. I did not…
Interview experiences · Amazon
Amazon Software Engineer interview: pressured DSA and leadership-principles loop
After the initial online assessment, I entered several technical interviews with a consistent structure: coding first, then strong pressure to connect my answers to Amazon Leadership Principles. The most intense round combined leadership-aligned evaluation with multiple DSA problems, turning it into a test of time and completeness rather than one neat solution. I also had a couple of medium codin…
Interview experiences · Amazon
Amazon Software Engineer interview: recruiter to live coding
I had a 30-minute recruiter phone screen about my background and resume. About a week later, I had an approximately one-hour technical video interview with a senior engineer. After introductions, I completed a live coding challenge in a shared editor. The round ended with system-design basics and questions about how my past projects worked in practice. It was average in difficulty: nothing entire…
Interview experiences · Amazon
Amazon Software Engineer interview: sliding window and a debugging leadership story
I had a phone round with two focused prompts. One was a medium sliding-window problem, and I had to explain how I would approach it. The other was about leadership: describe a time I debugged an error, including the issue, how I researched and debugged it, and what I put in place to prevent it from recurring. It felt difficult because it paired a concrete algorithm with a detailed accountability…
Interview experiences · Amazon
Amazon Software Engineer interview: space-system operations background in technical rounds
The process started with a behavioral interview with a team manager, followed by several technical rounds. The overall difficulty felt average, and nothing about the flow seemed chaotic. The questions kept returning to my experience with hardware and operationalizing space systems. Rather than staying only at an algorithm level, the technical discussions asked how I had handled real operational c…
Interview experiences · Amazon
Amazon Software Engineer interview: streaming-system design in a four-round loop
My interview journey was straightforward in how the rounds were organized. After the early steps, I entered a loop with four interviews, each about an hour. It began with a system-design conversation, and later rounds included manager-style discussion plus bar-raiser and behavioral evaluation. The design prompt was to build a streaming application like Netflix or Amazon Prime Video, so the discus…
Interview experiences · Amazon
Amazon Software Engineer interview: technical and leadership rounds
My process had multiple technical rounds and a couple of structured behavioral rounds. One technical conversation mixed troubleshooting with leadership themes such as Bias for Action and GenAI fluency, so it was not solely about writing code. Another technical round focused more directly on coding problems. The hiring-manager round covered leadership principles including Earn Trust, Learn and Be…
Interview experiences · Amazon
Amazon Software Engineer interview: technical assessment and team rounds
I applied online, completed a technical assessment, and then had a couple of interviews with people from the team I would work with. The process was simple and team aligned rather than chaotic. It had multiple rounds but did not feel like a prolonged gauntlet. The difficulty was easy, and it felt more like a check of fit and baseline skills than a difficult hiring process. Location: South Africa.…
Interview experiences · Amazon
Amazon Software Engineer interview: Top-K variation and a restaurant-manager problem
After an online assessment, I went through back-to-back interviews covering DSA, low-level and higher-level design, Leadership Principles, and a final bar raiser. There were a few unusual details. One round asked an AI-usage-style question. Another began with a hiring-manager version of a Top-K problem without API help. A technical prompt used a restaurant manager handling arriving groups, so I h…
Interview experiences · Amazon
Amazon Software Engineer interview: Two Sum and substring offer
I received an OA with two DSA questions and behavioral questions. I then had one interview with two more DSA questions at easy to easy-medium difficulty: Two Sum and longest substring without repeating characters. The interview followed the same basic DSA pattern as the assessment, and the two questions were the kind of fundamentals I could work through directly. The process moved quickly and fel…
Interview experiences · Amazon
Amazon Software Engineer interview with a team-aligned pair of one-hour technical sessions
I received an online assessment first, and then the process moved quickly to interviews aligned with the team I was being considered for. I had two interviews on the same day, each about an hour. Both mixed behavioral questions about past experiences and how I had worked with technical questions. The difficulty felt lighter than what I had heard about similar loops. The day felt manageable becaus…
Interview experiences · Amazon
Amazon Software Engineer interview with an emergency reschedule and four-part final loop
After recruiter communication, scheduling moved smoothly except for an interviewer emergency that required a reschedule. I eventually reached the final loop, which had four back-to-back technical interviews. Each covered a different area: data structures and algorithms, object-oriented design, system design, and behavioral questions tied to Amazon's Leadership Principles. The coding interviews we…
Interview experiences · Amazon
Amazon Software Engineer interview with coding, aptitude, technical, and fit stages
My process began with an online assessment that combined coding and aptitude questions. After I cleared it, I had one or two technical interviews on data structures, algorithms, object-oriented programming, and general problem solving. The final round shifted to fit, with behavioral questions about communication, teamwork, and overall alignment. The experience was challenging because I was evalua…
Interview experiences · Amazon
Amazon Software Engineer virtual onsite interview experience
My process began with a recruiter screen, then moved quickly through an online coding assessment and a technical phone interview. The questions were practical but time-constrained, which made it harder to slow down and check every edge case. The final stage was a virtual onsite loop with multiple interviews. I had data-structures-heavy questions, system design, and a debugging-focused segment. Am…
Interview experiences · Amazon
Amazon Technical Program Manager interview: scheduling fell apart
The process began smoothly but ended inconsistently. I had a recruiter phone screen to check cultural fit and whether the role matched my background. The planned next step was a loop of four or five interviewers using cases connected to Amazon Leadership Principles. In practice, communication was where it broke down. After recruiter contact, I did not hear about scheduling for some time and event…
Interview experiences · Amazon Web Services
Amazon Web Services Software Engineer Interview Experience: Nerves in LP loop
I started with an about-one-hour phone screen that was mostly technical and felt as though my future manager ran it. The process then moved quickly into an LP-focused loop, structured around Amazon-style leadership thinking even when the technical work did not look extremely hard. I got a LeetCode-medium problem in the spirit of binary search. I understood it but nerves kept me from landing the s…
Interview experiences · Amazon Web Services
Amazon Web Services Software Engineer interview: LLD and GenAI onsite loop
After the OA, I reached four onsite rounds. The first focused on LLD, and later technical rounds combined coding with Leadership Principle questions. One later round added a GenAI component alongside another LeetCode-style coding question. The demanding part was switching among lower-level design, coding, and leadership discussion. The LeetCode questions felt medium overall, but the range of desi…
Interview experiences · Amazon Web Services
Amazon Web Services Software Engineer interview: online assessment and two interviews
The online assessment combined one or two LeetCode-style problems with a work simulation and a behavioral or Leadership Principles survey. Around the 2-hour mark, time pressure became real. I ran out of time on one question but made partial progress and kept going. I then had two back-to-back one-hour interviews, each with behavioral and technical portions. I used STAR examples tied to Amazon Lea…
Interview experiences · Amazon Web Services
Amazon Web Services Software Engineer interview: timed OA and leadership-principles discussion
After a recruiter call, I completed an online assessment that took a few hours. It included DSA, Leadership Principles, and a work-style simulation about what I would do in a typical workday. I had to manage time tightly and optimize as I went. It felt fair but not forgiving. Soon after, I had a technical and behavioral interview. I worked through a medium-to-hard DSA problem and then answered Le…
Interview experiences · AMD Construction Group
AMD Construction Group Software Engineer interview
I first spoke with the hiring manager about the team and my day-to-day work in earlier roles. The rest of the process was several technical panels, with scenario-based questions that tested both problem solving and technical range. The panels covered computer architecture, UART, SPI, I2C, AXI, APB, AHB, coverage, assertions, UVM fundamentals, debugging, and verification strategy. One round also t…
Interview experiences · AMD Construction Group
AMD Construction Group Software Engineer Interview Experience: Linux, embedded work, and networking
After a recruiter call, I entered a structured technical loop that lasted a few weeks. The recruiter covered my background and the rough process, and about a week later I was in the first technical screen. The later conversations with engineers and the hiring manager focused mostly on my past projects, especially Linux systems and embedded-style software work. I also completed a coding session on…
Interview experiences · AMD Construction Group
AMD Construction Group Software Engineer Interview Experience: Medium LeetCode, RTL, and CUDA optimization questions
My process started with an HR-style phone pre-screen about my background and basic logistics. Then it became very technical. In a manager-style round, I walked through my resume and projects, which led into coding on a couple of medium LeetCode problems, mostly strings and arrays where edge cases mattered. The next technical discussion stayed in that problem-solving lane, with emphasis on RTL kno…
Interview experiences · AMD
AMD Project Manager interview: Agile and team-dynamics discussion
After a recruiter conversation, I met with two team leads and then had a second round with a senior manager. The tone was friendly and easygoing, so the process felt more like a conversation than a test. Most questions concerned my past experience and behavioral situations, especially how I would handle team dynamics when things were not working smoothly. Agile and Scrum terminology came up repea…
Interview experiences · AMD
AMD Software Engineer interview
I started with a hiring-manager call about my background and the work I had done day to day. The rest was panel-heavy: several interviewers in each session, mixing technical problem solving with technical fit. The whole process came to about six rounds, starting with recruiter screening, then the hiring manager, followed by detailed technical discussions based on my experience. The difficulty was…