Questions to Ask a Controller in an Interview
Interview questions for hiring a financial controller, written for the CFO or owner doing the hiring. They cover the monthly close, internal controls, ERP experience, audit history and how the candidate runs an accounting team.
The questions
Open any question for the note
Walk me through the close you run today: how many days does it take, and who owns each piece?
Why ask it
The day count is checkable on a reference call, and the ownership half matters more. A candidate who says "I close the books" without naming staff accountants and their handoffs has usually never delegated any of it.
What condition were the books in when you started your last job, and what did you fix first?
Why ask it
Separates people who have done cleanup from people who inherited a tidy ledger and kept it tidy. "Everything was in good shape" is worth probing, because it often means nobody looked at the reconciliations.
Which ERP and reporting tools have you worked in day to day, and which one would you choose again?
Why ask it
Listing systems is easy; choosing one and defending it is not. Someone who names six platforms with no preference among them probably pulled reports out of them rather than administering them.
Tell me about a reconciliation that would not tie. How did you track down the problem?
Why ask it
You are listening for method: subledger to general ledger, timing versus valuation, cutting the population down to find the break. Candidates who jump straight to "I asked the auditors" often cannot work a variance alone.
How do you decide what goes into the monthly reporting package, and what you leave out?
Why ask it
Controllers who cannot answer this send forty pages nobody reads. A good answer names the audience and the two or three exhibits that actually get discussed in the meeting.
Which controls did you design yourself, rather than inherit?
Why ask it
Signing off on an existing control matrix is very different from noticing an exposure and building the check. Ask what prompted it, since that specific detail is hard to invent on the spot.
Have you ever found a material error after the numbers were already reported? What happened next?
Why ask it
Most experienced controllers have. A flat denial suggests either a short career or an unwillingness to own mistakes, and the escalation story shows how they handle bad news travelling upward.
How involved are you in the forecast, and where do your numbers usually disagree with the sales team's?
Why ask it
Shows whether finance keeps score or participates. The disagreement itself is the useful part: a controller who has never pushed back on a revenue forecast has not been in the room where it gets set.
How far out does your cash forecast go, and how far out do you actually trust it?
Why ask it
The gap between those two numbers is the honest answer. Anyone claiming a reliable twelve month cash view either has unusual visibility or has never compared the forecast against what happened.
Which part of your current close is still manual, and why has it stayed that way?
Why ask it
Every close has one. The reason is the tell: a genuine resource constraint is fine, while "nobody has looked at it" after three years says something about their appetite for unglamorous work.
Describe your last external audit. What did the auditors push back on?
Why ask it
Specific pushback on revenue cutoff, an accrual estimate or an inventory count means they were in the room. Answers along the lines of "it went smoothly" usually mean somebody else managed the audit.
What do you do when a senior leader wants a number presented differently than you think is right?
Why ask it
This is the real pressure point of the job. Look for escalation and documentation rather than instant agreement or a heroic refusal that nobody actually survives in practice.
What have you done to shorten a close, and what did it cost in effort or accuracy?
Why ask it
Naming the tradeoff is the point. Cutting close days usually means materiality thresholds, standard accruals or automation work, and a candidate who claims no cost has not measured one.
How do you split tax work between your own team and an outside firm?
Why ask it
Tells you what they can do in house and where they will ask for budget. It also shows whether they treat the provision as their responsibility or as something the firm handles for them.
How many people have you managed directly, and what did you do the last time someone was not keeping up?
Why ask it
The headcount sets the scale; the second half tests whether they manage or avoid. Vague answers about coaching with no timeline usually mean the problem was left for the next person.
What is the biggest accounting judgment call you have personally owned?
Why ask it
Revenue timing, capitalisation, a reserve estimate: the answer shows how much technical weight they have carried themselves as opposed to reviewed after somebody else prepared it.
In your first two weeks here, what would you want to look at first?
Why ask it
A candidate who has been paying attention names artefacts, not areas: the trial balance, the close calendar, the last management letter. Vague answers about meeting the team mean they have not thought about your business yet.
Tell me about a time you disagreed with a CFO or an auditor. How did it end?
Why ask it
The resolution matters more than the topic. A controller who has never disagreed with either is either quite junior or not looking closely at the numbers they sign off on.
Which part of this job do you find least interesting, and how do you make sure it still gets done?
Why ask it
Everyone has one, often compliance filings or the fixed asset register. Naming it and describing a system for it is more credible than claiming to enjoy every part of the role.
What do you want from this role that your last one did not give you?
Why ask it
Tells you whether the job as scoped can deliver what they are after. A mismatch here, such as wanting FP&A or systems ownership you cannot offer, tends to predict a short tenure.
Running a Controller Interview
Practical guidance for the conversation itself
Decide which controller you actually need
The title covers two different jobs. A technical controller keeps the books clean, owns the audit and gets the provision right. A process controller shortens the close, replaces spreadsheets and builds a team that can run without them. Write down which one your business needs over the next eighteen months before you interview anybody, because the strongest candidate for one is often only adequate at the other.
Before the conversation
- Have your close calendar, chart of accounts and last audit management letter to hand, so you can ask about your own mess rather than a hypothetical one.
- Put someone in the room who can evaluate technical accounting, whether that is your CFO, your audit partner or a fractional controller, if you cannot judge it yourself.
- Decide in advance what is a hard requirement: a specific ERP, public company reporting, multi entity consolidation, inventory. Searches drift when nobody writes this down.
- Ask the recruiter for the candidate's stated reason for leaving beforehand, so you can compare it with what you hear in the interview.
Reading the answers
- Good sign: they quantify without being asked, giving close days, entity count, team size and revenue scale.
- Good sign: they describe a control by the exposure that prompted it rather than by its name.
- Good sign: they are precise about what they delegated and to whom.
- Watch for system names with no depth behind them. Ask which module they configured and who called them when it broke.
- Watch for every problem being attributed to a predecessor, with no account of anything they got wrong themselves.
- Watch for an inability to name a single disagreement with a CFO or an auditor.
Test the work, not just the conversation
- 1Give a short, real exercise: a trial balance with two seeded errors, or a set of reconciliations to review. Cap it at an hour and pay for longer.
- 2Ask them to walk you through the close calendar from their last job rather than describe a close in the abstract.
- 3Reference check the close specifically. Ask a former CFO how many days it took before and after this person, and what broke while they were there.
- 4Verify licensing and any public reporting claims directly rather than taking them from the resume.
Common mistakes
- Hiring for audit pedigree when the need is operational. Large firm training does not mean somebody can run a close with three people and no systems team.
- Skipping the team conversation. A controller who cannot keep staff accountants will hand you the same vacancy again in a year.
- Letting the candidate meet only finance. The controller works with payroll, sales operations and IT every single month.
- Accepting "we had good processes" as an answer. Ask who wrote them and what they replaced.