How to Answer "Tell Me About a Time"

"Tell me about a time when..." is the most common behavioral interview question. It appears at every FAANG company. The key is having a structured framework and pre-prepared stories.

The Framework

Every "tell me about a time" question follows the same pattern:

graph TD
    Q["Receive question"]
    Identify["Identify competency\nbeing evaluated"]
    Search["Search story bank\nfor matching story"]
    Select["Select best story"]
    Deliver["Deliver with STAR\n(S:20% A:55% R:25%)"]

    Q --> Identify --> Search --> Select --> Deliver

    style Q fill:#D97A2B,stroke:#B86418,color:#fff
    style Identify fill:#FAF6EE,stroke:#E8DFC8
    style Search fill:#FAF6EE,stroke:#E8DFC8
    style Select fill:#FAF6EE,stroke:#E8DFC8
    style Deliver fill:#D4EDDA,stroke:#28A745

1. Identify the competency: What is the interviewer evaluating? Leadership? Conflict resolution? Technical challenge? Failure?
2. Select a matching story: Choose from your prepared STAR story bank. Pick a story that demonstrates the specific competency.
3. Deliver with STAR: Follow the STAR structure. Spend 20% on Situation/Task, 50% on Action, 30% on Result.

Common Variations

• "Tell me about a time you had a conflict with a teammate." : Evaluate: conflict resolution, communication.
• "Tell me about a time you had to make a difficult decision." : Evaluate: judgment, decision-making under uncertainty.
• "Tell me about a time you failed." : Evaluate: self-awareness, growth mindset, learning from failure.
• "Tell me about a time you went above and beyond." : Evaluate: ownership, initiative, impact.
• "Tell me about a time you disagreed with your manager." : Evaluate: courage, constructive disagreement.

Example Answer

Question: "Tell me about a time you had to push back on a technical decision."

Situation: "At my previous company, the team decided to use MongoDB for a new payment processing service. I believed PostgreSQL was a better fit because payment data requires ACID transactions."

Task: "I needed to convince the team to reconsider without undermining the architect who proposed MongoDB."

Action: "I prepared a one-page document comparing both databases on the specific requirements: transaction support, data consistency, and our team's existing expertise. I scheduled a 30-minute meeting and presented the comparison objectively. I acknowledged MongoDB's strengths for other use cases and proposed we use MongoDB for the logging service instead."

Result:"The team agreed to use PostgreSQL for payments and MongoDB for logging. The payment service passed all ACID compliance audits. The architect thanked me for the thorough analysis, and this comparison document became a reference for future database decisions."

Common Mistakes

• Talking about hypothetical situations : Always use real experiences. "I would have..." is not an answer.
• Not being specific enough : Vague answers signal lack of ownership. Use names, dates, numbers.
• Blaming others : Even if someone else was wrong, focus on what YOU did and what YOU learned.
• Forgetting the Result : Every story must end with a quantified outcome or lesson learned.
• Rehearsing too much : Practice enough to be fluent, but not so much that you sound robotic.

How to Prepare

1. List 8-10 significant experiences from your career.
2. Write each as a STAR story (1-2 sentences per component).
3. Map each story to 2-3 competency areas.
4. Practice telling each story in 2-3 minutes.
5. Practice with a friend or use InterviewSkool's behavioral mock interview.