Questions to Ask Controller During Interview
Questions for a candidate interviewing for a controller role, to be asked of the chief financial officer, the chief executive, or whoever the position reports to. They cover the state of the books, close timing, audit history, systems, team gaps, and what the first year is expected to fix.
The questions
Open any question for the note
Why is this role open, and what happened with the person who held it before?
Why ask it
Growth, a promotion, a departure, and a dismissal each imply different first months. A vague answer about seeking a different skill set often means a conflict with leadership, so follow up by asking how long the role has been vacant and who has been covering it.
Who does this role report to, and does that person want a scorekeeper or a business partner?
Why ask it
Controllers who report to a chief financial officer usually have a defined technical lane; controllers reporting directly to a founder or chief executive often absorb planning, systems, and human resources as well. Ask which they intend, because the mismatch is a common reason these hires fail.
What do you need fixed in the first ninety days, and what by the end of the year?
Why ask it
The answer separates the accounting problem from the person problem. A clear ninety-day list, close timing, a cleanup, an audit, is workable. A wish list spanning systems, staffing, and reporting in the same quarter tells you the expectations have not been sized by anyone who has done the job.
How long does the monthly close take now, and where does it get stuck?
Why ask it
The number of days is easy to ask for and hard to dress up. The bottleneck is the real answer: accruals, intercompany, inventory, revenue recognition, or waiting on someone outside finance. If nobody can name the bottleneck, the close is not being managed to a calendar.
Which reconciliations or subledgers are currently behind?
Why ask it
Ask specifically about bank, inventory, accrued liabilities, prepaid accounts, and fixed assets. This is the question that surfaces cleanup work before you accept it, and an interviewer who answers it honestly is someone you can probably work with.
How often do reported numbers get revised after they have gone out?
Why ask it
Frequent restatements of internal reporting mean the process is producing estimates that leadership treats as facts. Ask what the largest recent revision was and what caused it, since that tells you where the controls are thinnest.
What did the last audit or review produce: adjustments, a management letter, any control deficiency?
Why ask it
Audit outputs are the most objective evidence available to you about the state of the books. Ask whether the adjustments were recurring, and ask who prepares the schedules, since a company where the auditors effectively do the closing has a structural problem, not a busy season.
Has the company ever restated results, missed a debt covenant, or reported a material weakness?
Why ask it
These are facts, not opinions, and asking plainly signals that you will ask plainly once you are inside. How the interviewer handles the question matters as much as the answer, because you are going to be the person who has to raise the next one.
What systems are in use, and how many spreadsheets sit between the accounting system and the numbers leadership sees?
Why ask it
The spreadsheet count is a good proxy for both risk and your workload. Ask who maintains those files and what happens when that person is on leave, since undocumented models built by one person are the most common single point of failure in finance.
Is a system implementation planned in my first year, and who owns it?
Why ask it
An implementation is a second full-time job, and controllers routinely inherit one that was scoped before they arrived. Ask for the timeline, the budget, whether an integrator is engaged, and whether you can change the plan if it is unrealistic.
How large is the team, at what levels, and how many positions are open?
Why ask it
A team of three senior accountants and a team of eight juniors need different management. Open positions tell you whether you will spend your first quarter hiring, and long-standing vacancies usually mean the pay band is below market.
Which tasks depend on one person with no backup?
Why ask it
Every small finance team has a few, often payroll or the revenue calculation. Knowing them before you start lets you plan cross-training rather than discovering the gap during someone's holiday, and it is a reasonable question that also demonstrates how you think about risk.
How is the cash forecast produced, and who owns collections?
Why ask it
Cash forecasting frequently lands on the controller without being written down anywhere. Ask about the horizon, how accurate it has been recently, and whether collections sit in finance or in sales, since that determines how much of your week is spent chasing customers.
Are there open tax or regulatory matters, such as sales tax exposure, unfiled entities, or payroll registrations?
Why ask it
Companies that grew quickly across states or countries often have registrations nobody completed. These become your problem on day one, and it is far better to negotiate the cleanup as part of your mandate than to discover it during an audit.
How would my time divide between technical accounting, planning and analysis, and systems work?
Why ask it
Controller titles cover a wide range, from a senior bookkeeper to a de facto finance chief. Asking for the split in percentages forces the interviewer to be concrete, and the answer tells you what your resume will look like in three years.
What does the board or the lender receive, and on what deadline?
Why ask it
Reporting obligations set the rhythm of your year, and covenant reporting in particular is unforgiving. Ask to see the reporting package if they can share it, since its quality tells you more about the finance function than any description will.
Who owns the finance budget, including audit fees, software, and headcount?
Why ask it
A mandate to improve the function without budget authority is a common trap. Ask what was spent last year and what is approved for next, and whether you can commission outside help for a cleanup or an implementation.
What happened the last time finance told the business it could not do something?
Why ask it
You are asking whether accounting judgment is respected when it is inconvenient. A specific example, including a decision that went against finance and was accepted, is reassuring. Being told that it never comes up is not credible in any operating company.
Is a transaction, fundraise, or sale likely in the next two years, and how would that change this job?
Why ask it
Diligence, quality of earnings work, and audit readiness turn a controller role into something much heavier. If a process is coming, that is worth knowing for both your workload and your compensation discussion, and it may explain why the role is open now.
Besides you, who else would I need to win over, and can I meet them?
Why ask it
Controllers depend on operations, sales, and the systems owner more than they expect. Asking to meet one of them tests whether the company will give you access, and the meeting itself usually reveals how finance is regarded internally.
A year from now, what would make you say this hire had not worked?
Why ask it
Asked toward the end, this often produces the most direct answer of the interview, because it invites a concern rather than a criticism. Whatever they name, close timing, credibility with the board, managing the team, is what you will actually be measured on.
What is the compensation range and bonus structure for this role?
Why ask it
Ask before final rounds so nobody wastes weeks. Also ask how bonuses have actually paid out for the last two years and against what targets, since a formula tied to company results you cannot influence is a different offer from the headline figure.
Interviewing for a controller role
Practical guidance for the conversation itself
How to evaluate the finance function
Ask for artifacts, not descriptions
The close calendar, the reporting package, the organization chart, and the chart of accounts tell you in five minutes what an hour of conversation will not. Some companies will decline to share them before an offer, which is fair, but the response to the request is itself informative.
Establish the size of the cleanup before you accept
Stale reconciliations, unfiled registrations, an audit in progress, and an implementation half done are all survivable, and all much easier to manage if they are written into your mandate and your first-year goals rather than discovered in week three.
Work out who you really report to
The line on the chart and the person whose opinion determines your success are not always the same. Ask who reviews your work, who presents finance to the board, and who decides your goals, then note whether those are three different answers.
Ask the same question of two interviewers
Try the ninety-day priorities question with both the hiring manager and a peer. Consistent answers suggest a company that has thought about the role. Different answers tell you which competing expectations you would be arriving into.
Signals worth taking seriously
- Nobody can say how many days the close takes, or the number has grown each year with no explanation.
- The auditors prepare significant schedules that the company should be producing itself.
- A third or fourth controller in five years, particularly under the same executive.
- A key report exists only in a spreadsheet maintained by one person who is described as indispensable.
- Recurring audit adjustments in the same accounts, which points at a process rather than an error.
- Interviewers who cannot name a time finance said no and was supported.
- An implementation already scoped and dated, with no controller involved in the plan.
What goes wrong
Taking a title that describes a different job
Some controller roles are senior bookkeeping with no team; others are a finance chief without the title or the pay. Ask about team size, budget authority, and the split of your time, then judge the title against those answers rather than the other way round.
Only asking technical questions
Systems, standards, and close mechanics are the comfortable ground, and they are not where controllers usually fail. The harder questions are about authority, whether accounting judgment holds when it is inconvenient, and who backs you when you have to deliver bad news.
Not asking about the previous controller
It feels intrusive and it is the single most predictive question available. Repeated short tenures in the seat point at the structure and the reporting line, not at the people who left.
Accepting a mandate without the resources
Being asked to shorten the close, pass an audit, and implement a system with the current team and no budget is a plan to be blamed. Negotiate scope, budget, or timeline before you accept, since none of the three gets easier to renegotiate afterward.
Leaving the compensation conversation until the end
Controller bands vary widely with company size, entity count, and whether an audit is required. Raise the range early and ask how bonuses actually paid out, rather than assuming the structure described is what people received.