Many engineers freeze when asked about impact. The question can feel like an invitation to inflate numbers or speak in corporate slogans.
Impact does not require a press release voice. It requires a clear account of what was true before, what you did, and what was different after.
A simple shape
Try this, in your own words:
- Situation: What was hard, unclear, or costly?
- Your part: What did you decide, build, coordinate, or unblock?
- Change: What improved for the team, the system, or the users?
- Learning: What would you do differently next time?
If you have a metric, use it. If you do not, a concrete before-and-after still counts. “Reviews that used to stall for days started landing same-day because we agreed a smaller review surface” is impact. “Drove synergies across stakeholders” is not.
Words that usually help
- I noticed…
- I proposed… / I decided…
- We tried…
- What changed was…
- The tradeoff was…
These keep the story grounded in judgment, not theater.
Words that usually get in the way
Skip the filler that sounds impressive and says little: leverage, utilize, optimize (without naming what), best-of-breed, cross-functional excellence. If a phrase would make a teammate roll their eyes in standup, leave it out of the interview too.
Practice out loud
Pick two stories from the last year. Say each one in under two minutes to a friend, a coach, or a voice note. Listen for where you hide behind “we” when the useful detail is your judgment, and where you overclaim when a modest, accurate version is stronger.
Impact is not a performance of importance. It is evidence that your involvement mattered—and that you can explain why without borrowing someone else’s vocabulary.