One title, five different jobs
A kernel take-home, a broken cluster to fix and a batching design in a shared doc are three different interviews sold under the same job title. Pick the one you are actually sitting, and study in the order that loop weights.
Not sure which? The 15-minute readiness check will point at one, and the must-know set is a reasonable start on any of them.
Inference Engineer
99 questions · 3 tracksLearn to deploy, measure and improve model serving: GPU memory, batching, inference engines, reasoning outputs and production reliability.
You can build software and want to run models as dependable services. Start with request behavior, then work toward performance experiments and fleet decisions.
Research infrastructure
94 questions · 3 tracksPlan, run and rescue training jobs large enough that failure is a schedule item.
You want to sit next to researchers and keep very large runs moving: parallelism layout, collectives, checkpoints and the failure math.
Platform and fleet
90 questions · 3 tracksRun the machine that other people's jobs run on, and keep it honest under many tenants.
You want the cluster itself: scheduling, the fabric, node health, quota and the on-call that comes with all of it. The largest share of open roles, and the path that skips kernels on purpose.
Kernel and performance
97 questions · 3 tracksReason from a warp to a rack, and make a kernel fast for a reason you can name.
You want to write and optimise the code the model actually runs on. The deepest path and the narrowest, and it gates hardest on C++ fluency.
Generalist AI infrastructure
95 questions · 3 tracksServe models and keep the fleet alive, which is what most postings with this title actually mean.
You want the common shape of the job rather than a specialism: enough serving to run it, enough fleet to keep it up, and enough arithmetic to size it.
