By Johnny Campbell
Introduction
Business acumen is not knowing your company’s revenue figure. Anyone can read an earnings release. It’s whether a candidate can explain why the work they personally did last quarter made the organisation money or cost it money—and then reason sensibly about a trade-off they don’t own. A support lead with real commercial judgement can tell you roughly what an hour of their team’s time costs, why the refund policy they enforce exists, and what would break if it changed. A support lead without it will tell you they “always put the customer first” and stop there. The difference shows up the moment someone has to choose between two defensible options where one protects margin and the other protects growth.
Most interviewers assess this badly, and they do it in three recognisable ways. The first is asking candidates to describe the business model and rewarding recall—a candidate who has read the About page for twenty minutes beats a candidate who has run a P&L, because one memorised the answer and the other assumed you wanted something harder. The second is mistaking financial vocabulary for commercial reasoning. Someone says “CAC payback” and “contribution margin” and the room relaxes, when nobody has checked whether they can apply either term to a decision. The third is never asking what a decision cost. Candidates narrate wins endlessly and are almost never asked what the win consumed—whose budget, whose headcount, what got dropped. Strip out the cost and every story sounds commercially astute.
This page covers 24 interview questions across four capability areas: Commercial Reasoning & Trade-offs, Numerical Literacy in Context, Cost, Risk and Margin Judgement, and Connecting Own Work to Business Outcomes. Every question is designed to be answered with a real example rather than a philosophy, and none of them asks a candidate to self-assess. We’ve drawn on structured interview research and our own patterns across thousands of candidate assessments to isolate the questions that expose real commercial reasoning, not financial vocabulary.
Commercial Reasoning & Trade-offs
What good looks like
A strong candidate can describe a decision where two things the organisation genuinely valued were in tension, and explain which one they chose to protect and why. They don’t default to the option that’s easiest to defend afterwards—they can name what they gave up, who disagreed with them, and what would have happened if they’d chosen the other way. Trade-offs they didn’t personally own are where this shows up most clearly.
Behavioural questions
- Tell me about a time you recommended the cheaper option over the better one.
- What were the two options, and what made the better one better?
- Who disagreed with your recommendation, and what was their case?
- What number or reasoning tipped it towards cheaper?
- How did it play out once the decision was made?
- Walk me through a decision where the right commercial answer and the right customer answer were different.
- What did the customer actually want, and what would it have cost to give it to them?
- What did you recommend instead, and how did you justify it?
- How did you explain the decision to the customer, if you were the one who had to?
- What was the actual commercial impact of going the way you did?
- Describe a situation where you argued against something your own team wanted.
- What did the team want, and why did they want it?
- What was your objection, specifically—what number or risk was it based on?
- How did you raise it with them, and what was the reaction?
- Where did it land—did the team come round, or did you lose that one?
- Tell me about a time you had to defend a spend to someone who controlled the budget.
- What was the spend, and how much was it?
- What was their objection, and how did you prepare for the conversation?
- What number or argument actually moved them?
- Did you get the full amount, a partial version, or nothing?
- Walk me through the last decision you made where you were trading speed against quality.
- What was the work, and what was the actual time pressure?
- What specifically did you sacrifice to hit the timeline, and what did you protect?
- Who else weighed in on that trade-off, if anyone?
- How did the outcome look against the quality you’d have preferred?
- Describe a time you changed your recommendation after seeing a number you hadn’t seen before.
- What was your original recommendation, and what was it based on?
- What was the number, and where did it come from?
- How did it change your reasoning, specifically?
- What did you end up recommending instead, and how did people react to the change?
- Tell me about something the organisation stopped doing because you made the case to stop it.
- What was it, and who was invested in keeping it going?
- What was your case—what number or risk made the argument?
- Who did you have to convince, and how long did it take?
- What happened once it stopped—did anything you predicted actually play out?
Situational scenario
Your team has a long-running feature or service that a small but vocal group of customers loves, but it costs disproportionately more to maintain than the revenue it brings in. A few of your most engaged accounts specifically cite it as a reason they stayed. Your VP wants a recommendation on whether to keep funding it, and you genuinely don’t know which way the numbers point yet.
Walk me through how you’d go about forming your recommendation.
Then introduce a constraint: “You run the numbers and it’s a close call either way—cutting it saves real money but the churn risk from your most engaged accounts is genuinely uncertain. Your VP wants an answer by Friday. What do you recommend, and how do you present the uncertainty?”
What to listen for
whether they name the actual number that would flip their recommendation, whether they present the uncertainty honestly rather than picking a side and hiding the doubt, and whether they distinguish between the vocal customers and what the broader account base would actually do.
Numerical Literacy in Context
What good looks like
A strong candidate reaches for a number unprompted rather than staying at the level of description, and can explain roughly how they’d estimate a figure they don’t have memorised. They know which numbers actually matter for the decisions in front of them, distinguish a trustworthy number from a convenient one, and are candid about the times their own estimate turned out to be wrong and what they learned from the gap.
Behavioural questions
- Walk me through how you’d estimate what your current team costs the business to run for a year.
- What’s your actual starting point—salaries, headcount, something else?
- What are you rounding or guessing, and how confident are you in those guesses?
- What would you want to check to tighten the estimate up?
- How far off do you think your number could plausibly be?
- Tell me about a time you built a business case for something and got it approved.
- What were you asking for, and what did it cost?
- What number in the case actually did the work of convincing people?
- Who pushed back, and on what part of the case specifically?
- Did the thing deliver against what the case promised?
- Describe a situation where a metric everyone trusted turned out to be misleading.
- What was the metric, and why had everyone trusted it?
- What made you look underneath it?
- What was actually going on that the metric was hiding?
- What changed once people knew—did the metric get fixed, replaced, or quietly ignored?
- Walk me through the numbers you checked most often in your last role, and why those ones.
- What were the top two or three, specifically?
- How often did you actually look at them—daily, weekly?
- What decision did each one actually feed into?
- Was there a number you wish you’d been checking that you weren’t?
- Tell me about a time you had to make a call without the data you wanted.
- What data were you missing, and why couldn’t you get it in time?
- What did you use instead to make the call?
- How did you communicate the uncertainty to whoever needed the decision?
- Were you right? How did you find out?
- Describe a forecast or estimate you got badly wrong.
- What was the forecast, and how wrong was it, specifically?
- What did you miss or misjudge in making it?
- Who did you have to tell, and how did that conversation go?
- What do you do differently now when you’re forecasting something similar?
Situational scenario
You’re asked to size the annual cost of a recurring internal process—something that’s never been formally costed because it’s spread across several people’s time, a bit of software spend, and some vendor fees nobody’s added up in one place. Finance wants a number by end of week to decide whether it’s worth automating.
Walk me through how you’d build that estimate in the time you’ve got.
Then introduce a constraint: “Two of the people whose time you need to estimate are on leave until after the deadline. What do you do?”
What to listen for
whether they build the estimate from a defensible method rather than a guess dressed up as a number, whether they flag their assumptions and confidence level rather than presenting a false-precision figure, and whether they find a workaround for the missing inputs rather than just waiting or dropping those costs from the total.
Cost, Risk and Margin Judgement
What good looks like
A strong candidate can price a downside, not just describe an upside. They can name a specific risk they knowingly accepted, what would have happened if it had gone wrong, and why they judged it worth taking. They notice hidden costs that aren’t in the headline number, push back when margin genuinely doesn’t work rather than deferring to enthusiasm, and can recognise when the commercially correct move is to do nothing at all.
Behavioural questions
- Tell me about a time you accepted a known risk deliberately.
- What was the risk, specifically, and what was the downside if it landed badly?
- What made you decide it was worth taking rather than avoiding?
- Did you tell anyone else you were taking it, or was it your call alone?
- Did it pay off, and how do you know it was the risk that made the difference rather than luck?
- Walk me through a decision where the upside was obvious and the cost was hidden.
- What was the upside everyone could see?
- What was the hidden cost, and how did you find it?
- Did you raise it before or after the decision was made?
- What happened to the decision once the hidden cost was visible?
- Describe a time you pushed back on a deal, project or request because the margin didn’t work.
- What was the deal or request, and what number told you the margin was off?
- Who was pushing for it despite the number?
- What did you say, specifically, to make your case?
- Did it go ahead anyway, get renegotiated, or die?
- Tell me about the most expensive mistake you’ve been close to.
- What was it, and how expensive, specifically—in money, time, or relationship?
- What was your role in it—did you cause it, catch it, or clean it up?
- What was the moment you realised how bad it could be?
- What actually happened in the end, and what did it cost?
- Walk me through how you decided what not to fund when the budget was cut.
- How much were you cutting, and what were the options on the table?
- What criteria did you actually use to decide what went?
- What did you cut that you disagreed with, if anything?
- What happened to the things that lost funding—did anyone notice they were gone?
- Describe a situation where doing nothing was the commercially correct choice.
- What was everyone pushing to do, and why did it seem obviously right?
- What made you conclude that doing nothing was actually the better call?
- How did you make that case to people who wanted action?
- What happened, and did it prove you right?
Situational scenario
A major customer asks for a significant custom feature as a condition of renewing a large contract. Building it would take real engineering time away from the core roadmap, and you don’t think other customers would pay for it. The account is genuinely large enough that losing it would hurt the numbers this year. Your sales lead is pushing hard to say yes.
Walk me through how you’d think this through and what you’d recommend.
Then introduce a constraint: “Your sales lead tells you if you don’t agree, they’re going to take it to your VP and argue you’re costing the company a renewal over a feature that ‘barely costs anything.’ What do you do?”
What to listen for
whether they actually cost out the engineering time rather than accepting “barely costs anything” at face value, whether they hold their position under the threat of escalation or fold to avoid the conflict, and whether they propose an alternative that addresses the customer’s need without the full cost of the ask.
Connecting Own Work to Business Outcomes
What good looks like
A strong candidate can draw a straight line from what they personally did to what the organisation gained or lost, without inflating it. They’re honest about work that mattered without making money, can critique how their own success was measured, and can explain in commercial terms—not just activity terms—what would actually break if their role stopped existing tomorrow.
Behavioural questions
- Tell me about a piece of work you’re proud of that made the organisation no money.
- What was it, and why are you proud of it specifically?
- Why didn’t it make money—was that expected, or a surprise?
- How did you justify the time spent on it to anyone who asked?
- What did it actually deliver, if not revenue?
- Walk me through how your last role’s success was measured, and whether you thought it was measured correctly.
- What was the actual metric or target you were held to?
- Where did it capture your real impact well, and where did it miss?
- Did you ever raise that the measure was wrong? What happened?
- What would you have measured instead, if you’d had the choice?
- Describe a time you realised your team’s priorities were out of step with the wider business.
- What was your team focused on, and what had the wider business actually decided mattered?
- How did you find out there was a gap?
- What did you do once you noticed—did you raise it, or work around it?
- What changed as a result, if anything?
- Tell me about a time you had to explain your work’s value to someone who didn’t understand what you do.
- Who was it, and why didn’t they understand the value already?
- How did you explain it—what language or example did you use?
- Did it land? How do you know?
- Did that conversation change anything about how you talk about your work now?
- Walk me through what would break commercially if your last role disappeared tomorrow.
- What’s the first thing that would actually go wrong, specifically?
- Who would notice first, and how quickly?
- Is there a number attached to that impact, even a rough one?
- Is there a part of your role that, honestly, wouldn’t be missed?
Situational scenario
Your team’s dashboard shows you’ve hit every target for the quarter. But you privately think the targets measure the wrong thing—they reward volume of output rather than the outcomes that actually matter to the business, and you suspect leadership hasn’t noticed the gap yet. Flagging it risks looking like you’re making excuses or moving the goalposts after a good quarter.
Walk me through what you do with that quarter’s results.
Then introduce a constraint: “Your manager presents your team’s results to leadership as an unqualified win before you’ve had the chance to raise your concern. What do you do now?”
What to listen for
whether they raise the measurement gap at all or let a good quarter go unquestioned, whether they can articulate the difference between the output metric and the actual business outcome in concrete terms, and whether they handle the timing—after their manager has already claimed the win—without either staying silent or undermining their manager.
Red flags to watch for when assessing Business Acumen
They can quote the company’s ARR but can’t estimate what their own team costs to run. Headline figures are public. Their own cost base is the thing they should have thought about.
Every trade-off they describe has an obviously right answer. Real commercial decisions are uncomfortable. If nothing they chose cost them anything, they’re describing tasks, not judgement.
Financial vocabulary with no application. They use “margin”, “burn” or “unit economics” as adjectives. Ask them to apply the term to a specific decision they made and the sentence collapses.
Revenue is the only number they mention. No cost, no risk, no time horizon. Business acumen that stops at the top line isn’t acumen.
They inflate attribution. A campaign, product or process improvement “drove £2m” with no acknowledgement of what else was happening in the market or who else touched it.
They’ve never spent someone else’s money. No budget conversation, no case made, no rejection survived. Candidates who have only ever executed within a budget someone else fought for often haven’t developed the muscle.
The customer answer is always the right answer, automatically. Genuine commercial reasoning includes the times you didn’t give the customer what they asked for, and why.
How to Use These Questions in a Structured Interview
These questions only work if you probe—the opener produces the story, but the acumen shows up in what follows. Score on a 1/3/5 scale, and write the anchors before you interview anyone. A 1 describes their work in activity terms only—what they did, not what it changed. A 3 connects their work to a business outcome and can name at least one cost or risk they weighed. A 5 reasons about a trade-off they didn’t personally own, uses a number they estimated themselves rather than one they were handed, and can say what they’d decide differently now. Three probes earn their place every time: what did that cost, who paid for it, and what would have happened if they’d done nothing.
Calibrate your interviewers before you run this competency at scale, not after—business acumen attracts more scoring variance than almost any other competency, because interviewers unconsciously reward people who sound like them. Run two or three recorded answers past the panel and compare scores before anyone meets a candidate; where scores diverge by two points or more, the problem is your anchors, not your candidates. See how Interview Intelligence solves this → by showing exactly where your panel’s definitions of the competency actually diverge.
Frequently asked questions
What is business acumen in an interview context?
Business acumen is the ability to reason about commercial trade-offs - how revenue, cost, risk and margin interact - and to connect one's own work to those outcomes. In an interview, you're assessing whether a candidate can explain the commercial consequence of a decision they made, including what it cost. It is not general intelligence, and it is not familiarity with your business model, both of which are frequently mistaken for it.
How do you assess business acumen in candidates from non-commercial functions like engineering, design or support?
Ask about the resources they consumed rather than the revenue they generated. An engineer with commercial judgement can explain why a piece of technical debt was worth carrying, or what the infrastructure they own costs to run. A designer can explain which piece of research they skipped and why. A support lead can explain the cost of a policy they enforce. Several of the questions in this bank work particularly well here because none of them requires a revenue line.
Should I ask candidates to explain our business model?
Only as context, never as a score. Asking someone to describe your business model rewards preparation and penalises candidates who assumed you wanted something more demanding. If you want to test commercial reasoning against your own business, give them a genuine trade-off you face and ask what they'd want to know before deciding. What they ask for tells you far more than what they conclude.
How many business acumen questions should I use in one interview?
Three or four, with real follow-up depth on each. Business acumen answers need probing - the opener produces the story and the probes produce the evidence. Twelve rushed questions will tell you less than three questions you pushed properly. If the competency is central to the role, split it across two interviewers with different capability areas rather than compressing it all into one stage.
Can business acumen be developed, or should I only hire for it?
It develops, but only through exposure to real trade-offs and real budgets. Someone who has never had to choose what not to fund won't build the muscle from a course alone. When hiring, look for evidence that a candidate seeks out the commercial context of their work even when nobody requires it of them - that instinct is the reliable predictor. The technical vocabulary is easy to teach afterwards.