Achievements
Tell the story of your best work so the interviewer sees the stakes, your own part in it and the result it changed.
Overview
Achievement questions ask you to describe the work you are proudest of. They sound easy, and most engineers still undersell. The usual mistakes are describing what the team did without saying what you did, starting with technical detail before anyone knows why it mattered, and ending without a result.
The interviewer is scoring four things. Can you tell work that matters from work that is only interesting? Can you name your own part? Do you connect technical work to what the business or the users needed? And can you carry something hard from start to finish? A story that sounds like a resume bullet, such as 'I built a caching layer', answers none of these.
- Stakes — Says who was hurt and how much before the fix — Starts with the technology
- Ownership — 'I' for your actions, 'we' for the team's — 'We' all the way through
- Difficulty — Names what made it hard, and what had failed before — Sounds routine
- Result — A number with a before and after — 'It went well'
- Reach — Others reused it, or it changed how the team works — Ends at launch
The stories on this page are fictional examples. Build yours from your own work, with numbers you can defend.
What you will be able to do
- Pick three to five achievement stories that each show a different strength.
- Open every story with the stakes in one or two sentences.
- Separate your own decisions from the team's work without sounding boastful.
- Close with a measured result and what it changed beyond the project.
Interview questions
- What's your proudest professional accomplishment?
- Describe your biggest technical achievement
- Tell me about a time you exceeded expectations
- What impact have you had in your current or previous role?
- Tell me about a project you started on your own
Sign up free to read the full topic
More Behavioral topics
Start free on Cariara · Coding problems · System design studio