AMD · OA → Phone screen → Onsite
In processAMD New Grad OA / Interviews by Role through Oct 2026: 11 Experiences (Part 2 :)
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: Software Engineer - GPU systems; C++ Software Engineer - Graphics; Software Development Engineer - ROCm/kernel; Applied Research Scientist; SDK Developer — ROCm Support; SDE2 - MTech campus hiring; Software Development Engineer - GPU functions; Graphics Profiler Software Engineer.
- Part 2 (current): Firmware Engineer; Hardware role — exact title not reported; Full-stack Software Engineer - DevOps team.
Coverage: 3 of 11 AMD New Grad accounts in 3 separate role sections.
Other AMD hiring levels
- Experienced Full-Time: 16 accounts in 3 parts.
- Hiring Level Not Reported: 9 accounts.
- Intern / Co-op: 18 accounts in 2 parts.
Historical Xilinx reports
New Grad at Xilinx covers 1 account under its original employer, with separate counts.
Roles in this article
- Firmware Engineer — 1 account.
- Hardware role — exact title not reported — 1 account.
- Full-stack Software Engineer - DevOps team — 1 account.
Firmware Engineer
1 account in this role.
What came up
Both phone rounds focused on C. A small bit-manipulation task sat alongside pointer, linker and driver questions.
Questions we found
Algorithms / Bit Manipulation
| Question | Frequency | All last seen dates |
|---|---|---|
| Write simple code to set and clear bits | 1 report | Reports: 2020-02-08 (report); Jan–Mar 2020 (header interview period) |
C / OS / Firmware Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| Explain function entry, return and the call stack | 1 report | 2020-02-08 (report); Jan–Mar 2020 (header interview period) |
| Explain the linker’s work and ordering | 1 report | 2020-02-08 (report); Jan–Mar 2020 (header interview period) |
| Discuss volatile, static and initialization of global/local variables | 1 report | 2020-02-08 (report); Jan–Mar 2020 (header interview period) |
| Explain addressing and different pointer types, including an int pointer used with uchar | 1 report | 2020-02-08 (report); Jan–Mar 2020 (header interview period) |
| What is a system on a chip? | 1 report | 2020-02-08 (report); Jan–Mar 2020 (header interview period) |
09: Firmware: two C-focused phone rounds with bit-setting code
Interview period: Jan–Mar 2020 (header) · Report: Feb 8, 2020 · Firmware Engineer · New grad · Passed the phone rounds
The candidate described two rounds of about 45 minutes each, mainly on C. They also pasted a firmware job description; its list of technologies is not evidence that all of those technologies were asked in the interviews.
Questions covered function entry and return, linker behavior and ordering, volatile and static, and initialization values for global and local variables. The driver discussion used GPIO changes as an example when asking about volatile.
The interviewer asked what addressing meant to a programmer; the candidate associated it with virtual memory. Another question compared pointer types and asked what would happen if an int pointer were used with uchar data. The precise declarations were not supplied.
There was simple set-and-clear-bit code and a question asking the candidate to define an SoC. The report marks the phone interviews as passed.
Hardware role — exact title not reported
1 account in this role.
What came up
The candidate recalled two MUX constructions, clocking questions and DFT follow-ups drawn from a project.
Questions we found
Digital Logic / Hardware Design
| Question | Frequency | All last seen dates |
|---|---|---|
| Implement an AND gate with a multiplexer | 1 report | Reports: 2018-07-10 (report); Jul–Sep 2018 (header interview period) |
| Implement an XOR gate with a multiplexer | 1 report | Reports: 2018-07-10 (report); Jul–Sep 2018 (header interview period) |
Clocking / Test Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| Explain setup time | 1 report | 2018-07-10 (report); Jul–Sep 2018 (header interview period) |
| Explain clock gating’s purpose and structure | 1 report | 2018-07-10 (report); Jul–Sep 2018 (header interview period) |
| Explain why DFT is used and which clock to use when the design has three clock frequencies | 1 report | 2018-07-10 (report); Jul–Sep 2018 (header interview period) |
10: Hardware phone screen: two MUX tasks and an unclear clock-domain question
Interview period: Jul–Sep 2018 (header) · Report: Jul 10, 2018 · Hardware role; exact title not reported · New grad
The phone conversation lasted a little over half an hour and started with projects on the resume. The candidate was asked to build an AND gate with a MUX and an XOR gate with a MUX.
One question described a signal bit going from a lower-frequency flip-flop domain to a higher-frequency one. The candidate initially thought it was about generating a faster clock, then wondered whether the intended issue was synchronization and metastability. The author said the wording had not been clear, so that interpretation remains uncertain.
Other questions covered setup time, clock-gating purpose and structure, why DFT is used, and which frequency to use for DFT when flip-flops in the design use three clock frequencies. DFT came up because of a resume project.
The candidate felt some answers had been weak but said the interviewer guided them toward answers. A later reply mentions a previous internship in China; it does not turn this new-grad application into an internship report.
Full-stack Software Engineer - DevOps team
1 account in this role.
What came up
Reported topics: coding tasks; OS, memory, architecture or concurrency; GPU, graphics, ML or numerical topics; projects or resume; web implementation, APIs or databases.
Questions we found
Algorithms / Data Structures
| Question | Frequency | All last seen dates |
|---|---|---|
| Maximum Falling Path Sum | 1 | Reports: Date not reported |
| Weighted interval sums with local weights 1..length | 1 | Reports: Date not reported |
Project Coding
| Question | Frequency | All last seen dates |
|---|---|---|
| Build a student-grade frontend/API/schema and extend its queries | 1 | Date not reported |
Frontend / UI Implementation
| Question | Frequency | All last seen dates |
|---|---|---|
| Write HTML with an input and submit button | 1 | Reports: Date not reported |
| Write a React component using state | 1 | Date not reported |
Behavioral (BQ)
| Question | Frequency | All last seen dates |
|---|---|---|
| Why full-stack/DevOps? | 1 | Date not reported |
| Background, interests, why AMD and relocation | 1 | Date not reported |
JavaScript / React Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| Angular versus React | 1 | Date not reported |
ML Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| Explain how BERT works | 1 | Date not reported |
SQL / Database Questions
| Question | Frequency | All last seen dates |
|---|---|---|
| Justify SQL versus NoSQL for an unspecified scenario | 1 | Date not reported |
11: Full-stack campus hiring: weighted queries, a grade app and React state
Report date not established · MTech campus SWE applicant, full-stack/DevOps team · India · Selected
The retained original does not establish an exact publication or interview date.
OA
The source names the platform as GeeekAssess. MCQs covered OS, basic networks and C output, without preserving the individual questions.
The candidate solved a Maximum Falling Path Sum task. Practice the explicitly completed variant here: Maximum Falling Path Sum. A second task asked for weighted range sums: for each 1-indexed inclusive interval, weights start at 1 at its left edge. With nums=[5,2,7,6,3] and queries [1,3], [2,5] and [4,5], the reported answers are 30,46,12. Their brute-force solution passed about half the cases. Practice: Weighted Range Sum Queries, with the same local weighting formula and reported example.
First technical round — two interviewers, about one hour
They explained a full-stack project's purpose, features and architecture, including live chat and sockets. An internship/C project prompted discussion of multithreading, file locking, synchronization and two-phase locking. A robotics-navigation project received a modification question whose changed requirements were not preserved.
The whiteboard task was a student-grade application: form fields, buttons and dropdowns; a JavaScript POST handler; backend POST and GET routes; SQL versus NoSQL; primary and foreign keys; and subject-wise grade display. The candidate used fetch, Express/Node and SQL, and could assume an existing database connection. Follow-ups added pagination, an index on subject, and performance beyond 100,000 rows.
BERT also came up. The candidate described training and fine-tuning models rather than only calling model APIs.
Second technical round — about 30 minutes
They wrote basic HTML with an input and submit button, then a React component using state. When they forgot class-component syntax, a function component was accepted. The interviewer also asked about Angular versus React and their projects. The linked HTML exercise supplies its form and field details for practice, with Python and Java serving the same editable template.
Third technical/managerial round — about 30 minutes
Questions covered Docker and prior use. The candidate did not know Nomad, so discussed Swarm and Kubernetes instead. They justified SQL versus NoSQL for a scenario that was not retained, and discussed interest in full-stack/DevOps and AMD.
HR — about 15 minutes
Background, interests, why AMD and relocation. Four applicants were shortlisted across two teams; the other candidates' HPC interviews are not part of this applicant's experience.
In this series
- Part 1
- Part 2 (current)
Comments
0No comments yet — be the first to share what you know.