Combine delivery flow metrics with outcome and health signals. DORA style measures (deployment frequency, lead time for changes, change failure rate, time to restore) describe the delivery system, not individuals. Pair them with whether shipped work moved the product metrics it was meant to move, plus health signals such as on call load, review latency and unplanned work. Never assess individuals by commits, lines or story points.
Why interviewers ask this
Interviewers ask this because bad measurement does real damage, and plenty of managers reach straight for individual output counts. They want system level thinking, an explicit statement of which metrics are gameable, and the link from delivery speed to actual product outcomes. Mentioning team health alongside throughput signals that you are thinking about sustainable pace rather than optimizing for one good quarter.
How to structure your answer
- Separate system metrics from individual assessment explicitly.
- Name the delivery flow metrics and what each one tells you.
- Connect delivery to product outcomes, not just velocity.
- Add health signals and name the metrics you refuse to use.
Example answer
I look at three layers. Delivery system: deployment frequency, lead time from merge to production, change failure rate and time to restore. Those tell me whether the machine works, and they are team metrics, never individual ones. Outcomes: did the thing we shipped move the number it was meant to move, because a team that ships quickly and changes nothing is not performing. Health: review turnaround, pages per week and how many land out of hours, and how much of the sprint gets eaten by unplanned work. When I joined my last team, lead time was about eleven days and most of that was waiting for review, not writing code, so we set a four hour review expectation and lead time halved without anybody working harder. For individuals I do not use metrics at all. I use evidence: the quality of their design work, whether they raise the people around them, whether their code needs three rounds of review or none. Story points per person is the fastest way to teach a team to inflate estimates.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What would you do if leadership asked you to rank engineers by output?
- How do you tell a slow team from a team with a genuinely hard problem?
- How do you measure the impact of platform or infrastructure work?
Related engineering manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions