BehavioralBeginner7 min readPart 3 of 7

Tell Me About a Time

“Tell me about a time when…” is the most common behavioral interview question, and it comes up at every FAANG company. The key is a clear framework and stories you have prepared in advance.

The frameworkHow it works

Every “tell me about a time” question can be handled the same way:

%%{init: {"look":"handDrawn","handDrawnSeed":7,"theme":"base","fontFamily":"Virgil, \"Segoe Print\", \"Comic Sans MS\", cursive","themeVariables":{"fontFamily":"Virgil, \"Segoe Print\", \"Comic Sans MS\", cursive","fontSize":"16px","primaryColor":"#fff4e6","primaryBorderColor":"#1e1e1e","primaryTextColor":"#1e1e1e","secondaryColor":"#e7f5ff","tertiaryColor":"#ebfbee","lineColor":"#1e1e1e","textColor":"#1e1e1e","mainBkg":"#fff4e6","nodeBorder":"#1e1e1e","clusterBkg":"#f8f9fa","edgeLabelBackground":"#ffffff","actorBkg":"#e7f5ff","actorBorder":"#1e1e1e","noteBkgColor":"#fff9db","noteBorderColor":"#1e1e1e"}}}%%
graph LR
  Q["hear the question"] --> I["identify the skill<br/>being tested"]
  I --> S["search your<br/>story bank"]
  S --> P["pick the<br/>best story"]
  P --> D["tell it with STAR"]
  class Q blue
  class I yellow
  class S,P violet
  class D green
classDef orange fill:#ffd8a8,stroke:#1e1e1e,color:#1e1e1e
classDef blue fill:#a5d8ff,stroke:#1e1e1e,color:#1e1e1e
classDef green fill:#b2f2bb,stroke:#1e1e1e,color:#1e1e1e
classDef red fill:#ffc9c9,stroke:#1e1e1e,color:#1e1e1e
classDef violet fill:#d0bfff,stroke:#1e1e1e,color:#1e1e1e
classDef yellow fill:#ffec99,stroke:#1e1e1e,color:#1e1e1e
classDef grey fill:#e9ecef,stroke:#1e1e1e,color:#1e1e1e
DiagramWork out what is being tested, then pick the story that proves it.

Identify the skill

What is the interviewer really checking? Leadership, handling conflict, a technical challenge, a failure?

Pick a matching story

Choose from your prepared STAR stories: the one that shows that specific skill best.

Tell it with STAR

Situation and Task about 20% of the time, Action about 55%, Result about 25%.

S + TActionResult
The same split as the STAR method: most of your time goes on what you did.

Common variations, and what they testCompare

“Tell me about a time…”What they are checking
…you had a conflict with a teammateResolving conflict, communication
…you had to make a difficult decisionJudgment, deciding under uncertainty
…you failedSelf-awareness, learning from mistakes
…you went above and beyondOwnership, initiative, impact
…you disagreed with your managerCourage, disagreeing constructively

Example answerExample

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 mistakesPitfalls

Hypothetical answersAlways use a real experience. “I would have…” is not an answer.
Too vagueVague answers suggest you didn’t own it. Use names, dates and numbers.
Blaming othersEven if someone else was wrong, focus on what you did and learned.
No resultEvery story ends with a measurable outcome or a lesson.
Over-rehearsedPractise until you are fluent, not until you sound like a recording.

How to prepareHow it works

List 8–10 experiences

The most significant things you have worked on or dealt with.

Write each as STAR

One or two sentences per letter.

Tag each story

Map every story to 2–3 skills it can prove.

Time yourself

Tell each story in 2–3 minutes.

Practise out loud

With a friend, or with an InterviewSkool behavioral mock interview.

Frequently asked questionsFAQ

How do I answer a "tell me about a time" question I have no story for?

Pause for five seconds, name the competency the interviewer is testing, then reach for the closest real experience you have. Interviewers accept a related example as long as it is genuine. If you truly have nothing, say so and describe the closest situation you observed and what you would have done differently.

Should I tell the same story for multiple behavioral questions?

You can reuse a story, but you must re-angle it for the competency being evaluated. A conflict story told for a leadership question should emphasise influence and ownership, while the same event told for a failure question should emphasise what you learned. Rotate across 8 to 10 prepared stories so no story is repeated in the same round.

Is it okay to talk about a team project as your own story?

Yes, as long as you are precise about your personal contribution. Say "I designed the caching layer" rather than "we built caching", and clearly credit teammates for their work. Interviewers can tell when a candidate claims the whole project, and that reads as inflated ownership rather than leadership.

Keep readingKeep reading

Ready to practice?

Reading is step one. Saying it out loud is step two.

Start a mock interview with Alex, get pushed on the parts you skip, and see your hiring signal right after.