Tell me about the project on your resume you're most proud of. Which part did you build yourself?

The interviewer asks this to check three things: whether you really built the project, how deeply you understand it, and whether you can explain a piece of technical work so someone else understands it.

A good answer takes about 2 minutes, in this order:

1. The problem: what the project does, and for whom. One sentence is enough.
2. Your role: for a team project, say clearly which part was yours, for example "I built all of the login and permissions". Don't say "we did" for everything.
3. One technical decision: which approach you chose, why, and what alternatives you considered. For example: "I stored images in file storage and kept only their paths in the database, so we wouldn't go over the database size limit."
4. One difficulty and how you got past it: a specific bug, and how you found its cause.
5. If you did it again: one thing you would do differently. This shows you can look back at your own work.

Avoid:

• Reciting a feature list as if you were reading the README.
• Claiming a part you can't answer the next question about. Interviewers often dig two or three levels deeper into exactly the part you claim.

Prepare ahead: for every project on your resume, write down the 5 points above and practise saying them out loud at least once.