READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 28 of 153
Interview experiences · AMD
AMD Software Engineer Interview Experience — GPU Systems, Inference, and an Offer
The author reports receiving an AMD GPU software engineering offer after interviews for a Toronto/Markham team. Recruiter outreach led to an initial screen and an extended hiring-manager conversation. An in-person onsite followed roughly two weeks after availability was requested, and the offer arrived about three weeks after that visit. The four onsite sessions covered inference systems, agent a…
Interview experiences · AMD
AMD Software Engineer Interview Experience: Strings, arrays, and edge cases
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…
Interview experiences · AMD
AMD Software Engineer Interview Experience — Three Video Rounds on Verification and PCIe
I'm based in Vancouver, Canada, and wanted to share my AMD interview experience from back then. I moved to AMD in 2022 from another chip company. The Vancouver site didn't have an office yet at the time, so the whole process was video interviews. There were 3 rounds in total, 2 of them technical, each about 1 hour. Overall it was mostly Verification plus the PCIe protocol. On the Verification sid…
Interview experiences · AMD
AMD Software Engineer interview: low-level C/C++ and hardware integration
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…
Interview experiences · AMD
AMD Software Engineer interview on timing and DFT
My interview centered on my project experience, beginning with how I handled both my master's and undergraduate work. The technical conversation moved into more specific areas, including timing and static timing analysis, where the questions became fairly in-depth. I also discussed architectural topics and some DFT basics. The interviewers wanted me to speak concretely about what I had done and c…
Interview experiences · AMD
AMD Software Engineer interview: RTL verification and debugging fundamentals
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…
Interview experiences · AMD
AMD Software Engineer interview: systems and hardware-software integration loop
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…
Interview experiences · AMD
AMD Software Engineer interview: two in-person technical rounds and delayed feedback
I had a couple of in-person technical rounds, and the interviewers gave me a positive signal because the sessions went smoothly. The process felt normal at the time, so I expected that I was moving forward. Afterward, the recruiter didn't update me for about two weeks. I followed up repeatedly, asking several times, and the response eventually became negative. The communication felt unprofessiona…
Interview experiences · AMD
AMD Software Engineer interview: WhatsApp-style design and DP questions
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…
Interview experiences · AMD
AMD Software Engineer interview with four technical and scenario rounds
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…
Interview experiences · AMD
AMD Software Engineer interview with NPU and hardware accelerator focus
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…
Interview experiences · AMD
AMD Software Engineer interview with two medium DSA questions
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…
Interview experiences · AMD
AMD Software Engineer interview with two weeks between HR and technical rounds
The HR screening covered the usual setup, and the technical process followed about two weeks later. The technical questions seemed straightforward at first, but they didn’t stay shallow. The interviewers kept digging into who I was as a person and how I worked, using my answers as the thread. The interviews felt more like an examination of how I function than a pure test of puzzle-solving. Even w…
Interview experiences · American Express
American Express Software Engineer Interview Experience — Three OA Problems, One a Pizza Discount Simulation
First question: given a 3x3 grid with stones placed on it — some cells may have more than one stone, and some cells may be empty — move stones between adjacent cells so that every cell ends up with exactly one stone. Find the minimum number of moves needed. This corresponds to LeetCode 2850, Minimum Moves to Spread Stones Over Grid. Second question: given a set of 2D coordinate points (x, y) and…
Interview experiences · Amgen
Amgen Software Engineer interview: technical deep dive and leadership fit
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…
Interview experiences · Amgen
Amgen Software Engineer interview with recruiter, hiring-manager, and pending panel stages
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…
Interview experiences · Amperity
Amperity Senior+ Software Engineer Interview Experience — Two Phone Screens, Five Virtual Onsites, and a Company Going All-In on FDE
I don't think anyone's posted about this company here — it's probably too small to be on anyone's radar. The pay HR quoted wasn't great either. Phone Screen 1 Coding: given a width and height, draw a rectangle in ASCII, with different characters for the border and the interior. Second part: draw a series of rectangles on one canvas, and handle overlap plus rectangles that go outside the canvas. I…
Interview experiences · Amperity
Amperity Software Engineer Interview Experience — Long Loop, Good Rounds, Then Silence
This company's interview process is seriously long and miserable. The HR keeps calling you without any heads-up, which feels like harassment. After the interviews they disappear for no reason, even though every round went well. My guess is that they do a back-channel background check behind your back. One of the interviewers is close with a PE in my org, so they probably went and asked him. Our P…
Interview experiences · Amplitude
Amplitude Software Engineer Interview Experience — OA, Phone Screen, Four Onsite Rounds, Then a Final Manager Chat
OA: Write a function to validate a group of employees according to a set of rules. Each employee can have a group of sub-employees under them, so each sub-employee also needs to be validated. Phone Screen: Add a new rule to the code from the OA, to validate whether there is a cycle in the employee list. Onsite (4 rounds): Implement a Snake game. Need to handle keyboard input (up/down/left/right m…
Interview experiences · An applied AI
An applied AI Software Engineer Interview Experience: clear recruiter handoff to hiring manager
The process for the Software Engineer role began with a straightforward recruiter screen. It was easy and focused on my background and whether I seemed like a fit. The communication was clear about what would come next. I then scheduled a hiring-manager round. The flow felt organized and respectful, and the timeline and coordination were timely. I appreciated that the recruiter explained the purp…
Interview experiences · An applied AI
An applied AI Software Engineer Interview Experience: Invitation promised, then rejection email
A recruiter told me I was moving forward and that an invitation for the first interview was coming. Before that, they sent questions in advance, and I answered everything. As far as I knew, none of those responses was a problem. The process then ended with a rejection email that gave no explanation or feedback. That lack of communication was the hardest part, especially because I had been told to…
Interview experiences · An applied AI
An applied AI Software Engineer interview: hostile and confusing interview conduct
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…
Interview experiences · An applied AI
An applied AI Software Engineer interview: rushed EV charging design discussion
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…
Interview experiences · An applied AI
An applied AI Software Engineer interview: TCP, TLS, and system design
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…