1 min lesson
Speak success in SLO terms
Name the parts in "Speak success in SLO terms" and give the practical job of each one.
Step 1 of 2
Speak success in SLO terms
- Latency
- p50 / p95 / p99 per surface; Tab has the tightest budget, Agent the loosest
- Availability
- Gateway uptime and error budget - failover exists to protect this number
- Cost
- Cost per request and per surface; the axis that funds the company at this ARR/headcount ratio
Watch out
Don't quote precise internal numbers you can't actually know - invented "Cursor does 4.2M RPS" stats read as bluffing. Frame scale honestly: "millions of requests is the JD's stated baseline and at a small headcount with high ARR, per-GPU-dollar efficiency is existential." Reason from the public facts, then show how you'd measure the rest once inside.
Tie every routing call back to a number
Practice converting design choices into dollars and milliseconds out loud. "This fallback saves roughly X% per-token but risks Y on quality, so I'd gate it to surfaces where a quality dip is invisible" is the register the deep-dive round rewards.