How to Talk About Your Work in an Interview

Your resume got you into the room. Then the interviewer says "tell me about a project you're proud of," and the same problem that used to live on paper walks in and sits down next to you.

Most engineers answer that question the way they'd write a status report. They describe the system, the constraints, the approach, and the outcome, accurately and in order. It's a perfectly correct answer, and it lands with almost no weight, because the interviewer wasn't asking for documentation. They were asking a different question underneath the stated one. They want to know what kind of problems you get handed, what you're like when things go sideways, and what changed because you were the one doing the work.

Here's a structure that answers the real question. Start with the stakes, not the system. Before you name a single technology, say why the project mattered, what was at risk, or what wasn't working. One sentence is enough. "We were three months from a delivery milestone and the integration kept failing" does more for your candidacy than five minutes of architecture description, because now the interviewer is listening to a story instead of reviewing a spec.

Then put yourself in the frame. Engineers habitually narrate in "we," and loyalty to the team is a good instinct, but an interview is one of the few places where the question is specifically about you. You don't have to claim the team's work. You have to be findable in the story. "My piece of it was the timing analysis, and what I found changed the approach" keeps both things true.

Then say what changed. Not what the system did, but what was different afterward because the work succeeded. Money saved, risk retired, a program kept on schedule, a customer kept. If you can't quantify it, describe it. "That failure mode never came back" is a result.

And then stop. The strongest interview answers are shorter than the ones most engineers give. Precision includes knowing where the story ends.

One more thing, because it trips up experienced people especially. Don't wait for the perfect question. Interviewers are often less skilled at interviewing than you are at your job, and many will never ask the question your best story answers. When there's an opening, take it. "That connects to something I worked on" is a legitimate bridge, and using it is not going off script. It's making sure the person deciding your candidacy actually meets you.

Figuring out which of your stories carry that kind of weight is real work, and it's hard to do from inside your own career. It's also exactly what my Strategic Career Diagnostic Session digs out. You can learn more at careercommunicationstrategies.com.