The author reports receiving an AMD GPU software engineering offer after interviews for a Toronto/Markham team. Recruiter outreach led to an initial screen and an extended hiring-manager conversation. An in-person onsite followed roughly two weeks after availability was requested, and the offer arrived about three weeks after that visit.
The four onsite sessions covered inference systems, agent architectures and compiler concepts, GPU profiling and optimization, and a hiring-manager follow-up. Technical discussion included attention caching, batching, memory-versus-compute limits, register spilling, and matrix-transpose performance. A top-k coding task prompted discussion of a partition-based approach after the applicant used a heap. The final conversation explored learning habits, team work, and emerging inference directions. Several sessions ran longer than scheduled. The author recommends preparing to connect machine-learning concepts with systems design and performance diagnosis, rather than relying only on algorithm practice.
Discussion
Loading comments…