Quantify your impact
Turn vague results into concrete, credible numbers.
- Express results with metrics such as latency, cost, revenue, or time saved.
- Estimate honestly when exact numbers are unavailable.
- Explain why a result mattered to users or the business.
“The page got faster” is forgettable. “I cut the checkout page’s p95 load time from 4.1 s to 1.2 s, and conversion rose 6%” is evidence. Numbers make your impact concrete, show you understood what mattered, and give the interviewer something to write in their notes.
What to measure
- Performance: latency, throughput, error rate, uptime.
- Cost: infrastructure spend, engineering hours saved.
- Business: revenue, conversion, retention, support tickets.
- Team and process: deploy frequency, build time, onboarding time, incidents.
- Scale: users, requests, data volume, number of teams affected.
Pair each number with its so what: “Build time went from 25 to 6 minutes, so engineers deployed several times a day instead of batching changes.”
The arithmetic is simple: if builds went from 25 minutes to 6, the change is (25 − 6) ÷ 25 = 76% faster. Saying “build time down 76%, from 25 minutes to 6” gives both the percentage and the real numbers behind it.
If you don’t have exact figures, estimate and say so: “roughly 30% fewer on-call pages, based on the incident dashboard.” Never invent numbers - interviewers ask follow-up questions, and precise-sounding figures you can’t explain destroy credibility. Relative changes (percentages) are often safer to share than confidential absolute values.
Practice: find the vague claims
Try it
Up to 15 XPSpot the vague claims
Each answer has phrases that sound good but prove nothing. Click them, then check. For each one, think about what you’d ask to pin it down.
Click every suspicious section. There are 2.
Try it
Up to 15 XPStrong evidence or weak evidence?
Decide whether each result would convince a skeptical interviewer.
“Cut p95 load time from 4.1 s to 1.2 s, and conversion rose 8%.”
“Improved the app a lot.”
“Reduced on-call pages by roughly 30%, based on our incident log.”
“Reduced costs by 12 cents.”
“Onboarding went from two weeks to three days for 40 new hires a year.”
Key takeaways
Quantify outcomes: performance, cost, business, team, scale.
Always add the “so what”.
Estimate honestly and never fabricate.
Lesson quiz
5 questions · pass with 4 correct · up to 50 XP
Passing this quiz completes the lesson and keeps your streak going. Questions you miss come back in review sessions later.
Questions about this lesson
Stuck? Ask. Figured something out? Share it. Explaining is one of the best ways to learn.
Loading posts…