Finance Expertise Is the Easy Part
A CFO can spend an hour with a finance leader candidate and walk away confident the person understands the numbers. That confidence is usually earned. Technical fluency shows up fast in an interview. The candidate knows forecasting, reporting, controls, and systems. The examples sound credible. The terminology is familiar.
That part is not the hard part.
The harder part is figuring out whether this person can operate beyond the numbers. Can they influence leaders who don't report to them? Challenge an assumption without becoming the person who always says no? Turn analysis into a decision the business actually makes? Develop the people around them? Those capabilities are what separate a strong technical operator from a strategic finance leader, and they are much harder to see in an hour than a discounted cash flow model.
The cost of missing this distinction rarely shows up right away. The hire produces accurate work, hits every technical mark, and still doesn't create the leverage the CFO expected. Six months in, the CFO is still translating the analysis for the rest of the leadership team, still managing the cross-functional friction, still carrying the exact strategic load this hire was supposed to take off their plate. Finance keeps reporting instead of influencing. The company has more technical capacity and no more strategic leverage than it had before.
Shared Fluency Creates False Confidence
When two finance professionals talk to each other, the conversation moves fast. Both people know the vocabulary. The candidate can walk through a variance analysis or a budgeting cycle without missing a beat, and it feels like real signal.
But knowing the work, leading the work, and shaping business decisions through the work are three different skills. An interview built entirely around the first one will miss the other two.
This is also where the word "strategic" can lose its meaning. For one company it means building FP&A from the ground up. For another it means better board reporting, or supporting an acquisition, or getting Sales and Finance to actually talk to each other. A candidate can be exactly the right kind of strategic for one environment and a mismatch for the next.
The interview should not start with the candidate. It should start with a Talent Alignment question: what must this role accomplish, what capability already exists on the team, and what is genuinely missing? Skip that step and even a strong candidate can look like the right answer to the wrong question.
Listen for Evidence, Not Language
Once the role is defined, the interview itself needs to shift from "tell me about a time" to "what actually happened."
Most interviewers ask some version of “Tell me about a time you influenced a decision without authority.” Polished candidates are good at answering that question. What the CFO actually needs to know is what the candidate personally did, who disagreed, what resistance they hit, and what changed because of their actions. The story is easy. The candidate's actual role inside the story is where the real answer lives.
Strong finance candidates often know the right language: business partnership, value creation, driving transformation. The vocabulary is easy to learn and easy to rehearse, which means the interview has to get beneath the language. Ask for the tradeoff they recommended, the outcome they influenced, and what they personally owned rather than what the broader team delivered.
A few areas worth pressing on, and what good evidence sounds like:
Influence. Not whether they can describe influencing someone, but whether they can point to a specific decision that moved because of them. Listen for how they handled disagreement, whether they adjusted how they communicated based on who they were talking to, and what changed afterward.
Judgment. Strong candidates can tell you what they decided. Better candidates can tell you what they chose not to analyze, and why. Listen for how they weighed tradeoffs with incomplete information and how they told a reversible decision apart from a real risk.
Commercial understanding. Can they explain how the company actually makes money without retreating into financial language? Do they talk about customers, pricing, and margin like someone who understands the business, or like someone reporting on it from a distance?
Leadership. Did they help others improve, or just perform well themselves? Listen for what they delegated, how they handled a technically strong performer who lacked leadership range, and whether they left the team stronger than before.
Courage. Can they challenge the business without being seen as someone who blocks progress? Listen for how they preserved the relationship after disagreeing, whether they offered an alternative instead of just an objection, and whether people kept coming back to them afterward.
None of this shows up in a résumé. It shows up in the specifics underneath the story.
Avoid Hiring Your Own Reflection
CFOs naturally gravitate toward candidates who think and communicate the way they do. It's comfortable. It's also not the same thing as complementary.
The useful question isn't "Would I approach this the same way?" It's "Does this person bring a capability, perspective, or leadership range the finance organization needs but doesn't currently have?" A team full of people who solve problems identically has a blind spot, not a strength. Building a stronger finance function around the CFO is a different goal than finding a smaller version of the CFO, and it's easy to confuse the two when the conversation feels effortless.
Technical fundamentals still matter. They're just no longer enough on their own. The harder work is deciding which capabilities can be developed and which the role requires on day one.
Define the Proof Before the Interview
The interviews that hold up are the ones where the panel agreed, in advance, on what strong evidence would actually look like. Not a list of questions. A list of proof points:
Strategic influence: a cross-functional decision that changed because of them
Leadership: someone they developed into a bigger role
Commercial judgment: an operating issue they caught before it hit the financials
Communication: a complex issue they made clear to a non-finance leader
Capability building: a process, function, or team that didn't exist before they built it
Agree on what counts as evidence before the first candidate walks in, and the interview stops being a chemistry test. It becomes less about instinct and more about a repeatable process. Technical familiarity and a comfortable conversation stop carrying more weight than they should.
Interview for Evidence, Not Familiarity
The strongest finance leaders do more than understand the numbers. They operate as growth architects, helping the organization decide what the numbers mean, what to do next, and which risks are worth taking. That's harder to assess than technical expertise, and it's the part of the interview most likely to get shortchanged in favor of the part that's easy to confirm.
Before deciding whether a candidate is impressive, get clear on what the finance organization needs them to achieve. Then interview for evidence, not familiarity.
