AMD interviews are a screening call followed by two to four technical interviews and a manager or HR round, mostly virtual on Microsoft Teams. Hardware roles (design verification, RTL design, silicon design) are tested on digital design, computer architecture, Verilog and SystemVerilog, UVM and bus protocols; software roles are tested on C++, data structures, operating systems and debugging, sometimes down to assembly. Fresher and campus hiring in Bengaluru and Hyderabad usually adds an online test of MCQs and coding before the technical rounds.
The questions stay close to the job description. A 2025 US verification candidate said every question was on digital design, bus protocols and UVM, and a 2025 Hyderabad candidate said the interview focused on VLSI, digital electronics and the role’s own requirements.
AMD interview process
- Online test (India campus and some roles)Varies
- Screening call~30 min
- Technical round 1~45-60 min
- Technical round 2~45-60 min
- Additional technical rounds~45-60 min each
- Manager / HR~30 min
| Round | Duration | What it tests |
|---|---|---|
| Online test (India campus and some roles) | Varies | MCQs on OS, C++ and OOP; coding (DP, segment trees) |
| Screening call | ~30 min | Resume, basics, role fit |
| Technical round 1 | ~45-60 min | Core fundamentals: digital design or C++ and DSA |
| Technical round 2 | ~45-60 min | Deeper role topics: UVM, architecture, advanced C++, debugging |
| Additional technical rounds | ~45-60 min each | Team-specific: bus protocols, timing, assembly, puzzles |
| Manager / HR | ~30 min | Projects, motivation, logistics |
AMD interview questions with answers
Q: Design a divide-by-3 clock with a 50% duty cycle.
A mod-3 counter on the rising edge gives a divide-by-3 output with a 33% duty cycle. To get 50%, generate one signal that is high for one and a half cycles using both edges: build the mod-3 counter on the rising edge, create a signal A that is high when the count is 0, create a copy B of A clocked on the falling edge, and OR them. A and B overlap by half a cycle, so the result is high for 1.5 of every 3 input cycles. Mention that mixing clock edges complicates timing analysis and that many teams prefer a PLL or a clock generator block for production designs.
Q: Explain setup and hold time and what happens when they are violated.
Setup time is how long data must be stable before the capturing clock edge; hold time is how long it must stay stable after. A setup violation means the path is too slow for the clock period, fixed by reducing logic depth, pipelining or lowering frequency. A hold violation means data changes too soon after the edge, usually from a short path or clock skew, fixed by adding delay on the data path; frequency does not help. Either violation can put the flip-flop into a metastable state where the output settles unpredictably, which is why signals crossing clock domains go through two-flop synchronizers.
Q: Walk through the components of a UVM testbench.
A sequence generates transaction objects; the sequencer arbitrates sequences and hands items to the driver through the seq_item_port; the driver converts transactions into pin-level activity on the virtual interface. A monitor watches the interface passively and broadcasts observed transactions through an analysis port to a scoreboard, which compares them against a reference model, and to coverage collectors. Driver, sequencer and monitor are grouped into an agent, which can be active or passive. The environment holds agents and scoreboards, and the test configures the environment through the config database and starts sequences. Expect follow-ups on phases (build, connect, run) and on objections that keep the run phase alive.
Q: How would you write a driver for a bus that allows multiple outstanding transactions?
Split request and response handling into two parallel threads. The request thread gets items from the sequencer, drives the address phase, tags each item with an ID, stores it in an associative array keyed by ID, and moves on without waiting for the response, up to the allowed outstanding limit. The response thread watches the response channel, looks up the matching item by ID, fills in the response data and calls item_done or puts the response back to the sequence. Handle out-of-order responses if the protocol allows them, and add a timeout check for requests that never complete. This is the shape of the APB outstanding-transaction question reported from Bengaluru, though plain APB itself allows only one transfer at a time, so clarify the protocol variant first.
Q: What types of cache are there, and how does a cache lookup work?
Caches are direct-mapped (each address maps to one line), fully associative (any line) or set-associative (one set of N lines). An address splits into tag, index and offset: the index selects the set, the tags in that set are compared in parallel, and on a hit the offset selects bytes within the line. On a miss the line is fetched and a victim is chosen by a policy such as LRU. Write-back caches mark lines dirty and write them on eviction; write-through caches write to the next level immediately. A 2025 Hyderabad candidate who joined as a fresher reported cache types and cache operation questions.
Q: What does virtual mean in C++, and how is it implemented?
A virtual function is resolved at run time based on the object’s dynamic type. Compilers implement this with a vtable per class holding function pointers, and a hidden vptr in each object pointing to its class’s vtable; a virtual call loads the vptr, indexes the table and calls through the pointer. Destructors in a base class meant for polymorphic use must be virtual, or deleting through a base pointer skips the derived destructor. Pure virtual functions make a class abstract. Expect follow-ups on object size with a vptr, calling virtual functions in constructors, and the cost of virtual calls in hot loops.
Q: Move all zeros in an array to the end while keeping the order of the other elements.
Keep a write index starting at 0. Scan the array; for each non-zero element, write it at the write index and increment it. After the scan, fill the rest of the array from the write index with zeros. This is O(n) time and O(1) extra space. A swap-based version swaps each non-zero element with the position at the write index, which avoids the second pass and minimizes writes when there are few zeros. The 2025 Santa Clara intern was asked to run the optimized version, so test it on all zeros, no zeros and a single element.
AMD interview questions by role
| Role | Reported questions and topics |
|---|---|
| Design verification | Digital design, bus protocols, UVM (US, 2025); testbench architecture, test planning, APB outstanding-transaction driver in UVM (Bengaluru, 2023); computer architecture, Verilog and SystemVerilog, Python, C or C++ (Bengaluru, 2024) |
| Hardware engineer | Digital design, computer architecture, clock divider and multiplier circuits (Hyderabad, 2025); timing analysis (US, 2025); how a transistor works (Austin, 2025) |
| Software engineer | C++ basics and advanced C++, DSA, puzzle, linked lists, stacks, code debugging (2025); OS and C++ OOP MCQs, DP and segment tree (Bengaluru OA, 2025) |
| Software intern | Move Zeroes, Group Anagrams, puzzles, research project questions (Santa Clara, 2025); debugging assembly code (Austin, 2025); OOP and OS (Hyderabad, 2025) |
| Experienced engineer, India | VLSI and digital electronics, questions on the job description and current role (Hyderabad, 2025); DSA, memory, cache types and how caches work, linked lists, digital electronics (Hyderabad, 2025) |
AMD design verification interview
AMD posts design verification roles in Santa Clara, San Jose, Austin, Boxborough, Bangalore and Hyderabad, from 2027 intern and co-op roles to leads. AMD’s verification postings ask for Verilog, SystemVerilog and UVM, C and C++, and scripting in Python, Perl or TCL; the day-to-day work is building directed and random tests, debugging failures with RTL and firmware engineers, and closing functional and code coverage.
The interviews follow the same list. An August 2025 US candidate said everything was based on digital design, bus protocols and UVM, with a basic screen and deeper follow-up rounds. An October 2023 Bengaluru hire was asked about testbench architecture and test planning and had to write an APB outstanding-transaction driver function in UVM; the process took about a week. A 2024 Bengaluru referral’s phone screen covered advanced computer architecture, Verilog and SystemVerilog, digital design and Python, C or C++.
Common topics
- UVM components: driver, monitor, sequencer, scoreboard, agent, and how sequences reach the driver
- SystemVerilog constraints, randomization and functional coverage
- Bus protocols such as APB and AXI: handshakes, outstanding transactions, ordering
- Writing a test plan for a new feature and deciding what to cover with directed versus random tests
- Debugging a failing test to root cause in RTL or in the testbench
AMD hardware and RTL design interview
Hardware engineer and RTL design candidates get digital logic and architecture questions. An August 2025 Hyderabad hardware engineer had two technical rounds totaling about 1.5 hours on digital design, computer architecture, and clock divider and multiplier circuits; the interviewers were relaxed and focused on basic and some intermediate concepts. An April 2025 US engineer report mentions a timing analysis question, and a November 2025 Austin candidate was asked to explain what a transistor is and how it works.
Common topics
- Clock dividers (divide by 2, 3, odd ratios with 50% duty cycle) and clock multipliers
- Setup and hold time, static timing analysis, metastability and synchronizers
- FSM design, FIFOs and clock domain crossing
- Cache organization, pipelines and hazards
AMD software engineer interview
AMD software roles cover drivers, compilers, firmware, GPU libraries and tools, so the language is usually C++. A Software Engineer II candidate in May 2025 came in through a referral and had four virtual rounds on Teams: C++ questions in the screen, DSA plus a puzzle, advanced C++, then C++ with linked lists, stacks and code debugging. A Santa Clara software intern in April 2025 had a screen, two technical assessments with algorithms, puzzles and DSA (Move Zeroes and Group Anagrams, optimized and run), and behavioral interviews about their research project. An Austin software intern in July 2025 had a 30-minute behavioral interview and a technical interview where they debugged assembly code.
AMD online assessment: quick answers
| Question | Answer |
|---|---|
| Does every AMD role have one? | No. Most US reports start with a call. India campus and fresher roles more often start with a test. |
| What is in it? | A September 2025 Bengaluru software OA had MCQs mostly on OS and C++ OOP, and two coding problems: an easy DP and a segment tree. |
| Is there one for hardware roles? | Reports mention a written or online test for some Hyderabad intern and campus roles before the technical round. |
| Which language? | C or C++ is expected for software roles; verification roles use SystemVerilog plus a scripting language. |
| How hard is the coding? | Easy to medium, with occasional advanced data structures such as segment trees. |
Who does well in AMD interviews
Good fit: You can draw a circuit or a testbench on a whiteboard and explain each block, you know one bus protocol in detail, and you read the job description closely because AMD interviewers ask from it. Software candidates who are strong in C++ internals and debugging do better than those who prepared only LeetCode.
Harder path: You list SystemVerilog or UVM on your resume but cannot write a driver or a constraint from memory. Hyderabad and US candidates in 2025 described rounds that went straight into these details.
AMD India: Bengaluru and Hyderabad hiring
AMD’s India engineering sites in Bengaluru and Hyderabad hire for CPU and GPU verification, RTL design, FPGA prototyping, SoC validation, physical design and software. Its careers site in late 2026 listed roles such as CPU Design Verification Engineer in Bangalore, and RTL Design Engineer, FPGA Prototyping Engineer, SoC Validation Engineer and Hardware-Software Integration and Verification Engineer in Hyderabad. Many listed India openings are senior or lead positions; fresher hiring runs through campus drives and intern programs.
AMD interview questions in India
- Hyderabad hardware engineer (August 2025, offer): Two technical rounds, about 1.5 hours in total, on digital design, computer architecture and clock divider and multiplier circuits.
- Hyderabad senior software engineer (April 2025, accepted, joined as a fresher): Basic DSA, memory, types of cache and how a cache works, linked lists, and digital electronics.
- Hyderabad senior software engineer (August 2025): A tough set of rounds with many VLSI and digital electronics questions plus questions on the job description and the candidate’s current work.
- Bengaluru software engineer OA (September 2025): MCQs mostly on OS and C++ OOP; coding: one easy DP and one segment tree.
- Hyderabad intern (June 2025): A test, a technical round on OOP and operating systems, and an HR round.
- Hyderabad design verification (April 2023, accepted): Two one-hour technical rounds and an HR round.
AMD India pay
AMD’s India postings do not list pay ranges, and no verified source for AMD India fresher packages was found. Ask the recruiter for the band, and compare written offers rather than forwarded figures.
A four-week AMD prep plan
- Week 1: Digital design: counters, clock dividers, FSMs, FIFOs, setup and hold, CDC. Draw each one and explain it aloud.
- Week 2 (verification): Write a small UVM environment for a simple bus: driver, monitor, scoreboard, one constrained-random sequence and a covergroup. Week 2 (software): C++ internals: virtual functions, smart pointers, move semantics, memory layout.
- Week 3: Computer architecture: caches, pipelines, hazards, branch prediction. Software candidates add OS topics and 15 medium DSA problems, including one segment tree.
- Week 4: Mock interviews driven by the job description: underline every tool and topic in the posting and prepare one example for each. Prepare behavioral stories for AMD’s five key behaviors.
AMD pay in the US
AMD’s US postings include base pay ranges. Ranges listed on AMD’s careers site in 2026:
| Posting | Location | Base range |
|---|---|---|
| Design Verification Engineer | Santa Clara, CA | $119,000-$170,000 |
| CPU Design Verification Engineer | Santa Clara, CA | $124,040-$177,200 |
| Design Verification Engineer - Methodology (February 2026) | Austin, TX | $171,200-$256,800 |
| Software Development Engineer | Santa Clara, CA | $127,400-$182,000 |
| Linux Kernel Software Engineer | Austin, TX | $101,500-$145,000 |
| 2027 Undergrad Software Engineer Intern/Co-op | Santa Clara and San Jose, CA | $66,560-$80,080 a year, annualized |
| 2027 Undergrad Software Engineer Intern/Co-op | Austin, TX and other sites | $60,320-$73,840 a year, annualized |
| 2027 Masters Software Engineer Intern/Co-op | Santa Clara and San Jose, CA | $104,000 a year, annualized |
Levels.fyi’s self-reported US medians for AMD software engineers, including stock and bonus, are about $156,000 at L5, $189,000 at L6, $240,000 at L7 and $332,000 at L8.
Frequently asked questions about AMD interviews
What is the AMD interview process?
A screening call, then two to four technical interviews, usually virtual on Microsoft Teams, then a manager or HR round. Hardware candidates are tested on digital design, computer architecture, Verilog and SystemVerilog and UVM; software candidates on C++, data structures, operating systems and debugging. Some India roles and campus drives start with an online test.
What AMD interview questions are asked for design verification?
Digital design, bus protocols and UVM in a 2025 US report; testbench architecture, test planning and writing an APB outstanding-transaction driver function in UVM in an October 2023 Bengaluru report; and computer architecture, Verilog and SystemVerilog, digital design and Python, C or C++ in a 2024 Bengaluru phone screen.
What AMD interview questions are asked for software engineers?
C++ fundamentals and advanced C++, data structures such as linked lists and stacks, code debugging, and a puzzle, according to a May 2025 Software Engineer II candidate with four Teams rounds. A 2025 Santa Clara intern was asked Move Zeroes and Group Anagrams and had to run optimized code, and a 2025 Austin intern debugged assembly code.
Does AMD have an online assessment?
For some roles, mostly in India. A September 2025 Bengaluru software engineer OA had MCQs on operating systems and C++ object-oriented programming plus two coding problems, one easy dynamic programming and one segment tree. A June 2025 Hyderabad intern had a test before the technical and HR rounds. Most US reports start with a call instead.
How much does AMD pay in the US?
AMD’s US postings list base ranges. In 2026, a Santa Clara Design Verification Engineer posting listed $119,000-$170,000, a CPU Design Verification Engineer in Santa Clara $124,040-$177,200, a Software Development Engineer in Santa Clara $127,400-$182,000, and a Linux Kernel Software Engineer in Austin $101,500-$145,000. 2027 undergraduate software intern postings listed $60,320-$80,080 a year annualized depending on location.
Does AMD hire in India?
Yes, mainly in Bengaluru and Hyderabad. AMD’s careers site lists hardware roles there such as CPU Design Verification Engineer in Bangalore and RTL Design Engineer, FPGA Prototyping Engineer and SoC Validation Engineer in Hyderabad, along with software roles. India postings do not show pay ranges.
What is the AMD interview process in Hyderabad and Bengaluru?
Usually an online test for freshers and campus candidates, two technical rounds of about an hour each, and an HR round. An August 2025 Hyderabad hardware engineer had two technical rounds totaling about 1.5 hours on digital design, computer architecture and clock divider and multiplier circuits, and received an offer.
What are AMD’s culture values?
AMD’s careers page lists five key behaviors: Push the Limits, Drive Excellence, Be Direct and Humble, Collaborate Deeply, and Be Inclusive, Always. AMD job postings describe the culture as striving for execution excellence while being direct, humble, collaborative and inclusive.
How long does the AMD hiring process take?
It varies by team. An October 2023 Bengaluru design verification hire went from application to offer in about a week, while a 2025 Austin intern described a disjointed process with unusual follow-up times because individual teams, not HR, set the pace.
Which languages and tools does AMD expect for verification roles?
AMD’s design verification postings list Verilog, SystemVerilog and UVM, C and C++, and scripting in Python, Perl or TCL. An Austin methodology posting adds formal verification, make flows, Ruby and shell scripting, and a Bangalore posting adds assembly tests and JTAG debugging.
Sources
- AMD Careers: culture and key behaviors
- AMD Careers job search (postings and US pay ranges)
- AMD: Design Verification Engineer - Methodology posting, Austin, February 2026 (copy)
- Levels.fyi: AMD software engineer pay by level
- Taro: engineer (verification), United States, August 2025
- Taro: software engineer II, May 2025
- Taro: software engineer intern, Santa Clara, April 2025
- Taro: software engineer intern, Austin, July 2025
- Taro: hardware engineer, Hyderabad, August 2025
- Taro: senior software engineer, Hyderabad, April 2025
- Taro: senior software engineer, Hyderabad, August 2025
- Taro: software engineer, Bengaluru, September 2025
- Taro: design verification engineer, Hyderabad, April 2023
- Bengaluru design verification (2023, 2024), Hyderabad intern (June 2025), US timing and transistor questions (2025): Glassdoor and Taro AMD interview reviews