real interview stories, told over a cup of tea ♡
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
3935 results
- Amazon Technical Program Manager interview: scheduling fell apartAmazon · Technical Program Manager · HR Screen · Jul 2026Rejected
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…
- Amazon Web Services Software Engineer Interview Experience: Nerves in LP loopAmazon Web Services · Software Engineer · Jul 2026
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…
- Amazon Web Services Software Engineer interview: LLD and GenAI onsite loopAmazon Web Services · Software Engineer · Online Assessment · Jul 2026
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…
- Amazon Web Services Software Engineer interview: online assessment and two interviewsAmazon Web Services · Software Engineer · Online Assessment · Jul 2026
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…
- Amazon Web Services Software Engineer interview: timed OA and leadership-principles discussionAmazon Web Services · Software Engineer · Jul 2026Offer
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…
- Ambiguous Word-Combination Problem, Rejected After a Rocky Phone ScreenAmazon · Software Engineer · Technical Screen · Jul 2026Rejected
Got rejected from the phone screen — I saw it on the portal before I even got the email. The interviewer opened with a hard problem, similar to a LeetCode problem, but it required outputting the actual combinations. It was really strange — the problem didn't say whether the word had to be in the given list, how many times each word could be used, or whether repeats were allowed. I asked him about…
- AMD Construction Group Software Engineer interviewAMD Construction Group · Software Engineer · Technical Screen · Jul 2026
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…
- AMD Construction Group Software Engineer Interview Experience: Medium LeetCode, RTL, and CUDA optimization questionsAMD Construction Group · Software Engineer · HR Screen · Jul 2026
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…
- AMD Project Manager interview: Agile and team-dynamics discussionAMD · Project Manager · Other · Jul 2026
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…
- AMD Software Engineer interviewAMD · Software Engineer · Technical Screen · Jul 2026
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…
- AMD Software Engineer Interview Experience: Strings, arrays, and edge casesAMD · Software Engineer · Technical Screen · Jul 2026Rejected
My first round was a DSA-focused screen with two medium coding questions about strings and arrays. I felt they cared most about handling edge cases carefully, not just arriving at a working answer. The interview went smoothly, and the interviewer was helpful when I got stuck, which made the pace easier to handle. Overall, it was a positive experience. The questions followed a familiar clean-codin…
- AMD Software Engineer interview with four technical and scenario roundsAMD · Software Engineer · Technical Screen · Jul 2026
The process started with a hiring-manager-style conversation about what I’d been working on day to day, and we went deep into my past experience. After that, I moved into a panel format, and the loop became more technical and focused on problem solving. I completed four rounds in total. The panels seemed to have a couple of interviewers each, and the questions mixed technical problems with scenar…
- AMD Software Engineer interview with NPU and hardware accelerator focusAMD · Software Engineer · Technical Screen · Jul 2026Offer
I started with a recruiter call about my location and sponsorship needs, followed by an explanation of the interview process. Next came a behavioral interview with the hiring manager, who followed up on almost everything I said. Since the role was with an NPU-related group, I spent a lot of time connecting my background to AI and hardware accelerators. The technical part included another coding-f…
- AMD Software Engineer interview with two medium DSA questionsAMD · Software Engineer · Technical Screen · Jul 2026
My first round was mostly DSA, with two medium LeetCode-style questions focused on strings and arrays. The interviewer seemed especially interested in how carefully I handled edge cases, rather than whether I could get a happy-path solution working. The pace was steady and the conversation felt supportive. When I got stuck, the interviewer nudged me back in the right direction. Overall, it went w…
- AMD Software Engineer interview: low-level C/C++ and hardware integrationAMD · Software Engineer · HR Screen · Jul 2026
My process began with an initial recruiter and hiring-manager screening, followed by a fairly rigorous technical loop. The format was described as a sequence of two to four rounds. The interviews focused on low-level systems knowledge, C/C++ coding, and how hardware and software need to work together. The questions weren't abstract brainstorming. They kept coming back to how I'd reason about syst…
- AMD Software Engineer interview: RTL verification and debugging fundamentalsAMD · Software Engineer · Jul 2026Rejected
My interviews were hardware-centric from the start, with a strong focus on verification and digital-design fundamentals. I had a digital and RTL round covering Verilog/SystemVerilog, UVM, and the practical work of verification. A second round brought together projects and real scenarios. The first technical section asked for solid fundamentals rather than broad buzzwords. The project round asked…
- AMD Software Engineer interview: systems and hardware-software integration loopAMD · Software Engineer · HR Screen · Jul 2026
The process began with a recruiter call and a hiring-manager screen, followed by a more demanding technical loop. Low-level systems knowledge and hardware-software integration were central. It was described as a two- to four-round sequence, and it felt like the depth increased steadily. In one round, I spoke with an engineer panel and other interviewers. The whole process took roughly a few weeks…
- AMD Software Engineer interview: WhatsApp-style design and DP questionsAMD · Software Engineer · Technical Screen · Jul 2026Offer
The hardest part of my loop was the systems-level design work. I was asked to cover both high-level and low-level design, then I got dynamic-programming prompts as part of the technical evaluation. One design prompt was essentially to build a messaging app like WhatsApp from scratch, and I had to explain what tech stack I'd use if I were developing it today. For the DP questions, I solved one med…
- Amgen Software Engineer interview with recruiter, hiring-manager, and pending panel stagesAmgen · Software Engineer · Jul 2026In progress
My process started with a recruiter phone screen about my current work and background from earlier roles. It was not overly technical. It felt more like they wanted to understand my experience and how I might fit the role. About a week later, I had a call with the hiring manager. That was a mix of a vibe check and targeted technical questions. The technical discussion focused on clarifying concep…
- Amgen Software Engineer interview: technical deep dive and leadership fitAmgen · Software Engineer · Technical Screen · Jul 2026
The Amgen process was unusually well organized. The recruiting team gave clear timelines and transparent communication, which made it feel professional and predictable. The first round was virtual and used a deep technical assessment of core competencies, problem solving, and real-world scenarios. The second was face to face and moved away from straight coding into leadership, cultural fit, and s…
- An applied AI Software Engineer interview: hostile and confusing interview conductAn applied AI · Software Engineer · HR Screen · Jul 2026
The process began with an HR-style call and then technical and bar-raiser-style conversations, but it quickly felt hostile and disorganized. Interviewers would not turn on their cameras and resisted when I asked to see them. Two people in one meeting space had similar accents, which made it genuinely hard to tell who was speaking. In other rounds, people did not seem to listen closely and sometim…
- An applied AI Software Engineer interview: rushed EV charging design discussionAn applied AI · Software Engineer · Technical Screen · Jul 2026
I got pulled into a Karat-driven stage that felt chaotic and rushed from the start. It was split evenly between system design and a DSA problem-solving block. I was asked to design an EV charging-station app that could find the nearest station and handle payments, and I was pushed to move quickly. The conversation barely felt like a design discussion. I spent a lot of time on basic whiteboard too…
- An applied AI Software Engineer interview: TCP, TLS, and system designAn applied AI · Software Engineer · Technical Screen · Jul 2026Offer
I started with a deep technical round that gradually broadened into leadership-oriented conversations. The first round covered middleware and networking fundamentals, including TCP, TLS, certificates, and how an F5 Big-IP device is upgraded and configured. It was detailed enough that I needed to be precise, but I could answer most questions and keep the discussion moving. The next stage was a tec…
- An applied AI Software Engineer interview: technical, manager, and bar-raiser roundsAn applied AI · Software Engineer · Technical Screen · Jul 2026
The process felt high-stakes and had two technical rounds, a managerial round, and a bar-raiser-style discussion. It opened with a coding round that could eliminate me. Once I finished it, the remaining stages came quickly. After a short gap of a couple of days, I completed the next rounds in a single day. The pace left little time to decompress, and I had to stay sharp across different formats.…
- An applied AI Software Engineer interview: unclear live coding expectationsAn applied AI · Software Engineer · Technical Screen · Jul 2026
The initial screening felt normal, but the technical interview did not. I was given LeetCode-style questions, and the interviewer's behavior made the situation tense. They did not want to explain the question and expected a fully running solution while I was answering. That mismatch between the communication and the expectation put me under stress and did not feel supportive. I did not move forwa…
- An Open-Book Coding Screen That Still Ended in RejectionNetflix · Software Engineer · Technical Screen · Jul 2026Rejected
I interviewed for the Member team — it was basically an open-book style interview, similar to a couple of other phone screen reports I'd seen. Problem Solving: Netflix homepage content dedup — for each row, the first n titles need to be deduplicated globally; after position n+1, you only need to make sure there's no duplicate within that row itself. Follow-ups: 1. what if n is different for each…
- Analog Devices Software Engineer interview: a rejection for interviews that never happenedAnalog Devices · Software Engineer · HR Screen · Jul 2026Rejected
I first spoke with a recruiter about a hardware-validation role. The call was friendly and clear. We covered my background, relocation and work authorization, and my interest in hardware validation, mixed-signal systems, and test development or automation. I was told to expect a hiring-manager interview and then a longer technical panel. Neither was scheduled. I later got a rejection email that n…
- Analog Devices Software Engineer interview: circuit-focused pressureAnalog Devices · Software Engineer · Jul 2026
This interview was almost entirely about circuit-level thinking. I met a director of test engineering early, and the technical conversation centered on circuits rather than behavioral topics. The expectation seemed to be quick, precise solutions, and I felt a mistake could end my chances. Another circuit-focused discussion covered how to test whether a circuit works, then components such as capac…
- Andela Products Software Engineer Interview Experience: Python, React, and live codingAndela Products · Software Engineer · Jul 2026
I began with an online Python-and-React assessment that felt like a mini project. It started with debugging, then two Python functions using real data structures rather than LeetCode-style tasks. The logic was straightforward, but I spent most of my time writing tests. The final part was a React layout, and AI use was allowed there. After passing, I had a Python-focused interview covering Python,…
- Andela Software Engineer Interview Experience: Practical Python and React assessmentAndela · Software Engineer · Jul 2026
My take-home assessment combined Python and React. It began with debugging, then two Python functions using real data structures rather than LeetCode problems. The core logic was straightforward, but I spent most of my time writing tests. The third section was a React layout, where AI use was allowed. After passing, I had a Python technical interview on fundamentals, FastAPI, and AI-related servi…
