TheJobsMap
AMD logo

AMD interview questions

From 8 candidate accounts, updated Oct 12, 2026

Candidate accounts
8
Rounds on average
2.5
Fewest and most rounds
1 to 5
Open roles at AMD
6

How the loop works

AMD runs a resume-and-project-centric loop rather than a heavy algorithmic gauntlet: a recruiter or manager screen followed by two to five technical conversations that live mostly inside whatever the candidate claims on their CV. Hardware and verification candidates get digital-design fundamentals, Verilog/SystemVerilog, timing and protocol questions plus a deep tour of their own project. Software, firmware and kernel candidates get C, Linux internals, computer architecture and one or two moderate coding problems. India campus and lateral hiring (Bengaluru/Hyderabad) dominate the public writeups, with a smaller stream of US intern accounts.

These 8 writeups cover design verification, digital design, silicon design and other roles, India-heavy, some US (Austin). 5 of them were posted under a forum handle, so we could not verify the authors’ identities.

See open roles at AMD

Interview experiences at AMD

Software Engineering Intern (9-month campus internship)

Not selected

Internship. 3 rounds. Shared by Gautham Shekar on blog, 2021-06-29

  1. 1Resume shortlistPhone screenNo test was administered: AMD screened the whole eligible M.Tech batch on resume alone and invited a small fraction to interview.Covered: Resume deep-dive
  2. 2Technical interviewTechnicalThe interviewer walked through the candidate's machine-learning project layer by layer, then switched to a short C snippet with a deliberate memory-allocation mistake and two small scripting exercises.Covered: Past projects, Deep learning, Pointers, Python, Recursion
  3. 3Second technical interviewTechnicalA second interviewer joined immediately after the first and probed project conclusions and future work, everyday Linux troubleshooting commands, and C fundamentals such as storage classes and sizing a type without sizeof.Covered: Past projects, Linux commands, Data structures & algorithms, Arrays & strings, Operating systems

Software Engineering Intern (Austin, Texas)

Received an offer

Internship. 1 round. Shared by Akash Kumar on blog, 2024-01-28

  1. 1Hiring manager interviewHiring managerA single hour-long manager conversation split roughly into resume and motivation questions, a block of language and OOP theory (abstract classes vs interfaces, synchronization, garbage collection, generators), and one short coding problem where the expected answer was parallelising the scan rather than a clever sequential trick.Covered: Behavioral, Resume deep-dive, OOP, Concurrency, Arrays & strings

What AMD is hiring for now

6 open roles in our index.

Most-posted roles

  • 171303_Power & Performance System Engineer (171303)1
  • 162443 Power & Performance System Engineer Lead (162443)1
  • 163106 MTS Systems Design Eng. (163106)1
  • 163107 MTS Systems Design Eng. (163107)1
  • 175701 Firmware Engineer (UEFI/BIOS firmware) (175701)1
  • 172203 SMTS Platform Application Engineer(NB/DT/WorkStation) (172203)1

Top locations

  • Taipei6

Open roles at AMD

See all 6 roles

AMD interviews: FAQ

What is the interview process like at AMD?
AMD runs a resume-and-project-centric loop rather than a heavy algorithmic gauntlet: a recruiter or manager screen followed by two to five technical conversations that live mostly inside whatever the candidate claims on their CV. Hardware and verification candidates get digital-design fundamentals, Verilog/SystemVerilog, timing and protocol questions plus a deep tour of their own project. Software, firmware and kernel candidates get C, Linux internals, computer architecture and one or two moderate coding problems. India campus and lateral hiring (Bengaluru/Hyderabad) dominate the public writeups, with a smaller stream of US intern accounts.
What topics does AMD test in interviews?
Commonly reported topics include Past projects, Resume deep-dive, Digital design, Verilog, SystemVerilog, UVM.

These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.