AMD AI Engineer interview typically runs 4 rounds: hiring manager and technical interviews. The process took about a month and was marked by last-minute scheduling and weak follow-up.
$108K
Avg. Base Comp
$200K
Avg. Total Comp
4
Typical Rounds
3-6 weeks
Process Length
Our candidates report that AMD’s AI engineering interviews can feel genuinely substantive once you’re in the room: the engineers are engaged, the questions are grounded in real GPU and validation work, and the conversation tends to reward people who can speak concretely about performance tradeoffs rather than just broad AI concepts. That’s the clearest signal we’ve seen — technical depth matters more than polish here, and the strongest impressions come from candidates who can connect their experience to AMD-specific hardware realities.
At the same time, a recurring theme is that the candidate experience can be uneven on the coordination side. In one case, the hiring manager missed the first meeting, scheduling shifted with very short notice, and follow-up communication essentially stopped after interviews were complete. That tells us something important about the process: candidates may be evaluated seriously on the technical side, but the experience can still feel opaque and inconsistent. We’ve seen that the people who do best are the ones who stay flexible without losing track of their own process, because at AMD, silence after strong interviews is not always a reliable signal — and that ambiguity is part of the experience candidates should be ready for.
Synthesized from 1 candidate report 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.
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
How would you build and justify the components of a Transformer encoder layer in PyTorch for large-scale text data?
| Question | |
|---|---|
| LRU Cache 1 | |
| Relational Migration | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Paired Products | |
| Upsell Transactions | |
| Hurdles In Data Projects | |
| Prime to N | |
| Size of Joins | |
| Get Top N Frequent Words | |
| Find the Missing Number | |
| Random SQL Sample | |
| Unique Work Days | |
| Closed Accounts | |
| Over-Budget Projects | |
| Longest Increasing Subsequence | |
| The Brackets Problem | |
| Maximum Profit | |
| Cyclic Detection | |
| Exam Scores | |
| Detecting ECG Tachycardia Runs | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| Integer to Roman | |
| Sum to N | |
| Equivalent Index | |
| Bucket Test Scores | |
| Cumulative Sales Since Last Restocking | |
| Bagging vs Boosting |
Synthesized from candidate reports. Individual experiences may vary.
The process begins with recruiter outreach and scheduling, but candidates may need to be flexible because timing can be last-minute. In this case, interview dates were moved around with short notice, including messages sent after 5 PM for the next day.
The first substantive conversation is with the hiring manager, though one candidate reported the initial meeting was missed and had to be rescheduled. This round appears to focus on role fit and setting the tone for the rest of the process.
Candidates then go through multiple technical rounds with engineers. These interviews were described as substantive and knowledgeable, with a strong focus on AI/ML and GPU performance validation topics relevant to the role.
After the interviews, the recruiter may provide verbal updates, but candidates should not assume a quick response. In this experience, the candidate received no follow-up for several weeks and ultimately learned the application status had changed in the portal without a direct rejection message.