“Put a number on it” is useful advice until you start making up the number.
You improved a handoff. You resolved a disagreement. You caught a missing requirement before a review. There was no dashboard measuring your contribution, and nobody sent you a report assigning it a dollar value.
An interview result without metrics can still be specific: explain what changed, how you know, and what you cannot conclude. The missing percentage is not a reason to replace a real example with a fictional achievement.
A result needs evidence
Nick Dimitrov's LinkedIn post on interview metrics argues for making the outcome visible. That is a useful aim. A candidate still needs a basis for the number they use.
“The team was happier” leaves the listener guessing. “The next shift received a handoff with every open item assigned to an owner” gives them something concrete to understand. It becomes stronger if you explain how that was checked.
A number can be excellent evidence. It can also be decoration. “Efficiency improved by 30%” tells us little if you cannot explain what you measured, over which period, or what else changed.
Three questions before you finish the story
Start with what was different afterward. A task completed is sometimes the relevant result, but explain why completion mattered. Did someone receive the information needed for a decision? Did a record stop contradicting another record? Did the responsible person accept the correction?
Then ask how you know. You might have reviewed the next handoff, received confirmation from its recipient, or seen the decision recorded. Explain that check in ordinary language.
Finally, identify the limit. Completing a handoff does not prove you prevented an incident. A resolved customer question does not establish a retention increase. Keep the result as large as the evidence supports.
A fictional answer without an invented percentage
Question: “What is an achievement you are proud of?”
“Our evening handoff listed outstanding requests but did not say who would follow up. I was responsible for preparing the note on my shift. I added an owner and a next step to each open request, then asked the receiving colleague to check whether anything was still unclear. They identified one request that needed a different owner, and I corrected it before I left. At the next handoff, I checked that the same fields were being used. The receiving team had an agreed owner for every listed item. I don't have a reliable figure for time saved; the result I can support is that those requests no longer arrived without an assigned next step.”
This is an illustrative example, not a customer story. The achievement is modest and complete. The candidate owned a defined change, checked it with the person affected, and explained its limits.
It would be weaker with “I transformed operations” at the end. That claim would need a different level of evidence.
Separate the outcome from the benefit you hoped for
An action, an observed result, and an intended benefit can sound similar:
- Action: “I added an owner field to the handoff.”
- Observed result: “The receiving colleague confirmed who would take each request.”
- Intended benefit: “We wanted fewer requests to get lost between shifts.”
Only the middle statement establishes what happened in this example. The final statement explains why the work mattered. It does not prove that the longer-term benefit occurred.
That distinction is useful when your project is still running. Say what you have observed so far and what has not yet been measured. You can discuss an interim result without pretending the whole project is finished.
Try your own example
Use the greatest professional achievement question. Write one sentence for the change, one for the check, and one for the limit. Then answer aloud without reading the sentences.
If your result belongs to a team, use the personal contribution exercise to make your part clear. If the details cannot be shared, use the confidential-work preparation guide before choosing what to include.
Common questions
Can I give a STAR answer without numbers?
Yes. Describe an observable change and how you know it happened. A corrected record, an agreed decision, or an independently checked handoff can be a result when it accurately reflects your work. Do not invent a metric to complete the format.
What can I use instead of a percentage in an interview answer?
Explain the before-and-after condition, who checked it, and what that allowed the team to do next. Use a real count or measurement when you have one, but distinguish an observed outcome from an estimate or a hoped-for benefit.
Should I estimate a result if I cannot remember the exact number?
Use an estimate only when you have a defensible basis and can label and explain it. If you cannot support the number, describe the outcome you can verify and say that you do not have a reliable measurement of the wider impact.
Specificity comes from being able to explain the result. A percentage cannot do that work for you.
