Critical thinking interview questions
Critical thinking interview questions test how a candidate reasons, not what they know: whether they weigh evidence, notice their own assumptions, and change their mind when the facts do. The 13 below force reasoning into the open — most work best when you push past the first answer and ask "how do you know?"
All 13 questions
Core critical thinking interview questions
- 01Tell me about a time you changed your mind about something important at work. What evidence moved you?
- 02Describe a time a number everyone trusted turned out to be wrong. How did you catch it?
- 03Tell me about a consensus on your team you concluded was wrong. How did you test your own reasoning before pushing back?
- 04What's something you believed about your field for years that you no longer believe? What dismantled it?
- 05Tell me about a good decision of yours that produced a bad outcome. How do you judge that decision now?
Critical thinking questions about AI output
- 06How do you decide whether an AI answer is trustworthy enough to act on? Walk me through the last time you made that call.
- 07What's a question you wouldn't ask an AI tool, because you couldn't evaluate the answer?
- 08Tell me about a time an AI tool gave you an accurate answer that still pointed you toward the wrong conclusion. What was missing?
- 09When your own analysis and an AI tool's disagree, how do you work out which one is wrong? Give me a recent case.
Critical thinking questions for judgment under uncertainty
- 10Here's a claim: 'Our best people leave because of pay — turnover is up and exit interviews mention salary.' What would you want to know before accepting it?
- 11Two credible sources give you contradictory answers and the decision is due tomorrow. How do you reason your way to a recommendation?
- 12A vendor's case study claims a 3x improvement and your team wants to buy. What do you ask before you believe the number?
- 13Pick a position you argued for recently. Now argue the other side as convincingly as you can.
Questions 1–5
Core critical thinking interview questions
Tell me about a time you changed your mind about something important at work. What evidence moved you?
A strong answer names the original position, the specific evidence that overturned it, and what the candidate did publicly after changing course. Candidates who can't produce one example usually defend positions instead of testing them.
What to look for
- Names the original position honestly instead of softening it in hindsight.
- The trigger is evidence — data, a user, a failed test — not social pressure.
- Updated publicly and adjusted the work, not just their private opinion.
Example answerRed flags
Example answer
I pushed for annual pricing for two quarters — the model said it would lift cash flow. Then win-loss calls showed we were losing mid-market deals specifically over the upfront commitment. I brought the recordings to the same forum where I'd made the original case and proposed monthly with an annual discount. Retention paid for the cash-flow hit.
Red flags
- Can't recall ever changing their mind on anything that mattered.
- The 'change' was just deferring to whoever outranked them.
Describe a time a number everyone trusted turned out to be wrong. How did you catch it?
Strong answers show the candidate noticed a mismatch between the metric and observable reality, traced the number to its source or definition, and fixed both the figure and the process that produced it.
What to look for
- Noticed because something didn't reconcile with reality, not by accident.
- Traced the number to its definition or source rather than arguing about it.
- Fixed the pipeline or definition, not just the one report.
Example answerRed flags
Example answer
Our dashboard said trial-to-paid conversion was 22%. Sales kept saying deals felt scarcer than that. I pulled the raw events and found the query counted plan upgrades by existing customers as conversions — the real figure was 14%. We'd been celebrating a broken number for two quarters. I rewrote the definition and added a monthly source check.
Red flags
- Accepts any number that arrives from a dashboard or a senior person.
- Found the error but let the team keep using the flattering figure.
Tell me about a consensus on your team you concluded was wrong. How did you test your own reasoning before pushing back?
The strong answer includes a genuine self-check — hunting for disconfirming evidence, asking who disagrees and why — before the challenge, and a pushback built on that evidence rather than on being contrarian.
What to look for
- Looked for evidence they were wrong before arguing they were right.
- Can articulate the strongest version of the consensus view.
- Pushed back with specifics, and accepted the outcome if overruled.
Example answerRed flags
Example answer
Everyone agreed churn was a product-quality problem. Before disagreeing I interviewed eight churned customers expecting to confirm it — five had left over an onboarding gap, not bugs. I wrote up both explanations with the interview notes and flagged what would prove me wrong. We fixed onboarding first, and churn dropped by a third.
Red flags
- Being against the consensus is the whole story — their own view was never tested.
- Presents themselves as the only clear thinker in every room.
What's something you believed about your field for years that you no longer believe? What dismantled it?
This tests intellectual humility on the candidate's own expertise. Strong answers name a real professional belief, the specific evidence or experience that broke it, and what they do differently now because of it.
What to look for
- The abandoned belief is professional and load-bearing, not trivia.
- Points to the specific evidence or experience that broke it.
- The update changed their current practice in a checkable way.
Example answerRed flags
Example answer
I believed more data always meant better decisions, so I'd delay calls waiting for one more analysis. A launch we studied for six weeks got beaten by a competitor who shipped in two and learned from the market instead. Now I ask what the extra data would change — if the answer is 'nothing decisive', we decide.
Red flags
- Nothing they believed five years ago has changed — a static model of a moving field.
- The dismantled belief is fashionable to abandon and cost them nothing.
Tell me about a good decision of yours that produced a bad outcome. How do you judge that decision now?
Strong candidates separate decision quality from outcome quality: they re-examine the reasoning against what was knowable at the time, own genuine process errors, and don't rewrite sound logic just because the result stung.
What to look for
- Evaluates the reasoning against what was knowable then, not hindsight.
- Distinguishes bad process from bad luck without hiding behind either.
- Would make the same call again — or names precisely which input was missing.
Example answerRed flags
Example answer
We picked the vendor with the stronger security posture over the cheaper one; six months in they were acquired and support collapsed. The reasoning holds — acquisition risk wasn't knowable from our diligence. What I did change: contracts now carry an exit clause tied to support SLAs, because that part was foreseeable.
Red flags
- Judges every past decision purely by how it turned out.
- No outcome has ever prompted a review of how they decide.
Questions 6–9
Critical thinking questions about AI output
2026 · AIHow do you decide whether an AI answer is trustworthy enough to act on? Walk me through the last time you made that call.
A strong answer shows a working verification heuristic — stakes, checkability, the model's known weak spots — applied to a real recent case, not a policy statement about always double-checking everything.
What to look for
- Scales verification to stakes and reversibility, not a flat rule.
- Knows which question types the tools fail on, from their own use.
- The recent example is real and specific, with the check they actually ran.
Example answerRed flags
Example answer
Last week a model summarized new EU packaging rules for a client memo. Regulatory plus client-facing means full verification: I pulled the two directives it cited and found one had been superseded. For internal brainstorming I skip all of that. My rule is that the cost of being wrong sets the depth of the check.
Red flags
- Trusts fluent output by default — verification has no trigger.
- Claims to verify everything, which means they've never weighed the cost of checking.
What's a question you wouldn't ask an AI tool, because you couldn't evaluate the answer?
This probes whether the candidate knows the edge of their own competence. Strong answers name a domain where they can't tell good output from bad, and route those questions to verifiable sources or experts instead.
What to look for
- Names a real domain where they can't judge output quality.
- Understands that fluent and correct are different properties.
- Has an alternative route: primary sources, an expert, or declining to answer.
Example answerRed flags
Example answer
Legal interpretation. I can check a model's marketing copy or SQL because I'll see the failure. If it tells me a contract clause is enforceable, the output reads identical whether it's right or wrong — I have no error signal. Those questions go to counsel, and I use the model only to prepare sharper questions for that conversation.
Red flags
- There's no question they'd hesitate to ask — they can 'usually tell' when output is wrong.
- Confuses topics they find boring with topics they can't verify.
Tell me about a time an AI tool gave you an accurate answer that still pointed you toward the wrong conclusion. What was missing?
Strong answers distinguish factual accuracy from sound framing: the output was technically right but omitted context, a base rate, or a rival explanation — and the candidate now checks for what's absent, not just what's wrong.
What to look for
- The example shows framing or omission, not a simple factual error.
- Spotted what was missing themselves, before the damage compounded.
- Now interrogates output for absent context, not just incorrect claims.
Example answerRed flags
Example answer
I asked for our top support-ticket drivers and the analysis was correct: password resets, number one. I nearly staffed for it before noticing the model had no severity data — resets were frequent but trivial, while a rare billing bug was costing real churn. Right numbers, wrong conclusion. Now I ask what data the tool couldn't see before acting.
Red flags
- The only failure mode they can imagine is factual error.
- Blames the tool without changing how they frame requests or check output.
When your own analysis and an AI tool's disagree, how do you work out which one is wrong? Give me a recent case.
The strong move treats disagreement as information: locate the exact point where the two analyses diverge — inputs, definitions, or logic — and test that point, rather than defaulting to self-trust or tool-trust.
What to look for
- Locates the precise step where the two analyses diverge.
- Tests the divergence against ground truth instead of picking a side.
- Has been wrong in both directions before, and says so.
Example answerRed flags
Example answer
My forecast said we'd miss the quarter; the model's said we'd land it. Instead of averaging them, I diffed the assumptions and found one disagreement — it weighted a pipeline stage by last year's conversion rates, which a process change had made stale. My number held. The quarter came in 4% under my forecast.
Red flags
- Automatically trusts whichever answer they liked more to begin with.
- Never runs their own analysis anymore, so disagreement can't even surface.
Questions 10–13
Critical thinking questions for judgment under uncertainty
Here's a claim: 'Our best people leave because of pay — turnover is up and exit interviews mention salary.' What would you want to know before accepting it?
A strong answer interrogates the evidence: who counts as best, turnover against what baseline, whether exit interviews are candid, and what rival explanations fit the same facts. The reflex to probe matters more than the conclusion.
What to look for
- Questions the definitions first — 'best people', 'up' against which baseline.
- Knows exit-interview data skews toward safe, socially acceptable answers.
- Generates at least one rival explanation that fits the same facts.
Example answerRed flags
Example answer
First I'd ask up compared to what — last year, industry, or just a bad quarter. Then who's actually leaving: if it's regretted attrition, from which teams and managers? Salary is the easiest thing to say on the way out. I'd compare the offers they accepted elsewhere and check whether leavers cluster under two managers before touching pay bands.
Red flags
- Accepts the framing and jumps straight to fixing compensation.
- Pure skepticism with no path to what evidence would settle it.
Two credible sources give you contradictory answers and the decision is due tomorrow. How do you reason your way to a recommendation?
Strong answers diagnose why the sources differ — scope, timeframe, definitions, incentives — decide what's resolvable before the deadline, and deliver a recommendation that names its remaining uncertainty instead of hiding it.
What to look for
- First move is diagnosing why credible sources disagree, not picking one.
- Separates what can be resolved by the deadline from what can't.
- The recommendation states its confidence and what would change it.
Example answerRed flags
Example answer
This happened with two market-size reports, 5x apart. In an afternoon I found they defined the market differently — one included services revenue. Neither was wrong; the question was which definition matched our decision. I recommended entry using the narrower figure, flagged the spread, and named the one number to validate in the first quarter.
Red flags
- Picks the source that supports what they wanted to do anyway.
- Delivers the recommendation with false confidence, uncertainty erased.
A vendor's case study claims a 3x improvement and your team wants to buy. What do you ask before you believe the number?
Strong candidates treat a vendor's number as an argument, not a fact: 3x against what baseline, measured how, on whose workload, selected from how many customers — and what a cheap independent test would show.
What to look for
- Asks for the baseline and the measurement method before anything else.
- Spots survivorship: case studies show the best customer, not the typical one.
- Proposes a cheap independent test — a pilot with success criteria set in advance.
Example answerRed flags
Example answer
3x of what, measured how? A support tool once claimed 3x faster resolution — their baseline was customers with no ticketing system at all. I'd ask for the median customer's result, not the showcase, and how many trials never became case studies. Then a four-week pilot on our own tickets, with the pass bar agreed before we start.
Red flags
- Takes the headline number at face value because a named brand is on the slide.
- So skeptical no evidence could ever clear the bar — analysis becomes a veto.
Pick a position you argued for recently. Now argue the other side as convincingly as you can.
This live exercise shows whether the candidate genuinely understood the opposing case before winning the argument. Strong candidates produce the other side's best evidence, not a strawman, and their original position gets sharper for it.
What to look for
- The counter-argument uses the other side's strongest evidence, not its weakest.
- Steps into the exercise without visible resistance or irony.
- Concedes the specific conditions under which the other side would be right.
Example answerRed flags
Example answer
I argued we should build our integration layer in-house. The honest other side: our two-person platform team becomes a permanent maintenance tax, the buy option ships in six weeks not six months, and 'vendor lock-in' cuts both ways — we'd be locked into our own worst code. If we can't hire a third platform engineer by Q2, buying is right.
Red flags
- The 'other side' is a strawman built to lose.
- Refuses, or visibly can't inhabit a view they disagree with.
Scoring rubric
| Score | Evidence anchor |
|---|---|
| 1 | Repeats received opinions and stays on the surface of every question; asked 'how do you know?', has nothing underneath the first claim. |
| 2 | Reasons in one direction only — collects evidence for the position already held, never generates a rival explanation, and treats confident sources as true. |
| 3 | Weighs evidence and spots obvious weak assumptions, but under pressure defaults to the familiar answer and changes their mind only when the counter-evidence is overwhelming. |
| 4 | Separates decision quality from outcome quality, hunts for disconfirming evidence unprompted, states uncertainty plainly, and updates visibly when the facts move. |
| 5 | Every claim arrives with its evidence and its confidence level, the strongest counter-argument is already inside the answer, and 'here's what would change my mind' comes unprompted. Reasoning you'd want in the room for your hardest calls. |
Frequently asked questions
What are good critical thinking questions for an interview?
The best critical thinking questions for interview settings make reasoning visible: ask candidates to evaluate a claim, argue against their own position, or explain how they caught a trusted number being wrong. Knowledge questions test recall; these test judgment.
How do you score reasoning quality in an interview?
Score the process, not the conclusion: did the candidate question definitions, generate rival explanations, name their uncertainty, and update on evidence? The 1–5 rubric above ties each level to observable behavior, so two interviewers score the same answer alike.
What do interview questions for critical thinking actually predict?
How someone behaves when the data is ambiguous and the confident answer is wrong — where judgment matters most. Candidates who probe assumptions in an interview keep probing them on vendor claims, forecasts, and AI output once hired.
How are critical thinking questions different from problem-solving interview questions?
Problem-solving questions watch a candidate work a concrete problem to a solution — process and execution. Critical thinking questions test the layer underneath: whether they trust the right evidence, spot weak assumptions, and change their mind when the facts demand it.
Can you assess critical thinking in a first-round interview?
Yes — two or three of these questions, each with one 'how do you know?' follow-up, separate reasoners from reciters in twenty minutes. Kira can run that subset by voice across every applicant before the human round.