Real, anonymous reports from people who interviewed for Software Engineer at AMD, newest first and distilled into what to expect across the loop.
My first round was mostly DSA, with two medium LeetCode-style questions focused on strings and arrays. The main thing I felt the interviewer was looking for was careful handling of edge cases, not just getting to a working “happy path” solution. The pace was steady, and the conversation felt supportive—when I got stuck, the interviewer helped nudge me back toward the right direction.
The process started with a hiring-manager style first conversation where I talked through what I had been working on day to day, and we went deep on my past experience. After that, I moved into a panel format and the loop turned more technical and problem-solving focused. I ended up doing four rounds total, with panels that felt like they each had a couple interviewers, and the questioning mix was a blend of technical problems and scenario-style problem solving.
The interview process typically begins with a recruiter call followed by a behavioral interview with the hiring manager, focusing on past experiences and alignment with the role. Candidates should prepare to discuss their background in detail and connect it to the job requirements.
Candidates can expect a technical coding interview that includes data structures and algorithms (DSA) questions, often in a LeetCode-style format, with a focus on edge cases and practical problem-solving. It's important to demonstrate clear reasoning and handle follow-up questions effectively.
Subsequent rounds often involve panel interviews with multiple interviewers, emphasizing technical depth across various topics such as systems knowledge, C/C++ coding, and hardware integration. Candidates should be prepared for in-depth discussions and scenario-based problem-solving.
Candidates may face system design questions that require both high-level and low-level design thinking, as well as practical implementation discussions. It's crucial to articulate design choices and reasoning clearly, as well as to be prepared for dynamic programming questions.
Throughout the process, interviewers assess not only technical skills but also how well candidates communicate their thought processes and fit within the team. Candidates should be ready to explain their reasoning and approach to problem-solving in a collaborative manner.
Candidates have reported mixed experiences regarding follow-up communication and feedback after interviews, with some feeling left in the dark. It's advisable to seek clarity on next steps and be prepared for potential delays in receiving updates.