“We rebuilt the onboarding flow.” It’s a useful opening: it gives the interviewer a project to picture. But if the whole answer stays at that distance, they can’t tell whether you found the problem, designed a change, wrote the code, or coordinated the release.

That doesn’t mean turning a team effort into a solo performance. A good account lets the listener follow your work and understand how it connected to everyone else’s.

Move in for one scene

Choose a moment when there was something to notice, decide, or resolve. You don’t need to walk through every stage of a six-month project. One decision can reveal how you work, especially if you explain what was at stake and what options were available.

Imagine a team improving customer onboarding. During two setup sessions, you notice a customer copying the same ID into three screens. You sketch a version that asks for it once. An engineer checks which services can share the ID, and the two of you agree on the first screens to change.

I noticed the repeated step and sketched an alternative. Our engineer checked what was technically possible, and together we chose where to start.

That answer is short, but the roles are visible. The observation and sketch belong to the speaker; the technical assessment belongs to the engineer; the choice is shared. You can make the same distinction whether your contribution was a difficult conversation, an analysis, or a small test.

Three people work on a shared paper layout while one marks a detail with a purple pencil.
Describe your part in the work while giving the team its due.

Name the work between milestones

Job titles and project milestones don’t always describe the interesting work. “I owned onboarding” might mean you arranged meetings, made the final call, or investigated why people were getting stuck. Pick a verb that says what happened: interviewed, compared, prototyped, challenged, documented, or followed up.

Then add enough context to make the action meaningful. What constraint did you work around? Who needed to be involved? In the example, the engineer’s assessment matters because a neat sketch alone couldn’t establish whether the services could share information. Naming that dependency makes the contribution more credible, not less.

Give the result an honest boundary

Say what you actually know. If you watched one later setup go more smoothly, you can describe that observation. It isn’t the same as knowing the change helped every customer or saved a measured amount of time. If a metric comes up, be ready to explain where it came from and what it covers.

Sometimes the result is unfinished. Perhaps the team tested a prototype but the release was postponed, or the change solved one problem and exposed another. That can still be a useful story. Tell the interviewer what you learned and where your view stops, rather than borrowing an outcome from the whole project.

If the work is confidential, prepare a version that leaves out names, figures, and sensitive details while retaining the decision you faced. You can explain the type of constraint without revealing a customer’s identity. Check what you’re allowed to share before the interview, so you aren’t deciding under pressure.

Practice for a follow-up

Try telling your story aloud, then ask someone what they think you personally did. If they can’t answer, find the sentence where “we” covers several different actions. Separate them without assigning yourself work you didn’t do.

Interview rehearsal

Who did what on the onboarding flow?

Interviewer
“When you say ‘we rebuilt it,’ which part did you do?”
Candidate
“I watched two customers copy the same ID into three screens. I sketched a version where they only entered it once. Our engineer checked where we could pass that ID along, and together we chose the first two screens to try.”
Try the follow-up question
Interviewer
“What did the sketch let you test?”
Candidate
“Whether someone could finish the second screen without entering the ID again. The engineer still had to check whether the services could share it.”

Prepare one layer deeper, too: why did you choose that approach, what did someone else contribute, and what would you change now? You don’t need a script for every possible question. You need the details close enough to hand that you can answer the one you’re asked.