Real, anonymous reports from people who interviewed for Software Engineer at Advanced Micro Devices, newest first and distilled into what to expect across the loop.
Get your personalized Advanced Micro Devices Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with a recruiter screen where the conversation covered logistics like my location and sponsorship, and I got a quick walkthrough of the interview process. That was followed by multiple technical rounds with engineers and then a hiring-manager touchpoint. Across the loop, the overall vibe was friendly and I felt like the interviewers were trying to understand both how I had built things before and how I’d troubleshoot in practice.
A lot of the discussion centered on my past projects and how that translated into low-level work. I talked through Linux systems and embedded-style debugging, and we touched computer networking fundamentals. In the technical rounds, I also ran through a coding exercise focused on basic data structures and algorithms, and I was asked medium-level LeetCode-style problems involving strings and arrays—especially around getting edge cases right. Even when questions were straightforward, they pushed for clarity and correctness rather than just surface-level answers.
3 weeks ago
Average Positive Bangalore Rural
My process leaned heavily into hardware and verification fundamentals. After an initial recruiter-style step, I moved into a technical session with multiple people where the questions were clearly meant to probe my depth rather than just my familiarity. A lot of it felt like RTL-to-system thinking: I was asked about implementation details and how concepts connect across the flow.
In the interviews, we covered a mix of topics including aspects of verification like UVM, coverage, and assertions, plus core architecture and interface knowledge. I remember discussing buses and protocols like UART, SPI, and I2C, and even when the questions weren’t framed as “coding,” they still required precise reasoning. There were also focused items like static timing analysis, and I was asked to explain how FPGA-style implementation comes together.
1 month ago
Difficult Neutral Austin, TX
My interview started like a quick alignment with the hiring manager, where I walked through my day-to-day experience and what I’d worked on before. Th…
2 months ago
Average Positive San Jose, CA
I went through an HR screening where the recruiter covered logistics and gave me a basic map of how the interview loop would work. After that, I had a…
2 months ago
Difficult Positive Hyderābād
I ran into an interview format that felt very design-and-problem-focused from the start. They asked me to frame things at the level of HLD and LLD, an…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter & Initial Screening
The interview process typically begins with a recruiter call that covers logistics, availability, and a brief overview of the interview structure. This initial step is generally straightforward and sets the tone for the subsequent interviews.
Recruiter callLogisticsInterview overview
Technical Rounds & Problem-Solving
Candidates can expect multiple technical interviews focusing on coding, algorithms, and system design, often involving LeetCode-style problems and real-world scenarios. The emphasis is on reasoning and clarity rather than just correct answers.
CodingAlgorithmsSystem design
Behavioral & Managerial Interviews
Behavioral interviews with hiring managers are common, focusing on past experiences, conflict resolution, and leadership moments. These discussions often delve into how candidates align with team values and project goals.
BehavioralLeadershipCultural fit
Technical Depth & Specificity
Interviews often probe deep into technical knowledge, especially in areas relevant to the role, such as hardware, verification, and low-level programming concepts. Candidates should be prepared for detailed questions that require thorough understanding.
Technical depthVerificationLow-level programming
Interview Experience & Communication
Overall, candidates report a mix of positive and negative experiences regarding interviewer demeanor and communication clarity. Some found the process friendly and engaging, while others noted disorganization and lack of follow-up.
Interview experienceCommunicationFeedback
Process Length & Follow-Up
The interview process can vary in length, typically spanning a few weeks, but some candidates experienced delays and lack of communication, leading to frustration. Timely follow-up is not guaranteed, and candidates should be prepared for potential wait times.