AMD software engineer interviews vary. One candidate reports a technical round on Linux `ps` output, Python scripting and ML, plus an HR round. Another reports five onsite rounds on repo navigation, coding, API design and debugging.
$136K
Avg. Base Comp
$152K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
AMD software engineer interviews do not follow one script, and candidate reports differ sharply in format. Neither account centers on trick algorithms. Both lean on practical engineering skill.
One candidate, who came in with an AI/ML background, describes two rounds: a technical round and an HR round. The technical round included a four-part Linux question built on raw ps output. Each subpart asked for a specific piece of information, such as how much memory a given process consumed. The candidate also faced ML theory and coding questions where interviewers had specific answers in mind. They found the emphasis on Linux and Python scripting heavier than expected. If your background is ML-focused, do not assume the loop will stay in that lane. Practice reading process listings field by field and writing small Python scripts that pull values out of raw text.
Another candidate describes five onsite technical interviews of about an hour each. The first was an open-source exercise: given a repository, explain how you would explore it and understand its structure. Another was a simple hashmap coding problem with discussion of past experience. A third covered system and API design for something that works across Windows, Linux and Mac without per-platform changes. The last was debugging and explaining an unfamiliar piece of code, which the candidate found the hardest. One interviewer also asked how a transformer works in detail. This candidate did not receive an offer.
Prepare for resume and project depth as well, since the second candidate faced project questions throughout the loop. Be ready to go deep on everything you list and to talk through design tradeoffs. Practice reading someone else's code aloud rather than only solving clean coding prompts.
Synthesized from 19 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Amd process.
I interviewed for a Software Engineer role at AMD in a single technical round conducted virtually. The interview was scheduled for about an hour and included a panel of two engineers from the hiring team. They started by asking about my background and technical skills, which took up maybe the first 15 minutes or so. After that, we dove into the technical questions. I was asked to identify the logic function that a particular circuit performs, which required understanding digital logic and being able to trace through gates and signals. Then they walked me through code for a finite state machine and had me explain what was happening at each state transition. The third major topic was timing in digital design — specifically setup time, hold time, and propagation delay. These questions required both theoretical knowledge and practical understanding of how timing constraints work in real hardware. The interviewers were direct and technical, and they seemed to be evaluating whether I could think through hardware problems methodically. The whole experience felt very focused on whether I understood the fundamentals of digital design and could communicate my reasoning clearly.
Prep tip from this candidate
Deep dive into digital logic fundamentals before your interview — specifically circuit analysis, FSM design, and timing concepts like setup/hold time and propagation delay. These weren't algorithm questions but rather hardware-focused technical knowledge, so make sure you can trace through circuits and explain state machines with confidence.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Amd
Migrating a social network's data from a document database to a relational database for better data metrics
| Question | |
|---|---|
| Transformer Encoder Layer | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Find the Missing Number | |
| Random SQL Sample | |
| Prime to N | |
| Upsell Transactions | |
| Get Top N Frequent Words | |
| Scrambled Tickets | |
| Maximum Profit | |
| Size of Joins | |
| Paired Products | |
| The Brackets Problem | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Recurring Character | |
| Detecting ECG Tachycardia Runs | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| Integer to Roman | |
| Sum to N | |
| Cyclic Detection | |
| Find the First Non-Repeating Character in a String | |
| Twenty Variants | |
| Bagging vs Boosting | |
| Equivalent Index | |
| Google Maps Improvement | |
| Completed Shipments |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a technical round with a four-part Linux question on `ps` output, such as how much memory a given process consumed. It also included ML theory and coding questions where interviewers wanted specific answers, and a heavy emphasis on Python scripting. Practice extracting values from raw command output.
The same candidate reports an HR round as the second of two rounds in their process. No details of its content were shared, so prepare a concise summary of your background and projects.
Another candidate reports five onsite interviews of about an hour each. They covered exploring an open-source repository, a simple hashmap problem with experience discussion, cross-platform system and API design, and debugging and explaining existing code. Resume and project questions came up throughout, and one interviewer asked how a transformer works.
