Behavioral question
Tell me about a time you improved a process
Process stories fail when they are a tour of a tool you installed. They want the old path, the step you removed or shortened, and a before-and-after count from people who walk that path.
Check this example, then replace it
The box starts with one STAR answer. Read the scores, then delete it and paste a story from your own work. Scoring stays in the browser.
87/100
Strong
About 56 seconds spoken · 139 words. Spoken time uses 150 words per minute.
Feedback
- This has a clear STAR shape. Only keep numbers you can defend out loud.
Which sentence is which
In August 2024 every production change on the payments team waited for a Thursday deploy train, and urgent fixes sat for days. I was responsible for a path that was safer than “just SSH it.”. I wrote a short checklist with three checks, instrumented a rollback timer, and asked two seniors to run a fix through it on a Wednesday as a test. I then moved urgent fixes off the Thursday train and kept the train for everything else. I added the three checks to the deploy template so the next urgent fix did not depend on me remembering the list. The result was urgent fixes shipping in a median of 6 hours instead of 4 days, with 0 bad rollbacks over the next 20 changes. The Thursday train stayed, and it got shorter because the emergencies were gone.
Why this example holds up
You do not blow up the old process. You split it. The median time and the rollback count are the proof.
How to answer “Tell me about a time you improved a process” with STAR
- Situation. Set the scene in one or two sentences: when it was and what was already wrong. For example: In August 2024 every production change on the payments team waited for a Thursday deploy train, and urgent fixes sat for days.
- Task. Say what you personally owned. For example: I was responsible for a path that was safer than “just SSH it.”
- Action. Say what you did, in order, with I. For example: I wrote a short checklist with three checks, instrumented a rollback timer, and asked two seniors to run a fix through it on a Wednesday as a test.
- Result. End on the change, with a number you can defend. For example: The result was urgent fixes shipping in a median of 6 hours instead of 4 days, with 0 bad rollbacks over the next 20 changes.
Mistakes on this question
- A new tool with no change in cycle time.
- Improving a process you do not use, then leaving. Adoption is part of the result.
- Numbers you copied from a vendor. Use a count you observed.
How to practice it
Draw the old path in three boxes. Your story should delete or shrink one box. If you only added a box, reconsider.
FAQ
Does this have to be an engineering process?
No. Hiring loops, support macros, and incident reviews are all fair, as long as you owned a change and counted it.
What if the process improvement was unpopular?
Say who disliked it and what you changed to get them through it once. One successful run beats a policy nobody follows.