How do you measure the performance of a delivery process? Mention the DORA metrics.
What they are really testing: Senior signal: knows the four DORA metrics and, crucially, that speed and stability go together rather than trade off, so you can argue for frequent deploys with data.
A real interview question
How do you measure the performance of a delivery process? Mention the DORA metrics.
What most people say
drag me
“I would measure how often we deploy and how many bugs we have.”
It gropes toward two metrics but misses the full DORA set (lead time, change failure rate, MTTR) and the central insight that speed and stability correlate, frequent small deploys are safer, not riskier, which is the senior point.
The follow-ups they ask next
Why do frequent deploys tend to be more stable, not less?
They mean small batches: each change is small, easy to test, reason about, and roll back. Big infrequent releases bundle many changes into one high-risk, hard-to-debug event. Small batch size is the link between speed and stability.
What are the two stability-focused DORA metrics?
Change failure rate (% of deploys causing a failure needing remediation) and time to restore service (how fast you recover from a deployment failure, deploy MTTR). The other two, frequency and lead time, measure speed.
What the interviewer is listening for
- Names all four DORA metrics in the two pairs
- Knows speed and stability correlate
- Links it to small batch size + uses metrics to improve
What sinks the answer
- Only vague "deploys and bugs"
- Misses lead time / MTTR / change failure rate
- Thinks speed trades against stability
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“Measure delivery with the four DORA metrics: speed = [deployment frequency + lead time for changes], stability = [change failure rate + time to restore (deploy MTTR)]. The key insight: [speed and stability correlate, not a trade-off], because [frequent deploys mean small low-risk batches, easy to test/roll back]. Use them to [drive smaller batches, automation, testing], improving all four together.”
Keep going with deployment
Foundation
What do CI and CD actually mean, and what is the difference between continuous delivery and continuous deployment?
Foundation
Why should you build an artifact once and promote the same one through environments?
Junior
What stages should a good CI/CD pipeline have?
Junior
A deploy went bad in production. How do you handle rollback, and how do you make rollback easy?
Junior
What are feature flags, and how do they decouple deployment from release?
Mid
Compare blue-green and canary deployments. When would you reach for each?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free