mediumNewCoreWeaveLambda LabsNVIDIA

A vendor says your configuration is the problem. You think it is their firmware. How do you proceed?

Arguing is the losing move and so is capitulating. What moves a vendor case is a reproducer small enough for their engineer to run, counters that isolate their layer from yours, and a bisection that removes your configuration as a variable entirely.

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

The Reliability Pushback StoryEvery AI infra loop has a behavioral round, and the story it wants most is the one where you stopped something (a launch, a run, a hardware admission) because the data said to, and you were accountable for the cost of stopping. This page gives the skeleton that works: the situation, the signal you read, the decision and who owned it, the evidence you brought, and what changed afterward. It also gives the follow-up interviewers hold back, the version that sounds right and fails, and the line between a senior telling and a staff telling of the same story.

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.

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 trackHow do you bring a junior engineer through their first serious incident?Next in this trackWhat do you think is the most underrated problem in AI infrastructure right now?Next in this trackThree incidents are open, your pager is going off, and a customer is escalating. What do you do first?

FEDITOR'S NOTE

Scored on building a minimal reproducer before escalating, on isolating the vendor's layer with counters rather than assertions, and on managing the case as a project with a workaround in parallel.

DISCUSSION · 0

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