What this prompt does
This prompt drafts a natural, confident 90-second spoken answer to the interview question "tell me about your team." It frames the model as a senior engineering leader and coach and is explicit that the answer should be said out loud, not read off a slide. It asks for six elements: a one-line mission framing, a concrete picture of the team's size and structure, a quantified win, an honest take on handling disagreement, a line on growing engineers, and a closing that ties back to the role.
Four variables tailor the answer. [role] is the position you're interviewing for, which the closing line ties back to. [company_type] calibrates tone and context. [team_and_stack] supplies the concrete size and technology details. [achievement] is the single quantified win the whole answer is anchored to. The guidance is to build everything around that one real win rather than listing responsibilities, because vague "we collaborate well" lines get tuned out fast. Folding in an honest line on conflict and a note on how you grow engineers rounds the answer into a picture of leadership, not just a status report on what your team shipped.
When to use it
- You're interviewing for an EM or tech-lead role and expect this question
- Your answer currently lists responsibilities instead of telling a story
- You want a quantified win to anchor the answer around
- You need an honest line on handling technical conflict
- You want to show how you grow engineers' careers, not just ship features
- You want three likely follow-ups prepped with angles
Example output
You get the full ~90-second answer written for speaking, covering the team's mission and place in the org, its size and stack and structure, a quantified win built around your achievement with your role in it, a short honest example of handling disagreement, a line on growing engineers, and a closing that ties the team to the role and company type. After the answer come three likely follow-up questions with one-line angles for each.
Pro tips
- Anchor the whole answer to the one real win in
[achievement]and let everything else support it, rather than listing responsibilities - Make
[achievement]genuinely quantified (e.g. cut p95 latency by 60% in a quarter) so the answer has a concrete spine - Give accurate
[team_and_stack]details so the team picture is specific and credible - Keep the disagreement example honest and short; a real tradeoff lands better than a sanitized non-answer
- Rehearse out loud and time it; 90 seconds on paper often overruns when spoken
- Tailor the closing to
[role]and[company_type]so the answer feels aimed, not generic - Review the three generated follow-ups and have a concrete example ready for each, since that is where a strong opening answer often unravels
