mediumNewOpenAIGoogleMeta

Two teams both need the same capacity and both have escalated. How do you resolve it?

A capacity fight is almost never about capacity. It is two teams with different information and no shared number. The move that ends it is publishing utilization both teams can see, and the escalation that works is a written proposal with options rather than a request for a ruling.

Updated Sep 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.

more free answers with an account · no card

The concepts behind this question

Ranked by how closely each one overlaps this question's topic, so the first card is the thing to read if the answer above moved too fast.

Foundational

🧭 Ownership & Judgment

Escalation That WorksEscalation has a reputation as a political act because most of it is done badly: a problem handed upward with no options and an implicit request that someone else choose a side. Done well it is a one-page artifact with two or three costed options, a recommendation, the decision needed, a date, and what you will do by default if no answer arrives. That last line is what converts a message into a decision, and it is the part almost everyone omits.

Foundational

🧭 Ownership & Judgment

Deciding Under Incomplete InformationMost infrastructure decisions are made before the evidence is complete, and the skill being assessed is not judgment in the abstract but classification: whether the decision can be undone cheaply. Reversible decisions deserve speed and a scheduled review; one-way decisions deserve the delay and a second opinion. Engineers who apply the same deliberation to both are slow where speed is free and careless where it is not.

Advanced

🧭 Ownership & Judgment🔒 Premium

Working with ResearchersInfrastructure engineers at AI labs and platform teams have an unusual customer: a researcher whose experiment is the company's product, who needs the cluster today, and whose request may be a bad idea for the fleet. The behavioral round tests whether you can serve that customer without being run by them: saying no with data, saying yes with conditions, finding the need behind the ask, and sharing ownership of outcomes neither side controls alone. This page gives the recurring situations at the boundary, the responses that work in each, worked narratives, and the answers that sound collaborative and fail.

Foundational

🧭 Ownership & Judgment

Talking About Cost and Capacity with LeadershipInfrastructure engineers are asked to justify large numbers to people who do not share their vocabulary, and the conversations go wrong in predictable ways: a technical objection with no alternative, a forecast with no assumptions, or a cost quoted in a unit the listener cannot act on. What works is a small number of costed options, a stated recommendation, the decision needed by a date, and every figure expressed in whatever the listener actually controls.

Explore the full curriculum →

UP NEXT ON YOUR JOURNEY

Next in this trackA researcher asks you to bypass a required check to hit a deadline. What do you do?Next in this trackHow do you keep current in a field that changes every few months?Next in this trackTell me about a cost reduction you led. How did you prove reliability did not suffer?

FEDITOR'S NOTE

Scored on establishing a shared fact before negotiating, on escalating with options and a recommendation rather than asking for a decision, and on the policy change that prevents recurrence.

DISCUSSION · 0

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