Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

15 stories

Likes earn the author +10 XP for the first 3 likes each day

AMDSoftware Engineer
Sep 2026

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…

OfferOnsite0
AMDSoftware Engineer
Reported Jul 2026

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…

OfferTechnical Screen0
AMDSoftware Engineer
Reported Jul 2026

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…

HR Screen0
AMDSoftware Engineer
Reported Jul 2026

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…

OfferTechnical Screen0
AMDSoftware Engineer
Reported Jul 2026

Software Engineer at AMD: computer architecture and UVM questions

I went through a technical-focused interview that leaned heavily into computer architecture and verification. I was asked about UART, SPI, and I2C, including how those topics connect to the bigger picture. We also covered object-oriented programming and verification languages and concepts such as UVM. The discussion then moved to bus protocols including APB, AHB, and AXI, followed by coverage, as…

0
AMDSoftware Engineer
Reported Jul 2026

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…

Technical Screen0
AMDSoftware Engineer
Reported Jul 2026

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…

Technical Screen0
AMDSoftware Engineer
Reported Jul 2026

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…

HR Screen0
AMDSoftware Engineer
Reported Jul 2026

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…

Rejected0
AMDProject Manager
Reported Jul 2026

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…

Other0
AMDSoftware Engineer
Reported Jul 2026

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…

Technical Screen0
AMDSoftware Engineer
Reported Jul 2026

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…

RejectedTechnical Screen0
AMDSoftware Engineer
Reported Jun 2026

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…

Offer0
AMDSoftware Engineer
Reported Jun 2026

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…

Technical Screen0
AMDSoftware Engineer
Reported Jun 2026

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…

OfferHR Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP