mediumNewOpenAIMetaAnthropic

Tell me about a decision you had to make without enough information.

The question is about how you handle uncertainty, so a story where you gathered more data until you were sure answers a different question. Reversibility as the thing that sets the bar, the check-in you schedule when you decide, and what to say about the ones that went badly.

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.

20 answers per topic instead of 10, plus saved progress and bookmarks · no cardor unlock all 283 remaining answers · ₹2,000 / $25

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

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

Your View on Where AI Infrastructure Is GoingSomewhere in a senior or staff loop an interviewer asks what you think happens next: to GPUs and their challengers, to training at scale, to inference economics, to the tools. It looks like small talk and it is scored. The answer that works is a thesis with a date on it, a reason grounded in numbers you can derive, the counterargument you find strongest, and the thing you would watch to know you were wrong. This page shows how to build such a thesis from the material on this site, gives three worked examples, and lists the answers that sound informed 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.

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.

Explore the full curriculum →

UP NEXT ON YOUR JOURNEY

Next in this trackYou think your tech lead's design is wrong. How do you handle it?Next in this trackWhat actually changes between senior and staff engineer in infrastructure?Next in this trackWhy would you leave a hyperscaler for a GPU cloud, or a GPU cloud for a hyperscaler?

FEDITOR'S NOTE

Scored on the decision being classified by reversibility, on a scheduled check-in with a stated trigger, and on the candidate naming what they would have needed to be certain and why they did not wait for it.

DISCUSSION · 0

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