# How to explain a past project in an interview

> "Walk me through a project you worked on" tests whether you can explain a system to someone who was not there. A two-minute structure in six parts, and what to prepare.

Source: https://hintvo.com/blog/explain-a-past-project-in-an-interview | Last updated: November 20, 2026 | Reviewed: 2026-11-20

"Walk me through a project you worked on" sounds like the easy question. It is where many good engineers lose the room, because they describe the system from the inside. The interviewer was not there. Give them the problem first, three boxes, your own part, and the one decision that was hard.

## Six parts, about two minutes

1. **The problem, and who had it.** One sentence a non-engineer would follow.
2. **The constraints.** Scale, deadline, the thing you could not change.
3. **What was built.** Three boxes and how they talk. No more.
4. **Your part.** What you personally designed, wrote or decided.
5. **The hard decision.** One trade-off, with what you gave up.
6. **The result.** What changed, with a number if you have one, and what you would do differently.

## Three boxes

Whatever the real architecture was, describe it as three parts at first. An interviewer can hold three boxes in their head and ask about any of them. Twelve boxes, and they stop listening and wait for you to finish.

## Say I

"We migrated the order pipeline" tells the interviewer nothing about you. "I wrote the consumer and designed how we would run both systems side by side during the move" does. Give the team credit once, then talk about your own work.

## The hard decision is the interview

Almost every follow-up question will be about the trade-off, so choose it before the interview. Pick a decision where a reasonable person could have gone the other way, and be ready to argue the other side as well.

## Prepare two versions

- **Two minutes,** for the opening.
- **Ten minutes,** with the data model, the failure cases and the numbers, for when they say tell me more.

## Common mistakes

- Starting with the technology list.
- Spending a minute on company background.
- Describing a project where you cannot say what you did.
- Having no number at all. Even a rough one is better than none.

> **Where Hintvo fits:** with your CV and the job post added, answers to questions about your experience are built from the work you actually did, with the follow-ups an interviewer is likely to ask. Use Hintvo only where AI help is allowed. Check the rules of your company, school or interviewer first, and respect a no. See [the interview copilot](https://hintvo.com/interview-copilot).

## Related

- [AI interview copilot that answers from your CV](https://hintvo.com/interview-copilot.md): How does Hintvo AI help in a job interview, and how do I practice with it?
- [Behavioral interview questions: build your answers from your own CV](https://hintvo.com/blog/behavioral-interview-answers-from-your-cv.md): How do I prepare answers to behavioral interview questions?
- [System design interviews: a structure that holds when you are nervous](https://hintvo.com/blog/system-design-interview-structure.md): How do I structure a system design interview?
