The Bill That Tripled
You are interviewing to lead infrastructure at a company whose cloud bill tripled in a year and now threatens runway. The CFO wants 40 percent gone in six months, engineering says nothing can slow down, and nobody can explain the bill.
the situation
You are interviewing to lead infrastructure at a 150-person product company. Its cloud bill has tripled in the last year, and at the current burn rate it is a genuine threat to runway. The CFO has mandated a 40 percent reduction in cloud spend within six months, and the board is watching the number. Engineering leadership has drawn its own line: reliability and delivery speed cannot regress while you cut. Nobody currently owns cloud spend, and when the CFO asked what the money actually buys, no one in the company could answer. The interviewer wants to know how you would take ownership of that mess.
what this interview covers
- Making the bill explainable
- Quick wins and their traps
- The incident, live
- Structural cost ownership
- Trade-off interrogation
- Guardrails and durable proof
How the interview works
One scenario, 45 minutes, hard stop. The interviewer works through the situation with you - design, incident, trade-offs - and will not confirm or correct anything until the debrief. There are more questions in the arc than most people reach; how far you get matters less than how well you reason. Saying you do not know and moving on beats bluffing. When time runs out, you are graded on everything you covered.
about this interview
About
A 150-person product company watched its cloud bill triple in a year, to the point where the CFO calls it a runway problem and has mandated a 40 percent cut in six months. Engineering leadership will not accept slower delivery or worse reliability as the price, nobody currently owns cloud spend, and nobody can explain what the money buys. You are interviewing to lead infrastructure and inherit exactly that. The interview walks the whole program: making the bill explainable, finding the fast money and the traps hiding inside it, a cost-cutting mistake that turns into a live data incident on your watch, the structural work of commitments and team ownership, and the moment you have to look the CFO in the eye over the last 15 percent.
The interviewer plays a senior engineer running a real screen. They will push on your answers and ask why, and that is normal, not a signal that you are wrong. What they will not do is confirm, correct, or hint at how you are doing while the interview is running. Any cloud and any stack earns full credit here; the interview is about reasoning, evidence, and ownership, not one vendor's product names. If you do not know something, say so and move on - bluffing costs more than honesty.
You get 45 minutes and the stop is hard: when time runs out, the interview ends wherever you are, exactly like a real screen. After that you get the debrief real interviews never give you - what each answer showed, what a strong answer looks like, and an overall hire signal based on everything you covered.