hardCoreWeaveNebiusLambda

Design the control plane for a GPU cloud: tenancy, provisioning, health, billing, and the API a customer sees.

Follow GPU ownership from reservation through verified delivery and cleanup, with stale-operation fencing, recovery and auditable metering.

Updated Sep 2026 · Learn how AI infrastructure works through explanations, worked examples and diagrams, then practise applying it to interview questions.

Follow GPU ownership from reservation through verified delivery and cleanup, with stale-operation fencing, recovery and auditable metering.

This answer is included with a free account. Sign in to read it and save your progress.

free account · no card needed

The concepts behind this question

Use these concept explanations to review the ideas behind this question.

Foundational

📐 AI Systems Design

Control Plane and API Design for GPU PlatformsA control plane records intended work and coordinates its execution. Clear retry, cancellation and listing semantics keep its API useful when requests or workers fail.

Foundational

🧮 Open Weights & Serving Engines

Capacity Planning for Open-Weights FleetsMatch forecast traffic to a measured replica operating envelope, then check failure domains, rollout capacity, readiness time and cost. Output tokens alone omit prompt work and live state; total parameter count alone does not determine a replica's throughput.

Foundational

🖧 Hardware & Cluster Build-Out

Cluster Bring-Up: Firmware, Drivers and the StackBring-up validates the dependencies between firmware, drivers, networking and the runtime. Checking each layer makes faults easier to locate.

Advanced

🩺 Fleet Reliability & Observability🔒 Premium

Incident Response for GPU FleetsGPU incident response restores useful service while preserving enough evidence to diagnose the failure. Mitigation, repair and return-to-service checks have different purposes.

Explore the full curriculum →

UP NEXT ON YOUR JOURNEY

Next in this trackDesign an LLM service for a 200 ms time-to-first-token SLO at p99. Decompose the budget and say what you would give up.Next in this trackDesign the runtime for long-running agents: sessions, tool sandboxes, KV that lives for hours, and checkpoints.Next in this trackDesign serving for a video generation model: diffusion steps, batching, memory, and a latency profile unlike an LLM's.

FEDITOR'S NOTE

Scored on explicit resource arithmetic, durable identity and state boundaries, failure recovery, and a design choice with its reversal condition.

DISCUSSION · 0

No comments yet — be the first to share your approach.