Project retrospective formats

The written artifact lets interviewers arrive with targeted questions. Keep the brief compact enough to read, then reserve most live time for decisions, failures, collaboration, and impact.

• Opening and role: about five minutes
• Project scope and constraints: about five minutes
• Challenges and technical deep dive: twenty to twenty-five minutes
• Collaboration, metrics, reflection, and questions: the remaining time

A lighter round usually gives you roughly forty minutes and fewer prepared materials. The same evidence is required, but context must be compressed so the interviewer can probe.

• One-sentence problem and your mandate
• Two or three decisions with alternatives
• One hard failure or constraint
• Measured result and what changed in your judgment

The timeline is only a container. The signals are whether you can separate your work from the team’s, connect technical choices to constraints, quantify results, and reason beyond the rehearsed path.

• Ownership without exaggeration
• Technical depth at the target level
• Influence across the relevant scope
• Self-awareness about misses and trade-offs

Finish the prepared portion early. A candidate who speaks for thirty minutes without leaving room for questions prevents the strongest evidence—unscripted depth—from appearing.

• Target fifteen to eighteen minutes of prepared material
• Use transitions that invite questions
• Keep appendix detail ready but out of the main path
• Answer the question asked before adding context