AMD CUDA, Triton & Kernel Engineering interview questions
For AMD kernel roles, connect GPU programming fundamentals to HIP and ROCm. This shared CUDA, Triton and kernel track includes transferable performance exercises; use the role’s named accelerator and software stack to decide which implementation to practice. Questions tagged to AMD appear first, followed by additional practice from our CUDA, Triton & Kernel Engineering track. Company tags indicate preparation relevance, not confirmed interview appearances. Confirm the current interview format with your recruiter.
Preparing for AMD kernel work with HIP and ROCm
- Separate source translation from validation. AMD’s HIP porting guide describes HIPIFY tools for translating CUDA code. Treat translation as a starting point: check unsupported APIs, compile for the target device and compare outputs against a reference. A successful build does not establish correctness or performance.
- Check warp assumptions on the target architecture. AMD documents different warp sizes across architectures. Use the device’s warpSize and appropriate lane-mask types instead of assuming 32 or 64 everywhere. For a reduction exercise, test partial groups and boundary sizes as well as full groups.
- Choose an optimization from a measured bottleneck. Fix the tensor shape, dtype and correctness tolerance, then profile a baseline on the target GPU. If memory traffic limits the operation, investigate reuse or fusion; if the trace shows launch gaps, investigate dispatch overhead first. Keep an optimization only when repeated measurements improve the target workload without breaking the tolerance. This is a preparation exercise, not a report of AMD’s interview format.
Sources: AMD HIP porting guide: translation, warp size and lane masks. Reviewed .
AMD Instinct and ROCm · Roofline Model. Check each resource’s access level.
CUDA, Triton & Kernel Engineering questions tagged to AMD
Additional CUDA, Triton & Kernel Engineering practice
These questions cover the same topic and are not tagged to AMD. Use them to practise applying the ideas in a different situation.
Concepts for CUDA, Triton & Kernel Engineering preparation
These concept explanations cover the ideas used in the questions. Check each card for its access level.
This collection includes practice questions such as "Port a hand-written CUDA kernel to MI300X. What translates mechanically, and what silently computes the wrong answer?", "Explain FlashAttention. Why is it called IO-aware, and what does it actually save?", "Explain occupancy and register pressure: launch bounds, spills, the calculator, and why 50% occupancy can beat 100%.". Company tags describe relevance to preparation; they do not confirm that AMD asked these questions. Check each question for answer access.
Start with a question at your level, use the linked concepts to understand the mechanism, then practise explaining your decision and its limits. Review the company guide's sources and confidence notes, and confirm the current role and interview format with your recruiter.
Yes: GPU Software Developers and Principal Software Developers for ROCm (Austin), AI Cluster Validation Engineers (Austin, Santa Clara, Seattle, Secaucus) and System Design Engineers for AI cluster software, plus ROCm library and framework roles. Note that the cluster validation posting stated no H-1B sponsorship.
Aggregated candidate reports: a coding round on algorithms and data structures in C or C++, a system design discussion about driver architecture or the GPU software stack, a domain deep dive by team, and a behavioral round with an engineering manager. Some ML-oriented candidates report only a technical round (Linux, Python scripting, ML theory) and an HR conversation. No dated first-hand ROCm kernel debrief was found.
Other topics for AMD preparation
Explore the other topics mapped to AMD in our preparation guide.
Continue your AMD interview preparation
Continue with related questions and the concept curriculum. Free questions are available in every track; check pricing for full access.
Independent and not affiliated with AMD. All trademarks belong to their owners.
