AI Infra Interviews logo

AI Infrastructure Engineer Interview Questions

A curated, continuously updated set of 413 AI infrastructure interview questions with worked answers, organized by topic and by company. These loops do not stop at “can you build the system.” They ask whether you know what the hardware is doing underneath it: why decode is memory-bound, what a slow all-reduce looks like in the logs, how many GPUs a training run needs and why the answer moves with MFU. The questions are modeled on loops at NVIDIA, OpenAI, Anthropic, Google, CoreWeave, Together AI, Fireworks, Modal and more, across the eleven areas that decide AI infra offers.

413 questions13 topics41 companiesupdated 2026

Grounded in real AI infrastructure interview loops and written to a senior-engineer editorial bar, with every number worked and every diagram hand-built.

What AI infrastructure interviews test

Across companies, the loop probes five dimensions. Which one dominates depends on the track: kernel and performance roles weight the first, platform roles the fourth, and every loop has some of the third.

  • Hardware numeracy and kernels

    The memory hierarchy, the roofline, coalescing and occupancy, FlashAttention internals. Kernel roles write CUDA or Triton live; everyone else is expected to read a profile and say why a kernel is slow.

  • Distributed training at cluster scale

    Data, tensor, pipeline, context and expert parallelism, the collectives under them, MFU, checkpointing, and what a run does at 3 a.m. when a GPU falls off the bus.

  • Napkin math and systems design

    How many GPUs, how much KV cache, how many tokens per second, what a million tokens costs; then a design that uses those numbers: an inference platform, a training cluster, a scheduler with preemption.

  • Cluster, network and fleet operations

    Kubernetes device plugins and DRA, MIG and sharing, gang scheduling, InfiniBand versus RoCE, DCGM, the XID taxonomy, stragglers, and the incident craft of keeping ten thousand GPUs acting like one.

  • Practical coding and judgment

    Build a GPU credit scheduler or a batching queue in 45 minutes, then the behavioral round: the launch you pushed back on, the migration nobody wanted, and at the labs, the safety and mission conversation.

GPU Architecture Interview Questions

SMs, warps and the memory hierarchy, tensor cores, the roofline model, FP8 and FP4 numerics, NVLink and HBM generations, and the non-NVIDIA canon: TPU, Trainium, MI300-class, Cerebras and Groq. The hardware physics every other round assumes you know cold.

See all 30 GPU & Accelerator Architecture questions with answers →

GPU Cluster Hardware and Deployment Interview Questions

Choosing between H100, H200, B200, B300 and RTX PRO 6000; NVLink domains and rack-scale systems; InfiniBand and Ethernet fabrics; the cables, transceivers and optics power nobody budgets; rack power, busways and liquid cooling; bring-up, burn-in and acceptance. The physical layer every cluster rests on, dated to 2026.

See all 40 Hardware, Cabling & Cluster Build-Out questions with answers →

CUDA & Triton Kernel Interview Questions

Coalescing, shared memory and bank conflicts, occupancy, fusion, tiled GEMM, FlashAttention internals, Triton, CUTLASS, Nsight profiling and torch.compile: the live-coding and take-home round at NVIDIA, Fireworks, Together and the labs' performance teams.

See all 30 CUDA, Triton & Kernel Engineering questions with answers →

Distributed Training Interview Questions

DDP, ZeRO and FSDP, tensor, pipeline, context and expert parallelism, collectives and their cost, MFU, activation checkpointing, elastic and fault-tolerant training, checkpoint economics and the RL post-training stack. Owning the training run at cluster scale.

See all 32 Distributed Training & Parallelism questions with answers →

LLM Inference & Serving Interview Questions

Prefill versus decode, the KV cache, PagedAttention and continuous batching, chunked prefill, speculative decoding, disaggregated serving, quantization, vLLM, SGLang and TensorRT-LLM, multi-LoRA and routing: hosting open-weight models at a latency SLO and a cost you can defend.

See all 30 LLM Inference & Serving questions with answers →

Open-Weights Model Serving Interview Questions

Running the 2026 open-weights frontier: GLM-5.3, Kimi K3 and DeepSeek V4. Reading config.json to size a model you have never run, latent attention and sparse indexers, vLLM and SGLang configuration, expert parallelism and all-to-all backends, weight formats, and the benchmarks that do not lie.

See all 40 Open-Weights Models & Serving Engines questions with answers →

Napkin Math & Estimation Interview Questions

Memory footprints, 6ND, arithmetic intensity and the ridge point, bandwidth-bound decode, communication volume, GPU counts and time to train, cost per million tokens, TCO and buy versus rent. The estimation round almost every AI infra loop includes, with every assumption stated.

See all 30 Napkin Math, Cost & Capacity questions with answers →

Networking, Interconnect & Storage Interview Questions

NCCL and the collective algorithms, RDMA, InfiniBand versus RoCE, rail-optimized and fat-tree fabrics, congestion control, GPUDirect, parallel filesystems versus object storage, data loading and checkpoint I/O: the fabric and the disks that decide whether ten thousand GPUs act like one.

See all 30 Networking, Interconnects & Storage questions with answers →

Kubernetes GPU Scheduling & Slurm Interview Questions

Device plugins and dynamic resource allocation, MIG, MPS and time-slicing, gang scheduling with Kueue and Volcano, topology-aware placement, multi-tenancy and quotas, Slurm versus Kubernetes, containers and cold starts: the platform round at CoreWeave, Modal, Nebius and every GPU cloud.

See all 30 Kubernetes, Slurm & GPU Scheduling questions with answers →

GPU Fleet Reliability & Observability Interview Questions

DCGM, the XID taxonomy, ECC and row remapping, NVLink faults, stragglers and hangs, thermal and power events, node health checks, SLOs for training and serving, incident response and postmortems at fleet scale. The on-call reality most prep sites skip.

See all 30 GPU Fleet Reliability & Observability questions with answers →

AI Infrastructure System Design Interview Questions

Design an inference platform at 10k requests per second, a 10,000-GPU training cluster, a job scheduler with preemption and checkpointing, a serverless GPU runtime with sub-second cold starts, a multi-tenant fine-tuning service, an eval pipeline. The whiteboard round at OpenAI, Anthropic, Baseten and Together.

See all 31 AI Infrastructure System Design questions with answers →

Coding Interview Questions for Infra Engineers

Practical builds in Python, Go and C++: a GPU credit scheduler, a rate limiter, a versioned KV store, merging GPU idle intervals, a batching queue, retry with backoff, concurrency under load, parsing a kernel trace. The screens that test whether you can ship infra code in 45 minutes.

See all 30 Coding for Infra questions with answers →

Behavioral Interview Questions for AI Infra Engineers

Pushing back on a launch for reliability, the on-call story, the migration nobody wanted, working with researchers, the safety and mission rounds at the labs, and your view on where AI infrastructure is going. The rounds that decide between two technically equal candidates.

See all 30 Behavioral & Ownership questions with answers →

AI infra interview questions by company

Each company runs a different loop and weights a different axis: CUDA-heavy, Kubernetes-heavy, distributed systems, ML systems design, or cost and capacity. These pages break down the process and what each round is really testing, compiled from public reports with a confidence level.

Before the interview: the role, the numbers, the tools

AI infra interview questions: FAQ

What does an AI infrastructure engineer interview test?

Whether you can build and run the compute under large models: GPU and accelerator internals, kernel performance, distributed training across thousands of chips, inference serving under latency and cost targets, cluster scheduling, the network and storage fabric, and keeping a fleet healthy. Loops mix practical coding, a systems-design round with real numbers, a napkin-math or debugging round, and a behavioral or mission round. Frontier labs, chip makers, GPU clouds and ML platform teams all run some version of it.

How is it different from a normal software engineer or SRE interview?

A standard loop asks whether you can build a distributed system. An AI infra loop adds hardware physics: is this kernel memory-bound, how many bytes does decode move per token, why did MFU drop when you doubled the cluster, which XID code means a GPU has to leave the fleet. SRE loops share the reliability half but not the accelerator half. Grinding LeetCode alone does not carry you; the differentiators are numeracy about hardware and experience with what breaks at scale.

What rounds does an AI infra interview usually have?

A common loop is a recruiter screen, a practical coding screen (build a scheduler, a rate limiter, a batching queue, not puzzles), a systems-design round (an inference platform, a training cluster, a job scheduler), a performance or debugging round (a slow all-reduce, a p99 spike, a kernel to optimize), and a behavioral round. Kernel and performance roles add a take-home or live CUDA or Triton exercise. Rounds vary by company and team, so confirm yours with the recruiter; the company pages below carry what is publicly reported with a confidence level.

Do I need to know CUDA?

It depends on the track, and the site tags every company by which axis it weights. Kernel and performance roles at NVIDIA, Fireworks, Together and the labs' performance teams test live CUDA or Triton. Platform and cluster roles at GPU clouds test Kubernetes, Linux and distributed systems and rarely ask you to write a kernel, though they expect you to know why one is slow. Inference and training roles sit in between: read kernels, reason about them, rarely write them in the room.

What is napkin math in an AI infra interview?

Estimation from first principles: how many GPUs to train a 70B model on 15 trillion tokens in a month, how big the KV cache is at 128k context, whether decode is memory-bound, what a million output tokens costs. The interviewer wants the formula, the assumptions stated, and the right order of magnitude. The formula sheet and calculators on this site cover every one of these.

Which companies hire AI infrastructure engineers?

Frontier labs (OpenAI, Anthropic, Google DeepMind, xAI, Meta), hyperscalers (Google Cloud, AWS, Azure, Oracle), chip makers (NVIDIA, AMD, Cerebras, Groq, SambaNova), GPU clouds and serving platforms (CoreWeave, Together AI, Fireworks, Baseten, Modal, Lambda, Nebius, Crusoe, Anyscale), and ML platform teams at Databricks, Netflix, Uber, LinkedIn and Pinterest. India has a growing set of roles at NVIDIA, AMD, Microsoft and Google engineering centers plus domestic AI clouds. See the company list below.

Is there an AI infra interview questions PDF or sheet with answers?

This page is a continuously updated, structured set of AI infrastructure interview questions with worked answers, organized by topic and by company, with the hardware numbers refreshed on each GPU generation. A static PDF goes stale the day a new part ships.

Prep every AI infra interview question, with answers that hold up in the room

413 questions across 13 topics, ordered easy to expert, each with a worked answer, a hand-built diagram where one earns its place, and the follow-ups interviewers hold back. The first questions in every track are free.

Interview loops change and vary by team, level, and region. Treat this as directional preparation and confirm the exact rounds with your recruiter.