Financial controller interview questions for employers: 6 kits by scope, from first finance hire to group controller, plus a work sample and scorecard.
Six interview kits chosen by scope rather than by competency: standard, group, technical, first finance hire, fractional, and a paid work sample with a scorecard. Every question carries why to ask it and what a strong answer sounds like. Download as DOCX.
The first time I sat in on a financial controller interview, the hiring owner asked eight questions and every one of them could have been asked of a bookkeeper. The candidate answered them all well, took the job, and was gone inside a year, because the role he had actually been hired into involved three legal entities and a lender who read the statements every quarter. Nothing in the interview had touched either.
That is the trap with this title. Financial controller covers at least five different jobs, and the questions that reveal a great candidate for one of them reveal almost nothing about another. So this page is organized by scope rather than by competency: pick the version of the role you are filling, then use the kit built for it.
At FirstHR, we build for employers who run this hire themselves, without a finance department or an HR department to lean on. Every question below states why it is worth asking and what a strong answer sounds like. For the posting itself, pair this with the financial controller job description.
TL;DR
Financial controller covers five different jobs, so scope the role before you write the questions. Pick one kit (standard, group, technical, first finance hire, or fractional), ask every candidate the same kit, and finish with a paid work sample: a sanitized trial balance with two or three planted issues. Score noticing, prioritization, explanation, escalation, prevention, and scope fit from 1 to 5. Download all six kits as DOCX.
Scope the Role Before You Write the Questions
Decide four things before you ask anything: how many legal entities are in scope, whether an outside auditor or lender reads your statements, whether there is an existing accounting team to run, and whether this person reports to you or to a CFO. Those four answers select the kit, and getting them wrong is the most expensive mistake at this level.
The reason it matters is that a strong candidate scoped against the wrong version of the role still interviews well. A group controller answers first-hire questions confidently and then stalls when there is no team to direct. A builder answers consolidation questions thinly and is exactly the person a company with one entity and no process needs. Neither failure shows up in the room.
If this is true of your business
Interview with
One entity, a bookkeeper already in place
Kit 1: standard controller
Two or more legal entities, or several locations
Kit 2: senior and group controller
An outside auditor, lender, or acquirer reads the numbers
Kit 3: accounting controller, technical depth
No finance function yet, owner has carried the books
Kit 4: first finance hire
A few days a month, employee or contractor
Kit 5: fractional and part-time
Any of the above, final round
Kit 6: work sample and debrief scorecard
Write the decision into the job posting as well as the interview. Candidates self-select on scope more reliably than on title, and a posting that says three entities and a quarterly lender review will filter your pipeline before you spend an hour on the wrong conversation. Browse the rest of the hiring templates if you still need the posting.
Pick One Kit, Not a Mix
The temptation is to take the interesting questions from all five kits. Resist it. A mixed set produces candidates who each answered a different interview, which is precisely what you were trying to avoid. Pick the kit that matches your scope, ask it of everyone, and add at most two questions of your own. If two versions of the role genuinely apply, run the more senior kit and note where the candidate was scoped down.
6 Interview Kits by Controller Type
Download all six as a single Word document, or copy the one you need. Each kit states when to use it, then lists the questions with a why-ask note and strong and weak answer notes underneath, plus space for evidence. The sixth is the work sample and its scorecard.
Standard controller
One entity, existing books
You already have a bookkeeper or staff accountant and need the person who owns the close, the statements, and the controls. Kit 1.
Senior or group controller
Several entities or sites
Consolidation, intercompany, mapped charts of accounts, and controllers you do not sit with. Kit 2.
Accounting controller
Technical and audit-facing
Weighted toward technical positions, memos, and audit or lender review rather than planning. Kit 3.
First finance hire
No finance function yet
The owner has carried the books. This person builds the function without over-building it. Kit 4.
Fractional or part-time
Days per month
Scope, availability, coverage, and what stays with you when the engagement ends. Kit 5.
Work sample and scorecard
Use with any kit
A sanitized trial balance with planted issues, a live debrief, and a 1-to-5 rubric scored against evidence. Kit 6.
Download All 6 Financial Controller Interview Kits
Standard, senior and group, accounting controller, first finance hire, fractional, plus a work sample and debrief scorecard. All in one DOCX.
Kit 1: Standard Financial Controller Questions
Nine questions for a single-entity role with books already in place: the close calendar day by day, reconciliation priorities, where their work stops and a CPA's begins, and what would worry them about your business.
Standard Financial Controller Interview Questions
STANDARD FINANCIAL CONTROLLER INTERVIEW QUESTIONS
Use when you already have an accounting function and are hiring the person
who will own it. Single entity, existing bookkeeper or staff accountant.
Candidate: __
Entity / entities in scope: __
Interviewer: __
Date: __
HOW TO RUN THIS SET
Ask all nine. Each question below states why it is worth asking and what a
strong answer sounds like, so you can judge the response without being an
accountant yourself. Take notes in the candidate's own words, then score on the
work sample and debrief scorecard in Kit 6.
QUESTIONS
1. What is your current close calendar, day by day, from day one to sign-off?
Why ask: the close calendar is the one artifact that shows whether the
candidate runs a process or reacts to one.
Strong answer: names actual days, owners, and dependencies, and separates
hard cut-offs (payroll, bank feeds) from tasks that can float.
Weak answer: "about a week" with no sequence and no owners.
2. Which three accounts do you reconcile first, and why those three?
Why ask: it reveals whether they think in terms of risk or in terms of habit.
Strong answer: picks cash, accrued liabilities, and whichever account carries
the most judgment in your business, and explains the exposure in each.
Weak answer: recites the full balance sheet in order with no prioritization.
3. What did your last set of financial statements not tell the owner, and how
did you cover that gap?
Why ask: a controller who knows the limits of their own reporting is far more
useful than one who defends it.
Strong answer: names a real blind spot (unbilled work, deferred revenue,
customer concentration) and the supplementary schedule they built for it.
Weak answer: insists the statements said everything.
4. Walk me through a month where the numbers moved and you had to explain why.
Why ask: variance explanation is the daily work of the role.
Strong answer: traces the movement to a specific driver, not to an account,
and describes the conversation with the person who caused it.
Weak answer: describes the variance report without describing the cause.
5. Where does your work stop and an outside CPA's work begin?
Why ask: scope confusion here creates surprise fees and missed filings.
Strong answer: draws a clear line (tax return preparation, attest work,
complex technical opinions) and describes how they hand off cleanly.
Weak answer: claims to do everything, or cannot describe the handoff.
6. What is the first control you would put in over outgoing payments here?
Why ask: it tests whether they can right-size controls to a small team.
Strong answer: proposes something proportionate (dual approval above a
threshold, owner-visible bank access) and explains what it prevents.
Weak answer: proposes an enterprise control framework with no sequencing.
7. Tell me about a number you signed off on that turned out to be wrong.
Why ask: everyone has one; the answer separates ownership from deflection.
Strong answer: states the error, the impact, who they told and how fast, and
the specific process change that followed.
Weak answer: cannot recall one, or blames a predecessor entirely.
8. What would you want in your first 30 days here, and from whom?
Why ask: it shows whether they have thought about your business or their own
comfort.
Strong answer: asks for bank access, the last three closes, the chart of
accounts, and time with whoever does the billing.
Weak answer: a generic onboarding wish list with no finance specifics.
9. What in our business would worry you as the person signing the numbers?
Why ask: an experienced controller will already have a hypothesis.
Strong answer: raises something concrete from what they know of you, such as
inventory counts, contractor classification, or revenue cut-off.
Weak answer: says nothing worries them.
NOTES
__
__
Kit 2: Senior and Group Financial Controller Questions
For multi-entity scope: intercompany matching, chart of accounts mapping, currency translation, closing a group with a late location, and managing accountants you do not sit with.
Senior and Group Financial Controller Questions
SENIOR / GROUP FINANCIAL CONTROLLER INTERVIEW QUESTIONS
Use when the role covers more than one legal entity, more than one location, or
a set of brands that have to be reported together.
Candidate: __
Entities / locations in scope: __
Interviewer: __
Date: __
WHAT THIS SET TESTS
Consolidation is the skill that separates a group controller from a very good
single-entity controller, and it is the one most interviews never reach. These
questions test whether the candidate has actually closed a group, not just read
about it.
QUESTIONS
1. How many entities did you consolidate, and what was the elimination that
caused you the most trouble?
Why ask: naming a painful elimination is proof of hands-on work.
Strong answer: describes intercompany balances that did not agree, and the
reconciliation routine they built so they agreed by default.
Weak answer: describes consolidation as a button in the software.
2. How did you keep intercompany balances in agreement between closes?
Why ask: groups fail here first, and it is invisible until year end.
Strong answer: a monthly intercompany matching step with a named owner on
both sides and a tolerance the group agreed in advance.
Weak answer: reconciles intercompany once a year for the accountants.
3. Do the entities share a chart of accounts? If not, how did you map them?
Why ask: mapping quality determines whether group reporting is trustworthy.
Strong answer: describes a mapping table, who maintained it, and how new
accounts were approved before use.
Weak answer: a spreadsheet nobody owned.
4. If any entity reports in another currency, how did you handle translation?
Why ask: currency handling is a fast, honest test of technical depth.
Strong answer: distinguishes the rates used for balance sheet and income
statement items and knows where the difference lands.
Weak answer: cannot separate translation from transaction effects.
5. How did you close a group where one location was always late?
Why ask: group control is largely people management at a distance.
Strong answer: describes escalation, a hard cut-off, and what they changed so
the location could hit it, not just pressure.
Weak answer: extended the deadline for everyone.
6. What did your group reporting pack contain, and who read it?
Why ask: the pack shows what the candidate thinks leadership needs.
Strong answer: a short consolidated set plus entity-level detail and a
commentary page, tailored to the reader.
Weak answer: a large export nobody could act on.
7. How did you manage controllers or accountants you did not sit with?
Why ask: the role is usually distributed.
Strong answer: a fixed cadence, shared calendar, and clear standards written
down rather than carried in one person's head.
Weak answer: "I checked in when there was a problem."
8. What happened at the last acquisition or new entity you brought into the
group?
Why ask: growth by entity is why groups hire this level.
Strong answer: describes opening balances, the mapping, and the first clean
close, with a realistic timeline.
Weak answer: has never opened a new entity in the ledger.
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
For audit-facing and lender-facing roles: revenue arrangements, technical memos, disagreeing with an auditor, estimation-heavy accounts, and preparing for an audit before it starts rather than during it.
Accounting Controller Technical Depth Questions
ACCOUNTING CONTROLLER: TECHNICAL DEPTH QUESTIONS
Use when the role is weighted toward technical accounting and audit support
rather than planning, and when an outside auditor or lender reviews your numbers.
Candidate: __
Auditor / reviewer, if any: __
Interviewer: __
Date: __
HOW TO USE THIS SET WITHOUT AN ACCOUNTING BACKGROUND
You are not grading the technical answer for correctness. You are listening for
whether the candidate can explain a judgment call in plain language, name the
guidance behind it, and say who reviewed it. Anyone who cannot explain their own
memo to you will not be able to explain it to your lender either.
QUESTIONS
1. Describe a revenue arrangement you had to think hard about.
Why ask: revenue timing is where most small-company restatements start.
Strong answer: identifies the promise to the customer, when control passed,
and why they landed where they did.
Weak answer: describes invoicing, not recognition.
2. Have you written a technical accounting memo? What was in it?
Why ask: written reasoning is what an auditor actually asks for.
Strong answer: describes the question, the guidance considered, the
conclusion, and who reviewed it.
Weak answer: has never documented a position.
3. What did you do the last time your auditor disagreed with you?
Why ask: the response reveals both technical confidence and temperament.
Strong answer: describes the evidence they brought, and the point at which
they accepted the auditor's view.
Weak answer: either never disagreed, or never conceded.
4. Which accounts carry the most estimation in a business like ours?
Why ask: it tests whether they can transfer knowledge to your context.
Strong answer: names allowances, accruals, inventory reserves, or warranty,
and explains what drives each estimate.
Weak answer: a generic list with no link to your business.
5. Walk me through the schedule you build for leases or long-term commitments.
Why ask: it is a common small-company gap that surfaces during diligence.
Strong answer: describes the schedule, its inputs, and how it ties to the
ledger each period.
Weak answer: keeps commitments only in the contract folder.
6. How do you prepare a request list before an audit rather than during one?
Why ask: audit cost is driven by preparation, not by the auditor.
Strong answer: keeps a rolling support file through the year, so the request
list is mostly already answered.
Weak answer: starts gathering support when the auditor arrives.
7. What is your process when you find an error in a period already reported?
Why ask: it tests judgment and honesty in one question.
Strong answer: sizes the error, decides on correction versus restatement with
a reviewer, and tells the owner early.
Weak answer: absorbs it quietly in the current period.
8. How do you stay current technically?
Why ask: technical work goes stale fast.
Strong answer: names concrete sources, updates, or CPE, and a recent change
they had to apply.
Weak answer: relies entirely on the outside accountant.
NOTES
__
Kit 4: First Finance Hire Questions
For businesses with no finance function: what they do in week one with no close calendar, what they would deliberately not do in six months, how they change an incumbent bookkeeper's process, and what they have built that outlasted them.
First Finance Hire Financial Controller Questions
FIRST FINANCE HIRE: FINANCIAL CONTROLLER QUESTIONS
Use when the business has no finance function yet, the owner has carried the
books with a bookkeeper or an outside accountant, and this hire builds it.
Candidate: __
Business: __
Interviewer (usually the owner): __
Date: __
WHY THIS SET IS DIFFERENT
At a company with no finance department, the controller has no team to inherit,
no documented process to follow, and no peer to check their work. The hire is as
much about temperament and sequencing as about technical skill. These questions
test whether the candidate can build from nothing without over-building.
QUESTIONS
1. You arrive and there is no close calendar. What do you do in week one?
Why ask: it separates builders from maintainers.
Strong answer: gets bank access, reconciles cash, looks at the last three
months, then writes the smallest calendar that can be met.
Weak answer: proposes a systems project before understanding the books.
2. What would you deliberately not do in your first six months here?
Why ask: over-building is the most common failure of this hire.
Strong answer: defers an accounting system migration, a full policy manual,
or a headcount plan until the basics are reliable.
Weak answer: wants to do everything at once.
3. How do you work with an owner who reads the numbers once a month?
Why ask: the owner is the entire audience for this role.
Strong answer: proposes a short recurring review, plain-language commentary,
and one or two decisions per month that the numbers should inform.
Weak answer: sends a report and waits.
4. Our bookkeeper has done this a certain way for years. How do you change it?
Why ask: the first controller almost always inherits one incumbent.
Strong answer: learns the current process before changing it, changes one
thing at a time, and keeps the bookkeeper's knowledge in the business.
Weak answer: replaces the person or the process on day one.
5. What would you tell me if you found something in the books you did not like?
Why ask: the owner is the only escalation path, so the answer matters.
Strong answer: says they would raise it directly and early, with the size and
the options, not a finished verdict.
Weak answer: would investigate quietly first.
6. How much of this job can you do yourself before we need to add a person?
Why ask: it forces an honest capacity answer before the offer, not after.
Strong answer: gives a volume-based answer (transactions, entities,
headcount) and names the first role they would add.
Weak answer: promises to absorb unlimited volume.
7. What have you built from scratch that outlasted you?
Why ask: durability is the point of the hire.
Strong answer: names a process, schedule, or system still in use after they
left, and explains why it survived.
Weak answer: describes only what they personally ran.
8. If we never grow past our current size, is this role still interesting?
Why ask: an honest no now is far cheaper than a resignation in eight months.
Strong answer: candid about what makes the role worthwhile at your size.
Weak answer: an enthusiastic yes with no reasoning.
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Kit 5: Fractional and Part-Time Controller Questions
A scoping conversation with evaluation attached: what is inside the monthly scope, how many other clients, who covers during your close, what stays with you if the engagement ends, and when they would tell you to hire full-time.
Use when you are engaging a controller for a set number of days or hours, as an
employee or a contractor, rather than hiring full-time.
Candidate / firm: __
Days or hours per month: __
Interviewer: __
Date: __
WHAT TO SETTLE BEFORE THE INTERVIEW ENDS
Fractional engagements fail on scope and availability far more often than on
skill. Treat this set as a scoping conversation with evaluation attached, and
write the answers down: they become the engagement terms.
QUESTIONS
1. What exactly is inside your monthly scope, and what triggers extra work?
Why ask: undefined scope is the single biggest source of dispute.
Strong answer: a written list of deliverables and dates, plus named
exceptions such as audit support or a system change.
Weak answer: "whatever you need."
2. How many days a month does a business at our volume actually take?
Why ask: it tests whether they have priced work like yours before.
Strong answer: gives a range tied to transaction volume, entity count, and
how clean the books are today.
Weak answer: quotes a figure without asking anything about you.
3. How many other clients do you carry, and when are you unavailable?
Why ask: close weeks collide across clients.
Strong answer: names the number, the busy windows, and how they stage closes
so yours is not always last.
Weak answer: avoids the number.
4. Who covers if you are ill during our close?
Why ask: a fractional controller can be a single point of failure.
Strong answer: a named backup, or a documented process someone else could
pick up.
Weak answer: no coverage plan at all.
5. What stays with us if the engagement ends?
Why ask: continuity of records is the main risk of an outside arrangement.
Strong answer: everything lives in your systems and your files, not theirs,
and they will document the close before leaving.
Weak answer: working papers held in the provider's own tools.
6. What do you need from us each month, by when?
Why ask: fractional work fails on the client side just as often.
Strong answer: a short, specific list with dates, and consequences stated
plainly if it slips.
Weak answer: no expectations set for you.
7. At what point would you tell us to hire someone full-time?
Why ask: an honest provider will name the point where they stop being the
right answer.
Strong answer: gives concrete triggers such as entity count, financing, or
the volume of judgment calls.
Weak answer: never sees an end to the arrangement.
8. How will you be classified, and who supervises the work?
Why ask: employee versus contractor status has real consequences.
Strong answer: engages through a firm or has clear contractor terms, and does
not resist the question.
Weak answer: treats the question as a formality.
NOTES
__
Kit 6: Work Sample and Debrief Scorecard
The exercise brief, the live debrief questions, and a six-area rubric scored 1 to 5 with written evidence. Use it in the final round alongside whichever kit you chose above.
Financial Controller Work Sample and Debrief Scorecard
FINANCIAL CONTROLLER WORK SAMPLE AND DEBRIEF SCORECARD
A 60 to 90 minute exercise plus the debrief that scores it. Use it in the final
round for every shortlisted candidate, and pay for the candidate's time.
Candidate: __
Kit used in the interview: __
Interviewer: __
Date: __
PART 1: THE EXERCISE (SEND IN ADVANCE)
Send a sanitized version of your own trial balance, one bank reconciliation, and
one month of financial statements, with names and amounts scaled or replaced.
Plant two or three realistic issues, for example:
•an accrual that was never reversed
•a large deposit posted to revenue that is really a customer prepayment
•an expense account with a balance that moves in the wrong direction
•an intercompany balance that does not agree between entities
Ask the candidate to come back with: the three things they would investigate
first, what they think each one is, and what they would ask us for.
Do not ask for a finished audit. You are testing what they notice and how they
ask, not how many hours they will donate.
PART 2: THE DEBRIEF (LIVE, 45 MINUTES)
•Which item did you look at first, and why that one?
•What did you assume, and what would change your answer?
•What would you have asked us if you could have called mid-exercise?
•Which of these would you fix quietly, and which would you escalate to me?
•How would you stop each one from happening again?
PART 3: SCORECARD (SCORE 1 TO 5, WITH EVIDENCE)
Noticing: found the planted issues without hints [ 1 2 3 4 5 ]
Evidence: __
Prioritization: ranked by risk, not by size [ 1 2 3 4 5 ]
Evidence: __
Explanation: made it clear to a non-accountant [ 1 2 3 4 5 ]
Evidence: __
Escalation judgment: knew what to bring to the owner [ 1 2 3 4 5 ]
Evidence: __
Prevention: proposed a proportionate control [ 1 2 3 4 5 ]
Evidence: __
Scope fit: matched the kit you interviewed against [ 1 2 3 4 5 ]
Evidence: __
SUMMARY
Total: ______ / 30
Kit used: [ ] Standard [ ] Group [ ] Technical [ ] First hire [ ] Fractional
References checked: [ ] Yes [ ] No
Credential verified, if required: [ ] Yes [ ] N/A
Recommendation: [ ] Strong hire [ ] Hire [ ] Maybe [ ] No hire
Key strengths: __
Key concerns: __
Note: score independently before comparing, and score against the kit you
actually used. A candidate who scores well on the first-hire kit is not
automatically a fit for a group role, and the reverse is more often true.
Consolidation Questions Most Interviews Skip
If your business has more than one legal entity, consolidation is the skill that separates a group controller from a very good single-entity one, and it is the area interviews most often never reach. Three questions cover most of the ground, and each of them is hard to answer convincingly without having done the work.
What was the intercompany elimination that caused you the most trouble?
Why ask it: Anyone can describe consolidation in the abstract. Naming a specific elimination that went wrong is the fastest proof that the candidate has actually closed a group rather than read about one.
Strong answer: Describes balances that stopped agreeing between two entities, how far the difference had drifted before anyone noticed, and the monthly matching step they introduced so it could not drift again.
Weak answer: Treats consolidation as a function of the software, or cannot name a single elimination that ever caused a problem.
Do the entities share a chart of accounts? If not, how did you map them?
Why ask it: Group reporting is only as trustworthy as the mapping underneath it. A mapping table with no owner is one of the most common reasons consolidated numbers quietly stop meaning anything.
Strong answer: Describes a maintained mapping table, names who owned it, and explains how a new account got approved before anyone was allowed to post to it.
Weak answer: A spreadsheet that lived on someone's desktop, or new accounts created locally without review.
How did you close a group where one location was always late?
Why ask it: At group level, control is mostly influence at a distance. This question tests whether the candidate fixed the cause or simply moved everyone's deadline to accommodate the slowest site.
Strong answer: Describes a hard cut-off, an agreed escalation, and something they changed on the local side (a template, a resource, an earlier bank feed) so the site could actually hit the date.
Weak answer: Extended the close for the whole group, or escalated to the owner without first trying to fix the local constraint.
You do not need to evaluate the technical accuracy of the answers to use these well. Listen for specificity: a candidate who has closed a group names entities, dates, and the moment something stopped agreeing. A candidate who has not describes consolidation as a feature. That difference is audible to anyone, which is the point of asking.
Systems, Data, and the Chart of Accounts
Ask what the candidate would change about your accounting system and, more importantly, when. The answer is one of the clearest signals of judgment in the whole interview, because a controller who wants a migration before the first clean close is telling you they prefer projects to process.
The chart of accounts deserves its own question. It is a reporting decision, not a housekeeping one, and a controller who treats it as cleanup will hand you a tidier ledger that answers no new questions. Ask who was allowed to add an account in their last role, and whether anyone approved it before the first posting.
Systems judgment
Can say when a migration is premature
Names what the current system still does well
Sizes the project in months, not weeks
Chart of accounts
Treats it as a reporting decision, not a cleanup
Knows who is allowed to add an account
Can explain a restructure without breaking history
Data hygiene
Reconciles the subledger to the ledger routinely
Notices when a feed silently stops
Keeps one source of truth per number
Red flags
Wants a new system before the first close
Cannot explain a report they built
Describes spreadsheets nobody else can run
One more question is worth the minute it takes: ask them to describe a report they built that someone else now runs. Work that only functions while its author is present is the quiet failure mode of a small finance function, and it surfaces during the first vacation rather than during the interview.
A Work Sample That Beats a Resume
A paid work sample tells you more about a controller than any answer you could not grade. Send a sanitized month of your own numbers with two or three realistic issues planted in it, and ask what they would investigate first. What they notice, and what they bring to you rather than fix quietly, is the hire.
Sanitize a real month
Take your own trial balance, one bank reconciliation, and one month of statements. Scale or replace names and amounts so nothing confidential leaves the building.
Plant two or three issues
An accrual never reversed, a customer prepayment sitting in revenue, an intercompany balance that does not agree. Realistic, not exotic.
Ask for three, not for everything
Request the three items they would investigate first, what they think each is, and what they would ask you for. Pay for the time and cap it.
Debrief live and score
Forty five minutes on what they looked at first, what they assumed, and what they would escalate to you. Score six areas from 1 to 5 with written evidence.
Keep the ask small and honest. Three items, ninety minutes, paid, with a clear cap. Candidates at this level have options, and an unpaid multi-day exercise costs you the people you most want. It also inflates the sample: what you learn from a rushed ninety minutes is closer to how the person will actually work in a busy close.
Sanitize Before You Send
Scale or replace customer names, employee names, and amounts before the file leaves your building, and send it under the same confidentiality agreement you would use for any candidate exercise. Never send live bank credentials or a real reconciliation with account numbers in it. The exercise works just as well on scaled figures, because you are testing what the candidate notices, not what your revenue actually was.
Public Accounting, Industry, and the CPA Question
Controller candidates arrive in three broad shapes, and each one is strong in a different place. Scoring them on a single scale is how good candidates get rejected for the background they came from rather than for the job they would do.
Strength
Public accounting background
Industry background
Comfortable with audit and technical positions
Has run a close under real operating pressure
Used to documenting a judgment in writing
Used to explaining numbers to a non-finance owner
Has managed an accounting team day to day
Neither column is better; they fail differently. A first-time industry hire from public accounting can be slow to accept that a close has to ship imperfect, and an industry candidate may not have written a technical position in years. Ask each about the column they are weaker in, and weight the answer according to your scope.
On the credential: require a CPA only if an auditor, lender, or acquirer will read your statements. If they will not, requiring it narrows the pool for a benefit you may never use, and preferred rather than required is the better setting. Whatever you choose, apply it to every candidate and verify the license with the state board if you require it.
Structured, Consistent, and Legal Interviewing
A structured interview means every candidate gets the same questions, in the same order, scored on the same rubric. It predicts performance better than an open conversation and it is also the cleanest defense you have, because it shows the decision rested on job-related evidence rather than impression.
The rules here are the same as for any role. Keep every question tied to the work, and avoid the questions employers cannot ask, including age, family plans, national origin, religion, disability, and financial history. For a finance hire, that last one deserves care: personal credit and personal debt are not job-related interview topics, and any background or credit check runs under its own rules after an offer, not as small talk in the room.
Keep Every Question Job-Related
The EEOC prohibits hiring decisions based on protected characteristics including age, race, religion, national origin, sex, pregnancy, and disability. For a controller, ask about the close, the controls, the reporting, and the judgment calls. Asking every candidate the same job-related questions and recording the evidence is both the fairer approach and the more accurate one.
Two habits carry most of the weight: score immediately after each conversation while the answers are fresh, and have each interviewer score independently before anyone discusses. A shared structured interview process plus an evaluation form is enough structure for a small business. This is general information, not legal advice.
Interviewing a Controller Without an HR Department
Most companies hiring a financial controller for the first time have no HR function and no finance peer, which means the owner is interviewing for judgment they do not personally hold. That is a solvable problem, but only if you change what you are grading and how many rounds you plan.
You are interviewing for judgment you do not have yourself
Most owners hiring a financial controller cannot grade the technical answer, and trying to is the wrong goal. What you can grade is whether the candidate explains a judgment call in language you follow, names the guidance or the reviewer behind it, and tells you what would change their mind. Every question in these kits carries a why-ask note and a strong-answer note for exactly this reason. If a candidate cannot make their own memo clear to you, they will not make it clear to your lender or your auditor either, and that is a job-related conclusion you are fully qualified to draw.
The wrong kit produces a confident wrong hire
The most expensive mistake at this level is not a weak candidate, it is a strong candidate scoped against the wrong version of the role. A group controller interviewed on first-hire questions looks impressive and then stalls when there is no team to run. A first-hire builder interviewed on consolidation questions looks thin and is exactly who you needed. Decide which of the five kits describes your role before you write a single question, put that decision in the job posting, and score every candidate against the same kit.
You get one interview loop, not four
A company with a finance department can afford a screen, a technical panel, a case, and a leadership round. You get two conversations and a work sample, so each has to do more work. Use one kit rather than a mix, run the work sample in the final round, and score immediately while the answers are fresh. After the decision, the paperwork side is where FirstHR fits: e-signature on the offer and the confidentiality agreement, document management for the signed file, and task workflows for system and bank access. Applicant tracking is coming soon to FirstHR.
References carry more weight here than at almost any other level, so make them specific. Ask each reference how the person handled being wrong, whether the close landed on the same day each month, and what they would not hand this person again. Vague warmth is a soft no. A short call before the offer is worth more than a fourth interview.
If you are still deciding between levels, the controller interview kit covers the competency-by-competency version of this process, and the CFO questions cover the strategy-weighted role above it. Applicant tracking is coming soon to FirstHR.
What Controller Pay Tells You About Scope
Read the wage ladder as a scope signal rather than as a single number. Controllers sit inside the federal financial managers occupation, whose median is high because the group also contains treasury and corporate finance leadership, so the percentile spread is far more informative than the midpoint.
Financial Managers: Median $166,570 (BLS OEWS, May 2025)
Financial managers, the occupation that includes controllers, reported a median annual wage of $166,570, with the tenth percentile at $94,310, the twenty fifth at $125,490, the seventy fifth at $219,980, and the ninetieth at $323,270 (U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2025). The same source projects about 74,600 openings a year in the occupation over the decade to 2034.
In practice, a single-entity controller at a small company sits near the lower quartile, a multi-entity group role with audit exposure sits above the median, and the top decile reflects corporate finance leadership rather than anything you are hiring. For contrast, the accountants and auditors occupation reported a median of $83,680 in the same survey, which is roughly where a strong senior accountant sits.
A fractional controller is billed monthly for a few days of work and costs a fraction of a full-time salary, which is why many businesses start there and convert later. Whichever route you take, set the range before you post, and settle the exempt classification before the offer rather than after. The federal criteria are published in the Department of Labor white-collar exemption fact sheet, and some states set stricter thresholds.
After the Offer: Handing Over the Books
A controller handover is different from an ordinary onboarding because access is the job. Stage it deliberately: read access first, posting rights after a supervised close, and payment release last. Put the scope you interviewed against into the offer itself, so the role the person accepted is the role you assessed.
Offer and confidentiality first
Put the scope you interviewed against into the offer itself, and sign a confidentiality agreement before any book access is granted.
Stage the access
Read access to the ledger and bank on day one, posting rights after the first supervised close, payment release last and never alone.
Keep an owner view
Retain your own read-only bank and accounting login permanently. A strong controller will expect this and often ask for it.
Hand over the record, not the story
The last three closes, the reconciliations, the open items list, and every filing deadline, in writing rather than in a conversation.
Hand over the record rather than the story. The last three closes, the reconciliations, the open items, and every filing deadline belong in writing, not in a conversation you will both remember differently in March. The federal occupation profile for accountants and auditors is a useful sanity check on what the surrounding roles are expected to cover.
Once you have decided, the offer letter template handles the terms and the confidentiality agreement covers the access. Both should be signed before the first login is issued, not alongside it.
FirstHR connects the offer, the e-signature, the new-hire paperwork, and the access checklist in one place, so a business without an HR department can onboard a senior finance hire with the controls staged from the start. FirstHR is an onboarding and HR platform, not an accounting or financial reporting system, so keep those separate. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Financial controller covers at least five different jobs, so decide the scope before you write a single question.
Four questions select the kit: how many entities, who reads the statements, is there a team, and who does the role report to.
Use one kit for every candidate rather than a mix, so you compare candidates instead of comparing conversations.
Every question needs a stated reason for asking and a note on what a strong answer sounds like, so a non-accountant can score it.
Finish with a paid work sample: a sanitized trial balance with two or three planted issues and a live forty five minute debrief.
Read the BLS financial managers percentile ladder as a scope signal, from $94,310 at the tenth percentile to $323,270 at the ninetieth.
Frequently Asked Questions
What should I ask a financial controller candidate?
Ask questions scoped to the version of the role you are actually filling, because the title covers at least five different jobs. For a standard single-entity role, ask for the close calendar day by day, which three accounts they reconcile first and why, and what their last set of financial statements did not tell the owner. For a group role, ask about the intercompany elimination that caused the most trouble and how the entities’ charts of accounts were mapped. For a first finance hire, ask what they would deliberately not do in the first six months. Every question should have a stated reason for asking and a note on what a strong answer sounds like, so the person running the interview can judge the response without an accounting background of their own.
How is a financial controller different from a controller?
In United States job postings the two titles usually describe the same job, and most employers use them interchangeably. Financial controller is somewhat more common at companies with a European parent or a group structure, and controller is the more common domestic phrasing. What actually changes the role is scope rather than the word in front of it: how many legal entities are consolidated, whether an outside auditor reviews the numbers, whether there is an existing accounting team to run, and whether the person reports to an owner or to a CFO. Decide those four things before writing the posting, then interview against that scope. This page keeps a separate kit for each of the common scopes so the questions match the job.
How do I interview a controller if I am not an accountant?
You are not grading technical correctness, you are grading explanation, prioritization, and escalation judgment, all of which a non-accountant can assess. Ask the candidate to walk you through a judgment call in plain language, then ask what would change their answer and who reviewed it. A candidate who cannot make their own reasoning clear to you will not make it clear to a lender or an auditor either. Add a paid work sample: send a sanitized trial balance with two or three planted issues and ask which three things they would investigate first. What they notice, how they rank it, and what they would bring to you rather than fix quietly tells you more than any technical answer you could not grade anyway.
Should a financial controller be a CPA?
It depends on who reviews your numbers. If an outside auditor, a lender, or an acquirer will examine your statements, a CPA or an equivalent credential adds real value and is worth requiring. If the role is an internal one at a growing business with no audit, requiring the credential narrows your candidate pool considerably for a benefit you may never use. A useful middle path is to make the credential preferred rather than required, and to test the underlying skill directly through the technical kit and the work sample. Whichever you choose, apply it consistently to every candidate and verify the license through the state board if you require it. This is general information, not legal advice.
What is a good work sample for a controller interview?
Send a sanitized version of one real month: a trial balance, one bank reconciliation, and one set of financial statements, with names and amounts scaled or replaced. Plant two or three realistic issues such as an accrual that was never reversed, a customer prepayment sitting in revenue, or an intercompany balance that does not agree. Ask for three things only: what they would investigate first, what they think each item is, and what they would ask you for. Cap the exercise at about ninety minutes and pay for the candidate’s time. Then debrief live and score noticing, prioritization, explanation, escalation judgment, prevention, and scope fit from 1 to 5 with written evidence. It is far more predictive than asking someone to describe a close process.
Is a financial controller exempt from overtime?
A financial controller is usually classified as exempt, but the classification depends on the actual duties and salary, not on the title. The federal white-collar exemptions require both a salary basis test and a duties test, and the Department of Labor publishes the criteria for the executive, administrative, and professional exemptions. Most controller roles meet the administrative or executive duties tests because they exercise discretion over significant financial matters and often supervise staff. State rules can be stricter than the federal ones, including higher salary thresholds in some states, so confirm both before you classify. Decide the classification before you extend the offer rather than after, and document the duties you relied on. This is general information, not legal advice.
How much does a financial controller cost?
Controllers fall inside the federal financial managers occupation, which reported a median annual wage of $166,570 in the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey published for May 2025. The tenth percentile was $94,310 and the ninetieth was $323,270, a spread wide enough that the median tells you very little on its own. Read the percentile ladder as a scope signal: single-entity roles at small companies sit near the lower quartile, multi-entity group roles with audit exposure sit above the median, and the top of the range reflects large corporate finance leadership rather than a small-business controller. A fractional controller engaged for a few days a month is billed monthly and costs a fraction of a full-time salary, which is why many smaller businesses start there.
How many interview rounds does a controller hire need?
Two conversations and a work sample is a realistic and sufficient process for a small business, provided each stage is structured. Use the first conversation for the kit that matches your scope, the second for the areas that concerned you plus the reporting relationship, and the work sample debrief as the final round. Ask the same questions of every candidate and score immediately after each stage while the answers are fresh. Verify references specifically on close accuracy, controls, and how the person handled being wrong, and verify any credential you decided to require. Adding rounds beyond this rarely improves the decision and does cost you strong candidates, who at this level usually hold more than one conversation at a time.
