AMD · Phone screen → Onsite
In processAMD Intern / Co-op OA / Interviews by Role through Oct 2026: 18 Experiences (Part 1 :)
Note: This is the most complete collection of interview information I could find in this round of searching. If friends need more information in the future, I may start another round of research. Good luck with your interviews! — 11-02-2026 (jane)
In this series
- Part 1 (current): DevOps Engineer; Systems Engineer; Embedded Firmware Engineer; Software Engineer; GPU / Compiler Software Intern; Video Encode/Decode Software Engineer.
- Part 2: ML Software Engineer; Software Custom Engineering; Internship role not specified - MTech; Compiler Engineer; GPU Architecture; Virtualization Validation; Internship role not specified - dual-degree campus.
Coverage: 11 of 18 AMD Intern / Co-op accounts in 6 separate role sections.
Other AMD hiring levels
- Experienced Full-Time: 16 accounts in 3 parts.
- Hiring Level Not Reported: 9 accounts.
- New Grad: 11 accounts in 2 parts.
Historical Xilinx reports
Intern / Co-op at Xilinx covers 2 accounts under their original employer, with separate counts.
Roles in this article
- DevOps Engineer — 1 account.
- Systems Engineer — 1 account.
- Embedded Firmware Engineer — 1 account.
- Software Engineer — 6 accounts.
- GPU / Compiler Software Intern — 1 account.
- Video Encode/Decode Software Engineer — 1 account.
DevOps Engineer
1 account in this role.
What came up
Reported topics: coding tasks; projects or resume; tooling, CI/CD or infrastructure.
01: Vancouver DevOps: Python, GitHub Actions and teamwork
Interview: June 2026 · DevOps Intern · Vancouver, Canada · No offer
About 20–25 minutes of the hour-long interview went to an easy Python coding question and follow-ups. The candidate did not name it.
The rest covered GitHub Actions and CI/CD in previous projects, teamwork and learning. This is a DevOps account, rather than evidence about every SWE internship.
Systems Engineer
1 account in this role.
What came up
Reported topics: OS, memory, architecture or concurrency; projects or resume; GPU, ML or hardware-specific topics.
Questions we found
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Design an AI automation workflow spanning hardware/software | 1 | Reports: 2026-06 (interview) |
02: Systems co-op: hardware communication and an AI workflow
Interview: June 2026 · Systems Engineer Co-op · Markham, Canada · No offer
The one-hour interview moved from the candidate's resume and AI background into hardware communication protocols, motherboard components, and the different capabilities of CPUs and GPUs.
The candidate was also asked to design an AI automation workflow spanning software and hardware. The actual workflow was not described in the account. The linked exercise supplies an explicit device-command workflow and safety assumptions for practice.
Embedded Firmware Engineer
1 account in this role.
What came up
Reported topics: language, runtime or compiler details; coding tasks; OS, memory, architecture or concurrency; projects or resume; GPU, ML or hardware-specific topics.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Count similar/repeated letters (counting rule not shared) | 1 | Reports: Post displayed as 6 months old on 2026-10-30; exact date unavailable |
| Reverse a string | 1 | Reports: Post displayed as 6 months old on 2026-10-30; exact date unavailable |
C/C++ / OS Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| PCIe rates/layers, encodings, hot plug and lane versus link | 1 | Post displayed as 6 months old on 2026-10-30; exact date unavailable |
03: Firmware intern: project circuits, strings and PCIe
Post displayed as 6 months old on October 30, 2026; exact date unavailable · Embedded Firmware Intern · Selected
Round 1 — project deep dive, 75 minutes
The candidate explained the objective, implementation, problems and fixes in an embedded project. They drew Time-to-Digital Converter modules and logic, then discussed changing values or moving blocks.
An 8-bit carry-save adder led to questions about the choice of hybrid full adder, output swing and driving strength.
Round 2 — manager technical interview, 40 minutes
The coding tasks were to count similar or repeated letters in a string and reverse a string, including time and memory costs. The counting convention was not specified in the account; the linked counting exercise explicitly counts occurrences after each letter’s first appearance.
C questions covered static storage, dangling pointers, memory leaks, heap and stack, and malloc, calloc and realloc. They also discussed memory/cache read-write cycles, pipelines, kernels, embedded mutexes and semaphores.
PCIe questions included generation rates, protocol layers, 8b/10b and Gen6 encoding, hot plugging, and the distinction between a lane and a link.
Round 3 — senior manager, 15 minutes
The conversation covered the team, work expectations and what to do before joining.
Software Engineer
6 accounts in this role.
What came up
| Topic | Reports | Most recent report |
|---|---|---|
| Language, runtime or compiler details | 5 of 6 | 2026-01-20 (interview) |
| Projects or resume | 3 of 6 | 2026-01-20 (interview) |
| Coding tasks | 4 of 6 | 2025-08 (interview) |
| GPU, ML or hardware-specific topics | 1 of 6 | 2025-08 (interview) |
| Tooling, CI/CD or infrastructure | 1 of 6 | 2025-08 (interview) |
| OS, memory, architecture or concurrency | 2 of 6 | 2025-01-06 (interview) |
Questions we found
System Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Respond to a GPU training-cluster outage | 1 | Reports: 2025-08 (interview) |
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| LC 1503: Last Moment Before All Ants Fall Out of a Plank | 1 | Reports: 2025-08 (interview) |
| Valid Anagram | 1 | Reports: 2025-01-15 (interview) |
| Two Sum in Python | 1 | Reports: 2025-01-06 (interview); Additional same-company practice history: 2022-06-14 (report date) |
| Implement memcpy in C | 1 | Reports: 2025-01-06 (interview); Additional same-company practice history: 2024-09-12 (report date) |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Why AMD? | 1 | 2025-01-15 (interview) |
| Background, motivation, strengths/weaknesses, a work challenge and five-year plans | 1 | 2024-01-28 (report) |
Language / Runtime Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| Python list comprehensions | 1 | 2025-01-15 (interview) |
| Java abstract class versus interface | 1 | 2024-01-28 (report) |
| Pointers versus references | 1 | 2024-01-28 (report) |
| Functional programming and its advantages | 1 | 2024-01-28 (report) |
| Java GC and generational collection | 1 | 2024-01-28 (report) |
| Python generators | 1 | 2024-01-28 (report) |
Complexity / Parallelism Discussion
| Question | Frequency | All last seen dates |
|---|---|---|
| Discuss finding an array maximum in O(1) time | 1 | 2024-01-28 (report) |
04: Vancouver software intern: explaining the code in a project
Interview: January 20, 2026 · Software Engineering Intern · Vancouver, Canada · Selected
The candidate applied on December 4, 2025, had recruiter contact on January 12, and completed the roughly one-hour final interview on January 20.
They walked through project code and explained design decisions, then answered OOP and Python-fundamentals questions and discussed their resume and teamwork. The individual technical prompts were not shared. The offer was reported on February 15.
05: A GPU-cluster outage and ants on a plank
Interview: August 2025 · Software Engineer Intern · Markham, Canada · No offer
The hour combined technical and behavioral discussion. Alongside previous work and role-related technologies, the interviewer asked what to do when a GPU training cluster goes down. The linked design exercise supplies a Kubernetes GPU control-plane setting for practice; that infrastructure was not established in the account.
The named coding problem was LeetCode 1503, Last Moment Before All Ants Fall Out of a Plank. The account does not add a custom variant.
06: A Markham internship with Valid Anagram
Interview: January 15, 2025 · Software Engineering Intern · Markham, Canada · Selected
The roughly one-hour interview included Valid Anagram, Python list comprehensions and why the candidate wanted to join AMD. The reported offer date was January 22.
07: Two Sum in Python, then memcpy in C
Interview: January 6, 2025 · Software Engineering Intern · Markham, Canada · No offer
This 90-minute technical round paired Two Sum in Python with implementing memcpy in C (byte-copy practice). The source also mentions simple technical/behavioral discussion, without preserving the prompts.
08: Undergraduate SWE intern: language details and project follow-ups
Completed-interview follow-up displayed as 1 year old on October 30, 2026; exact interview date unavailable · Undergraduate Software Engineer Intern
The original post was written before the interview. A later first-person follow-up said the completed interview covered language/OOP details and a project deep dive.
The candidate felt it had gone poorly, but did not report a final recruiting decision or an identifiable coding task. The displayed edit age does not establish when the interview happened.
09: Austin internship: Java/Python fundamentals and an O(1) maximum discussion
Report date: January 28, 2024 · Software internship · Austin, Texas · Selected
One manager interview lasted about an hour: roughly 35 minutes on background and general questions, 15 on technical Q&A and 10 on coding.
The opening covered interest in AMD and the role, strengths and weaknesses, a challenging work situation and five-year plans.
Technical questions covered Java abstract classes versus interfaces, synchronization, pointers versus references, functional programming and its advantages, SDLC, runtime polymorphism, Java garbage collection/generational collection and Python generators.
For coding, the candidate was asked to find an array's maximum in O(1) time. They first mentioned square-root decomposition, then proposed parallel processing of chunks. No processor or work model was supplied, so the account does not establish a correct general constant-time solution.
GPU / Compiler Software Intern
1 account in this role.
What came up
Reported topics: language, runtime or compiler details; coding tasks; OS, memory, architecture or concurrency; tooling, CI/CD or infrastructure.
10: An off-campus GPU/compiler internship process
Report date: January 13, 2026 · GPU software/compiler intern · India
This commenter described their own off-campus process: OA/coding at LeetCode medium-to-hard level, followed by compiler, OS, DSA, C/C++, LLVM and high-performance-computing topics. They did not name an exercise.
The surrounding campus process belonged to other applicants, so it does not fill the gaps in this account.
Video Encode/Decode Software Engineer
1 account in this role.
What came up
Reported topics: language, runtime or compiler details; coding tasks.
11: Video encode/decode internship: C, OOP and bits
Interview: November 2025 · Software Engineering Intern, Video Encode/Decode · Markham, Canada · No offer
The hour-long interview covered C questions, C++ OOP and a bit-manipulation LeetCode task. The exact bit operation was not provided. The work-term label on the card was later than the actual interview date.
In this series
- Part 1 (current)
- Part 2
Comments
0No comments yet — be the first to share what you know.