Interview Recipes
Menu

Adaptability

How a candidate responds when the ground shifts: changing course on new evidence, staying effective through ambiguity and setbacks, and turning what happened into what they do differently.

The rehearsed version of adaptability is a conversion story: the candidate resisted the change, saw the light, and championed it by the end. Real adaptation is less tidy. It is what someone does in the first weeks of a reorg they didn't want, or in the first hour after a deadline collapses with no procedure to lean on.

These adaptability interview questions are built to get under the rehearsed version. They anchor on tight time windows (the first hour, the first day of recovery, the first few weeks) because concrete moves are hard to invent on the spot. They cover change imposed from above, plans knocked over by surprises, unclear expectations, critical feedback the candidate disagreed with, and the setback that genuinely hurt. What good answers share is visible behavior while still unconvinced or still rattled, not a verdict delivered from the far side of the story.

Ask a couple of them, then let the follow-up probes do the work; the red flags on each card catch the stories that skip straight to the happy ending.

Interview for it when

The plan will change under them, more than once.

Where this competency comes from

Adaptability is not our invention: it shows up, under different names, in every major validated competency framework. Our ten-competency taxonomy keeps what at least three of the four agree on. The full reasoning is in why structured interviews work.

The Great Eight (Bartram, 2005)
Adapting & Coping
UK Civil Service Success Profiles
Changing and Improving
US OPM general competencies
Adaptability, Resilience
Google’s four attributes
Googleyness (comfort with ambiguity)

In the O*NET content model it maps to the work activities Updating and Using Relevant Knowledge and the work styles Tolerance for Ambiguity · Adaptability · Stress Tolerance.

O*NET mapping adapted from the O*NET content model (U.S. Department of Labor), used under CC BY 4.0.

The questions

All 10 cards in full: the question, why it works, the follow-up probes, and the anchors to score against. Still choosing competencies? Plan the interview first.

adaptability

Tell me about a change at work you didn't choose and wouldn't have chosen — a reorg, a new direction, a new way of working. What did you do in the first few weeks?

Why this works

Change-champion stories are rehearsed; "wouldn't have chosen" takes that script away and leaves the real signal — the gap between private opinion and observable behavior. Adaptation shows in what someone does while still unconvinced, which is why the question asks for the first few weeks rather than the eventual verdict.

Follow-up probes

  • What was your first reaction, and who saw it?
  • What part of the old way did you hold onto longest?
  • When did you stop comparing everything to how it used to be?

What good looks like

Initial resistance acknowledged honestly, a visible decision to make it work while doubts remained, concrete changes to their own routine within weeks, and a fair account of what the change got right.

Red flags

A conversion story where they loved it by day two, quiet non-compliance recounted as principle, or a change from years ago still being relitigated in the interview room.

Card page · add to recipe

adaptabilityjuniorsituational

You're three weeks into a project you care about when your manager shelves it — priorities changed — and moves you to something less interesting, starting today. What do you do?

Why this works

The dilemma has no clean move: sulking is visible and costly, but letting three weeks of work evaporate without a trace is careless. It works for candidates with little work history, and the "less interesting" detail tests whether their effort is attached to the outcome or to their own enthusiasm.

Follow-up probes

  • What happens to the half-finished work?
  • What, if anything, do you say to your manager about the call?
  • What does your first day on the new assignment look like?

What good looks like

The shelved work closed out responsibly — documented, parked where others can find it — disappointment named without being performed, a real question about the reasoning, and full effort on the new thing from day one.

Red flags

Instant cheerfulness with no sign the loss registered, a campaign to reverse the decision dressed as questions, or the new assignment visibly starting at half throttle.

Card page · add to recipe

adaptability

Walk me through a time something you hadn't seen coming knocked your plan off course. What did the first day of recovery look like?

Why this works

Plans fail on contact all the time; the signal is the reflex that follows — re-sorting what still matters, giving up what can't be saved, and telling the right people early. Anchoring on the first day keeps the answer in observable moves instead of a tidy summary of the eventual save.

Follow-up probes

  • What did you deal with first, and what did you deliberately drop?
  • Who did you tell, and how quickly?
  • Could you have seen it coming — and what do you check now?

What good looks like

A disruption with real stakes, priorities re-sorted rather than everything pushed harder, the people affected told early, and an honest verdict on whether the surprise was foreseeable.

Red flags

Recovery that is purely extra hours with the plan itself unchanged, stakeholders finding out at the deadline, or a story that jumps from disaster straight to happy ending.

Card page · add to recipe

adaptability

Tell me about a work situation that turned urgent fast — something broke, a deadline collapsed — with no procedure to lean on. Walk me through your first hour.

Why this works

Urgency with no procedure strips away everything rehearsable, leaving default behavior: what they check first, when they pull in help, whether anyone gets told. The first-hour frame keeps the story concrete and stops it drifting into a speech about thriving under pressure.

Follow-up probes

  • What did you check or stabilize first, and why that?
  • When did you ask for help, and from whom?
  • What did you change so the same thing never surprises you twice?

What good looks like

A concrete first move with a reason behind it, whoever owned the stakes told early, help pulled in instead of heroics, and something changed afterward so the same surprise lands softer.

Red flags

The story is about the hours worked rather than the moves made, sole-hero framing where help was never an option, or the same fire has burned repeatedly with nothing learned.

Card page · add to recipe

adaptability

Tell me about a moment you were put on the spot without the answer — a question, a demo, a call going sideways. What did you do right then?

Why this works

Everyone rehearses the story where they thought fast and nailed it; asking for the moment they didn't takes the script away. The live move is the signal — buying time honestly, saying "I don't know" without unraveling — along with how fast they closed the gap afterward.

Follow-up probes

  • What exactly did you say in that moment?
  • How did you close the gap, and how quickly?
  • What do you prepare differently now because of it?

What good looks like

A plain in-the-moment admission paired with a credible next step — "I don't know, here's how I'll find out" — steadiness without bluffing, and the follow-up actually delivered.

Red flags

A bluff retold as quick thinking, a gap that never got closed, or the example quietly morphing into one where they did know the answer after all.

Card page · add to recipe

adaptability

Describe a moment at work that got heated — raised voices, real frustration in the room. What did you do while it was still hot?

Why this works

Composure claims are cheap, so the question asks for the mechanics of one charged moment: what they said, what they deliberately didn't, and how the temperature came down. The point isn't suppressing a reaction — it's staying able to work the problem while others momentarily can't.

Follow-up probes

  • What did you say first once it escalated?
  • What did you deliberately not say or do?
  • What happened to the issue itself once things cooled?

What good looks like

The trigger described without villainizing anyone, a deliberate cooling move — slowing the pace, naming the disagreement, taking it offline — and the underlying issue still dealt with afterward.

Red flags

Composure that was really checked-out silence with the issue left to rot, quiet pride in winning the shouting match, or a story where everyone else is unreasonable.

Card page · add to recipe

adaptability

Describe a piece of work where the expectations and rules were never made clear. How did you decide what good enough looked like?

Why this works

Ambiguity can't be answered from process memory — the candidate has to show how they built their own scaffolding: what they inferred, what they asked, what they simply tried. It also locates their stalling point: how long they can keep moving without certainty before freezing or escalating everything.

Follow-up probes

  • Where did you look for guidance before inventing your own?
  • What call did you get wrong, and how did you catch it?
  • How did the people relying on you know where things stood?

What good looks like

Guidance hunted down before being invented — precedent, adjacent teams, the assigner's intent — provisional calls made and revisited without drama, and their own working rules made explicit for whoever came next.

Red flags

Stalled until instructions arrived, every judgment escalated upward, or the opposite: weeks of confident work in a direction nobody wanted, with no checkpoint along the way.

Card page · add to recipe

adaptabilityjunior

Think about the last time you were new — a job, a team, a client. What did you deliberately do to learn how things really worked there?

Why this works

Every workplace runs on unwritten rules, and the people who adapt fastest treat learning them as active work — watching, asking, testing small things — rather than waiting for onboarding to cover it. "Deliberately" pushes past "I settled in fine" to moves an interviewer can actually score.

Follow-up probes

  • What surprised you about how they worked, and how did you adjust?
  • Who did you learn the unwritten rules from, and why them?
  • What did you get wrong early because you didn't know yet?

What good looks like

Named tactics — shadowing, asking about norms, testing their understanding early — an unwritten rule they discovered and adapted to, and an early misstep owned along with what it taught them.

Red flags

Settling in described as passive absorption, nothing about the place surprised them, or the adjustment ran one way — the new environment was expected to adapt to them.

Card page · add to recipe

adaptability

Tell me about a piece of critical feedback you disagreed with when you first heard it. What did you do with it?

Why this works

"Tell me about feedback" invites the polished growth story; adding disagreement forces the harder account — sitting with a judgment that felt wrong and working out which part of it was true anyway. Whether anything visibly changed afterward separates absorbing feedback from surviving it.

Follow-up probes

  • What was the feedback, as close to word-for-word as you can?
  • Which part turned out to be right?
  • What did the person who gave it see you change?

What good looks like

The feedback restated fairly rather than caricatured, a real reckoning — part accepted, the genuine disagreement raised with the giver directly — and a specific change the giver could verify.

Red flags

The giver was simply wrong and that's the whole story, agreement performed in the room and dropped afterward, or the only example on offer is praise lightly disguised as criticism.

Card page · add to recipe

adaptability

Tell me about a work setback that genuinely knocked you back — a failure, a lost deal, a collapsed project. What did the next month look like?

Why this works

Failure stories get told for the lesson; this asks for the recovery, which is much harder to script. The pace of regrouping, what got rebuilt first, and whether the lesson became a different way of working — rather than a better story — are where resilience is actually visible.

Follow-up probes

  • What did the first week after look like, concretely?
  • What did you rebuild or restart first, and why that?
  • What do you do differently today that traces back to it?

What good looks like

A setback with real stakes owned without deflection, a recovery told in visible steps rather than a mood arc, and a current, checkable practice that traces straight back to it.

Red flags

A trivial setback carrying a grand resilience narrative, a recovery summarized as "I moved on", or the claimed lesson nowhere to be seen in how they describe later work.

Card page · add to recipe

Often assessed alongside

A good interview covers four to six competencies, chosen for what the job turns on. Roles that need adaptability usually also lean on:

Hiring for a role that turns on adaptability?

Plan the interview and three short steps will work out which competencies your role needs, no account required. Or subscribe and get new vetted questions and interview guides as we publish them.