An engineer told me last week that he lets his work speak for itself. If you can’t explain your work out loud, that same instinct is exactly why you’re still looking for a job.
Quick answer: To explain your work in an interview, lead with the business problem (not your task), signpost exactly three actions you took, and close on one number the business cares about. Keep each project to about 90 seconds, then hand the conversation back.
Why good people lose the final round
I’ve watched four people get bridesmaided this month. They made it to the final round, then got the email: “Everyone on the team loved you, but we went with someone else.”
Different roles, same leak. And it’s almost never strategy. In fact, strategy is what got them in the room. The resume worked, the networking worked, and four rounds of interviews went fine.
The problem is that nobody ever taught them to talk about their work. None of these people get paid to describe what they do. Instead, they get paid to ship. Ten years in, and not one performance review said, “Get better at explaining your work to a stranger in 30 minutes.”
So they got good at the thing they were paid for. Then the last round graded them on the thing they weren’t. By the final round, everybody still in the running can do the job. As a result, the tiebreaker between two qualified people is usually which one told the clearer story. That’s also why “more closely aligned” rejections sting so much: you didn’t lose on skill.
The curse of knowledge makes you a bad narrator of your own work
There’s a reason experts are often the worst at this. Chip and Dan Heath call it the curse of knowledge: once you know something well, you can’t easily imagine not knowing it.
They point to a Stanford study where people tapped out well-known songs on a table and predicted listeners would name about half of them. Listeners got roughly one in forty. The tappers could hear the melody in their heads. The listeners heard knocking.
That’s you describing a project you lived for 18 months. You hear the melody. Meanwhile, the panel hears “we refactored the pipeline and migrated to the new service.” You skip the steps that feel obvious, and those skipped steps are exactly where the value was.
How to explain your work in three translations
I run every client through the same system, and you can use it on each project you plan to talk about.
Step 1: Translate the task into the problem the business felt
Most people open with what they were assigned: “I led the migration to Kubernetes.” That’s the admitting nurse talking. The nurse saw the symptom. The doctor who diagnosed the disease gets the credit.
Open with the pain instead: “Deploys took four hours and broke production about once a week. Engineers were scared to ship on Fridays.” Now the listener cares before you’ve said a single word about what you did.
Test: if your first sentence contains a tool, a framework, or a project name, you started with the task. Rewrite it.
Step 2: Signpost exactly three moves
Next, tell them how many things you did, then number them. “I did three things. First, I mapped where deploys actually failed. Second, I got the two teams who owned the pipeline to agree on one standard. Third, I rolled it out one service at a time so nothing broke.”
This is signposting, and it works because interviewers remember almost nothing verbatim. Their notes are their memory. Three numbered moves are easy to write down, and those few lines in their notes are what gets read aloud when you’re not in the room.
Also, notice who’s doing the work in those sentences. “I mapped,” “I got,” “I rolled out.” If you say “we” for everything, the panel can’t tell what you did.
Step 3: Close on one number the business cares about
Finally, land it: “Deploy time went from four hours to 20 minutes, and we went three months without a production incident.”
You don’t need a perfect figure. You need to be directionally truthful, meaning in the right ballpark and honest about it. The number should connect to money, time, risk, or customers. If you already wrote strong resume bullet points, you’ve done half of this translation. Now say it out loud.
What this sounds like, before and after
Before: “So at my last company I was on the platform team, and we used a lot of Jenkins, and there was this big initiative to move to Kubernetes, and I was pretty involved in that, and it went well overall.”
After: “Deploys took four hours and broke production weekly, so engineers stopped shipping on Fridays. I did three things. I mapped where deploys failed, got the two pipeline teams onto one standard, and rolled it out service by service. Deploy time dropped from four hours to 20 minutes, and we went three months with zero incidents. Happy to go deeper on any of those.”
Same project, same person. However, only one version gives a panel something to repeat in the debrief.
Practice explaining your work to a stranger this week
You can fix this in a weekend, but you can’t fix it by thinking about it. It takes reps.
- Pick your three strongest projects.
- Write each one as three lines: problem, three moves, number.
- Say each out loud to someone outside your field, like a partner, a friend, or a neighbor.
- Ask them to repeat back the problem and your three moves. If they can’t, your version is still too close to the task.
- Record yourself once and listen back. Cut every “kind of,” “sort of,” and “I think.”
Most people I work with need five or six passes before a project sounds effortless. That’s normal. The goal is an answer that the hiring debrief can carry without you in the room.
FAQ
How long should I spend explaining one project in an interview?
Aim for about 90 seconds on the first pass. Give the problem, the three moves, and the number, then stop and invite follow-up questions.
What if I don’t know the exact numbers from my past work?
Use a directionally truthful estimate you can defend, like “roughly a 30% drop” or “about two hours saved per engineer per week.” Being in the right ballpark beats saying nothing.
Should I say “I” or “we” when I explain my work?
Say “I” for the actions you personally took and “we” only for the team outcome. Panels are trying to figure out what you’ll do on their team, so they need to hear your part.
What to do next
If you’ve been getting to final rounds and losing, it’s worth knowing what that stall is costing you each month. Run the job search cost assessment to get a real dollar figure in about 90 seconds.
If you want to turn your three translated projects into a small set of stories that answer almost any question, read Interview Stories: Build Five, Not Twenty Single-Use Ones next.
If you’d rather have someone listen to how you describe your work and tell you exactly where it loses the room, book a free strategy call.