How to answer "tell me about a time" questions with substantive evidence

The short answer

Behavioural interview questions - the "tell me about a time when..." family of questions that hiring teams use to evaluate how candidates have approached real situations in their past work - are designed to surface specific evidence of behavioural capability. Strong responses provide that evidence: concrete situations, specific reasoning at the time, observable outcomes, honest reflection on what worked and what didn't. Weak responses rely on rehearsed templates that signal preparation depth without surfacing the underlying behavioural capability.

The gap between strong and weak behavioural responses is substantial in evaluation. Evaluators have been trained to distinguish between candidates who can articulate specific past behaviour with substantive evidence and candidates whose responses follow recognisable templates with generic content. The distinction matters because behavioural responses are increasingly weighted alongside technical evaluation in modern hiring decisions, particularly for mid-level and senior roles.

This guide walks through what behavioural evaluation actually measures, how to prepare responses that surface genuine evidence rather than rehearsed templates, and what specific patterns evaluators look for in strong responses. The perspective is from the assessment infrastructure side - Skolarli's behavioural assessment infrastructure runs at scale, and the patterns that distinguish strong evaluation outcomes from weak ones are clearer than most candidates realise.

What behavioural evaluation actually measures

Worth being precise about what evaluators are trying to surface through behavioural questions, because the dimensions matter for how you should prepare your responses.

Behavioural evaluation tries to surface evidence of how you actually behave in specific situations, based on the premise that past behaviour predicts future behaviour better than hypothetical reasoning does. When an evaluator asks "tell me about a time when you handled a disagreement with a colleague", they're not testing whether you can construct a plausible-sounding answer - they're trying to evaluate how you actually handle disagreements based on specific evidence from your past.

The specific dimensions evaluators are watching for:

Specificity of the situation. Strong responses describe specific situations with concrete details - the actual context, the specific people involved (without using names), the timeline, the constraints, the stakes. Weak responses describe generic situations that could apply to anyone. The specificity signals genuine recall versus rehearsed construction.

Reasoning at the time of the event. Strong responses articulate what you were thinking at the time of the situation - what you considered, what alternatives you weighed, what factors influenced your decision, what concerns you had. Weak responses describe what you did without surfacing the reasoning process. The reasoning articulation reveals judgment patterns that behavioural responses are designed to measure.

Observable actions you took. Strong responses describe specific actions you took - concrete things you said, decisions you made, conversations you had, steps you executed. Weak responses describe outcomes or feelings without specifying the actual actions. The action specificity supports verification through follow-up questions; rehearsed responses often collapse when probed for action details.

Honest acknowledgement of complexity. Strong responses acknowledge complexity in the situation - uncertainty about the right approach, valid concerns from other people, tradeoffs you accepted, things you might do differently with hindsight. Weak responses present clean narratives where you made obviously correct decisions. The complexity acknowledgement signals genuine reflection versus narrative construction.

Specific outcomes and consequences. Strong responses describe concrete outcomes - what actually happened, what changed because of the actions, what feedback you received, what implications followed. Weak responses describe vague positive outcomes without concrete consequences. The outcome specificity supports evaluation; vague outcomes don't.

Reflection that demonstrates learning. Strong responses include genuine reflection - what you learned, what you'd approach differently, what the situation taught you about yourself or your work. Weak responses either skip reflection entirely or include performative reflection that doesn't demonstrate genuine learning. The reflection quality signals learning patterns that matter for role performance.

Response to follow-up probing. Strong responses hold up under follow-up questions - "what did the other person say in response?", "why did you choose that approach over X?", "what would you do differently?". Weak responses collapse under probing because they were constructed for the initial question without genuine evidence underneath. The probing response is often where rehearsed templates fail visibly.

The pattern across these dimensions: behavioural evaluation measures whether you have genuine behavioural evidence from your past experience and can articulate it substantively, not whether you can construct plausible-sounding answers to behavioural questions.

Why rehearsed STAR templates often produce weaker outcomes

The STAR framework - Situation, Task, Action, Result - is genuinely useful as scaffolding for organising behavioural responses. It helps candidates surface the components of a response (context, what was needed, what they did, what happened) in a structure evaluators can follow. The framework itself works well.

What produces weaker outcomes: treating STAR as a memorisation template rather than as a framework for surfacing genuine evidence. Candidates who memorise specific STAR-structured stories and deploy them as scripted responses face two structural challenges.

Pattern recognition by experienced evaluators. Evaluators who conduct many behavioural interviews develop pattern recognition for rehearsed templates. Specific phrases ("I took the initiative to...", "I noticed an opportunity to...", "I implemented a solution that...") and structural patterns (clean narrative arc, problem-solution-success structure, generic positive outcome) get recognised as rehearsed rather than as genuine. The recognition itself doesn't disqualify the response, but it shifts evaluation toward probing the underlying evidence, where rehearsed responses often collapse.

Limited transferability across questions. Memorised STAR stories typically work well for the specific question they were prepared for and weaker for questions with subtle variations. "Tell me about a time you handled a difficult colleague" differs from "tell me about a time you had to influence someone who didn't report to you" differs from "tell me about a time when you disagreed with a senior colleague about a technical decision". Each requires a different specific situation and different reasoning patterns. Rehearsed templates designed for one question apply awkwardly to variations.

Vulnerability to follow-up probing. Strong evaluators probe behavioural responses with follow-up questions - about specifics, about alternatives, about other people's perspectives, about what you'd do differently. Rehearsed templates often handle the initial question well but collapse when probed for evidence the template didn't anticipate. "What did your colleague actually say in response?" requires evidence; templates provide narrative structure but not necessarily evidence depth.

The honest framing: STAR framework as organising structure produces stronger responses than unstructured rambling. STAR framework as memorised script produces weaker responses than substantive evidence surfaced authentically. The preparation discipline that works develops the capability to surface genuine evidence, organised through the STAR scaffolding, with reasoning depth and honest reflection - not the capability to deploy memorised scripts.

How to prepare substantive behavioural responses

Given what evaluators measure, the preparation discipline that produces reliable outcomes focuses on surfacing genuine evidence from your past rather than constructing plausible-sounding narratives.

Map your past experiences to behavioural dimensions. Before specific question preparation, develop a mental inventory of situations from your past work that would surface different behavioural dimensions - situations involving collaboration challenges, disagreements you handled, decisions under ambiguity, mistakes you made and recovered from, technical decisions you led, situations where you influenced people without authority, projects where you needed to learn new capabilities quickly. Each situation provides evidence for multiple potential behavioural questions; the inventory becomes the source material for substantive responses.

Develop the situations with substantive specificity. For each situation in your inventory, develop the specifics - the actual context, the timeline, the people involved (without names), the constraints, the stakes, your reasoning at the time, the actions you took, the outcomes, what you learned. Write these out if it helps; spoken articulation of written material develops the muscle for genuine recall during actual interviews. The specificity is what distinguishes strong responses from rehearsed templates.

Practise articulating reasoning at the time of events. This is the dimension where most candidates underperform. Articulating what you were actually thinking during a past situation - what you considered, what concerned you, what alternatives you weighed - requires deliberate practice. The reasoning is often clearer to you in your head than in your speech; practising articulation develops the capability to surface it under interview pressure.

Practise acknowledging complexity honestly. Strong behavioural responses include genuine complexity acknowledgement - uncertainty about the right approach, valid concerns from other people, tradeoffs you accepted, things you might do differently. Practise this acknowledgement explicitly because it cuts against the natural tendency to present clean narratives where you made obviously correct decisions. The complexity acknowledgement is often what distinguishes substantive evidence from constructed narrative.

Prepare for follow-up probing. For each situation in your inventory, anticipate the follow-up questions an evaluator might ask. What did the other person say?", "Why did you choose that approach?", "What would you do differently?", "How did you know your decision was the right one at the time?". Prepare specific answers to these follow-up questions because the probing is where rehearsed responses typically fail.

Develop multiple situations for common behavioural dimensions. Rather than memorising one situation per behavioural dimension, develop two or three situations that would surface each dimension. This provides flexibility during actual interviews - you can select the situation that best fits the specific question phrasing rather than forcing a single memorised situation to fit varying questions.

Practise the response structure through articulation, not memorisation. Use the STAR framework as scaffolding for organising responses, but practise the responses through articulation rather than memorisation. Speak through situations multiple times, varying the emphasis and detail based on what each practice run reveals. The goal is fluency with the situations rather than memorisation of specific phrasings. Fluency transfers across question variations; memorisation doesn't.

Develop reflection depth for each situation. For each situation in your inventory, develop genuine reflection - what you learned, what you'd approach differently, what the situation taught you. The reflection is often the dimension that distinguishes strong responses from adequate ones; performative reflection ("I learned the importance of communication") doesn't substitute for substantive reflection ("I learned that I was anchored on the technical solution and underweighted the stakeholder concerns - now I try to identify stakeholder reasoning explicitly before committing to a technical direction").

What strong behavioural responses sound like

A specific example showing the difference between rehearsed and substantive responses might help.

The question: "Tell me about a time when you had to influence a decision without having formal authority."

A rehearsed STAR response might sound like:

In my previous role, I noticed an opportunity to improve our deployment process. The team had been using a manual deployment workflow that was creating delays. I took the initiative to research alternatives and proposed a CI/CD pipeline implementation. I worked with the team to gain alignment and we successfully implemented the new pipeline. As a result, deployment time decreased by 60% and the team adopted the approach across other services.

This response has STAR structure but signals as rehearsed because: the situation is generic (could describe many candidates' experiences), the reasoning isn't articulated ("I noticed an opportunity" doesn't reveal thinking), the actions are summarised rather than specific ("worked with the team to gain alignment" doesn't describe what that looked like), the outcome has a clean percentage without context for how it was measured, and complexity is absent.

A substantive response to the same question:

About eighteen months into my role at [previous company], the engineering team was struggling with deployment delays - most deploys were taking 90 minutes or more because of a manual integration test phase. I'd been thinking about whether we could move to a CI/CD pipeline, but I wasn't on the infrastructure team and I couldn't make the call unilaterally. The infrastructure lead had pushed back on previous CI/CD proposals because of concerns about test reliability - the manual phase had developed because earlier automated approaches had let flaky tests reach production.

My approach was to start with the concern rather than with the solution. I spent about two weeks documenting the actual failure modes from the previous CI/CD attempt - looking at the post-mortems, talking to the engineers who'd been involved. About 70% of the issues traced to two specific test categories that had inherent reliability problems. I proposed a hybrid approach where those two categories stayed in the manual phase while everything else moved to CI/CD.

The infrastructure lead was sceptical initially - they thought the hybrid approach would create complexity. We had probably three conversations over two weeks where I worked through the specific implementation. What changed their mind was actually a specific concern they raised - what happens when the categorisation needs to change as tests evolve. We agreed to add a quarterly review of which tests belonged in which phase. The hybrid approach went live about three months later. Deployment time dropped to around 35 minutes for the CI/CD portion, with the manual phase still taking longer when it was needed.

Looking back, the thing I'd do differently is start the conversation with the infrastructure lead earlier - I spent a lot of time on the documentation phase before I really engaged with them, and some of that documentation work could have been more focused if I'd understood their specific concerns from the beginning. The lesson I took was about anchoring conversations on the other person's concerns rather than on your own proposal.

This response is meaningfully stronger because: the situation is specific (eighteen months in, particular context, specific previous attempt), the reasoning is articulated (concerns about test reliability, hybrid approach as response to specific failures), the actions are concrete (documenting failure modes, three conversations, specific implementation approach), the outcome includes both success and ongoing complexity (categorisation review, manual phase still taking longer), and the reflection includes genuine learning ("start the conversation earlier", "anchor conversations on the other person's concerns").

The substantive response provides evidence; the rehearsed response provides narrative. Evaluators distinguish between them readily.

Common behavioural question categories worth preparing for

Most behavioural interview questions cluster into several common categories. Worth developing inventory situations for each category so you have substantive evidence available regardless of the specific question phrasing.

Collaboration and influence questions. Questions about working with difficult colleagues, influencing without authority, handling disagreement, working across functions, building consensus, supporting team members.

Decision-making under ambiguity. Questions about decisions you made with incomplete information, situations where the right answer wasn't clear, tradeoffs you accepted, judgment calls under pressure.

Failure and recovery questions. Questions about mistakes you made, projects that didn't go well, decisions you'd reverse with hindsight, situations where you were wrong. These questions are often where candidates underperform because the temptation is to deflect; strong responses engage honestly with failure.

Learning and growth questions. Questions about learning new capabilities, adapting to changes, situations that taught you something significant, areas where you've developed.

Technical leadership questions. Questions about technical decisions you led, system designs you owned, technical disagreements you navigated, situations where you took technical responsibility.

Customer or stakeholder questions. Questions about handling difficult stakeholders, balancing competing priorities, customer impact decisions, situations where you advocated for users or stakeholders.

Speed and pressure questions. Questions about delivering under tight timelines, handling crises, prioritising under pressure, making decisions when speed mattered.

Values and ethics questions. Questions about situations where you faced ethical considerations, decisions where your values were tested, situations where you chose principle over expediency.

For each category, having two or three specific situations from your past that provide substantive evidence - with reasoning, actions, outcomes, and reflection developed - gives you flexibility during actual interviews to select the situation that best fits the specific question.

Where preparation effort produces strongest returns

A few honest observations about where behavioural preparation effort produces strongest returns:

The situation development work matters more than the response rehearsal. Spending preparation time developing your inventory of past situations with substantive specificity produces better returns than spending preparation time rehearsing specific responses. The situations become source material that supports varied responses; rehearsed responses don't transfer to question variations.

Articulation practice through speaking produces capability that writing doesn't. Behavioural responses get delivered through speech, often under pressure. Practising the articulation through speaking - to yourself, to a practice partner, recorded for self-review - produces capability that written preparation alone doesn't develop.

Follow-up probing preparation is undervalued. Most candidates prepare for initial behavioural questions but not for the follow-up probing that strong evaluators apply. The follow-up preparation produces capability that distinguishes substantive responses from those that initially seem strong but collapse under probing.

Recent situations work better than ancient ones. Situations from the last 2-3 years typically produce stronger responses than situations from 5+ years ago because the recall is sharper and the reasoning is more accessible. For senior candidates with longer careers, recent situations also signal that you're still developing rather than coasting on distant accomplishments.

Honest reflection on failure produces stronger responses than performative success. Candidates often avoid failure questions because of the temptation to deflect. Strong responses engage honestly with failure, articulate what you learned, and demonstrate the growth that followed. This is genuinely harder preparation work but produces meaningfully stronger evaluation outcomes.

Senior candidates need more substantive reasoning depth. Junior behavioural responses can be carried by enthusiasm and clear narrative. Senior behavioural responses need depth - articulation of judgment patterns, acknowledgement of complexity, reflection that demonstrates senior practitioner wisdom. The preparation discipline scales with role seniority.

Where Skolarli's infrastructure fits behavioural preparation

For candidates who want to verify their behavioural articulation capability before actual interviews, Skolarli's verified candidate assessments include behavioural and scenario-based components that use the same evaluation infrastructure hiring teams use for actual hiring decisions. The verified credentials provide evidence of your articulation capability that supports your candidacy alongside other evaluation results.

For deeper context on how hiring teams design behavioural evaluation, the Operator's Compass post on behavioural assessment for junior and mid-level hiring covers the evaluator-side perspective on what behavioural assessment is designed to measure and how it's calibrated. Understanding the employer-side view of behavioural evaluation helps candidates anticipate what evaluators are watching for.

For practice with the articulation discipline specifically, mock interviews with experienced engineers or paid mock interview services produce capability that solo practice doesn't develop. The conversational pressure of real-time articulation differs substantially from the comfort of preparation, and mock interview experience reduces the novelty factor of that pressure during actual evaluations.

For candidates building their inventory of behavioural situations, deliberate reflection on past work - written notes about specific situations, conversations with mentors or coaches about your behavioural patterns, structured self-review of recent professional experiences - produces source material that supports substantive responses across varied questions.

About this piece

This post is part of the Skolarli Candidate's Compass, an analytical series from Skolarli Akademy Research providing candidate-side preparation guidance written from the assessment platform perspective. The series complements the Buyer's Compass, Operator's Compass, and Engineering Hiring at Scale series.

Skolarli Akademy Research is the editorial arm of Skolarli Edulabs Pvt. Ltd., publishing analysis on learning, hiring, and assessment infrastructure for both practitioners and candidates. Findings are reviewed by Skolarli's founders and product leaders before publication.

Reviewed by Jayalekshmy Nair, Co-founder & CTO, Skolarli.