Cohesyve · Practice for candidates
Preparing for a Financial Controller role? Start by finding out where you stand.
Import the actual job you're going for, run a simulation built from it, and get a scored report showing which of these areas you're weakest in — before you spend weeks studying the wrong thing.
3
free assessments
$0
no card required
Full
scored report every run
Every
question type included
3 free assessments · No card required · Pro from $16/mo
Overview
Controller interviews are less about technical accounting than candidates expect and more about ownership. The panel wants to know whether the close would land without them chasing you, whether the controls would hold, and whether you can manage a small team through a difficult year-end. Expect a technical exercise, but expect the decisive stage to be a conversation with the finance director about how you run a function. This page sets out the stages, the topics and the questions.
The hiring process, stage by stage
CV screen
Screened on scope: number of entities, team size, whether you owned statutory reporting and audit, and the systems environment you managed.
How to prepare: Lead with scope rather than duties. State entities, ledgers, headcount reporting to you, and whether you signed off statutory accounts. Scale is the filter at this level.
Call with the finance director or a specialist recruiter
Covers your remit, what the FD would delegate to you, why the role is open and how it is structured relative to FP&A.
How to prepare: Ask early whether the role is reporting-led or a broader number two, since the two demand different evidence. Prepare a clear account of what your current FD leaves entirely with you.
Technical exercise or case
Often a review task rather than a build: a pack or a set of accounts with issues in it, a consolidation question, or a scenario about a control failure you must respond to.
How to prepare: Practise reviewing rather than preparing. Work through a pack systematically — do the totals reconcile, do the balances move sensibly, does the commentary match the numbers, and what is missing entirely.
Panel with stakeholders
Usually the FD plus an operational leader and sometimes HR. Tests how you deal with budget holders, how you manage a team, and how you behave when a deadline is at risk.
How to prepare: Prepare stories on turning around a late close, managing an underperformer, and pushing back on a commercial stakeholder. Have a view on what you would do in your first ninety days.
Final conversation and references
A closing discussion on your first ninety days, the audit relationship, and how you would improve the reporting the business currently receives.
How to prepare: Bring a specific, modest ninety-day plan: understand the close, stabilise it, then improve one thing. Grand restructuring proposals from someone who has not seen the ledger tend to land badly.
What to study
Ownership of the close and the reporting cycle
It is the core deliverable. The panel is deciding whether the numbers land on time without the FD intervening.
Controls and risk
The controller owns the control environment. Being able to describe a control you designed, and one that failed on your watch, is more persuasive than describing a framework.
Statutory reporting, audit and compliance
Audit is the visible test of the function you run, and a difficult audit is expensive in both fees and credibility.
Consolidation and group reporting
Multi-entity work is where technical depth actually shows, and it is a common gap in candidates stepping up from a single-entity role.
Leading a small finance team
Most controller failures are management failures rather than technical ones — a team that misses deadlines or loses people mid-year.
Cohesyve for candidates
Practise a Financial Controller assessment before the real one
Run the same AI job simulations companies use to evaluate applicants. You get a scored report showing where you're strong and where you're not, plus what to work on.
Your preparation plan
Four weeks out
Define your scope precisely and study the employer in detail.
- •Write down your current scope in numbers — entities, ledgers, headcount, close days
- •Read their filed accounts, including the accounting policies and any audit emphasis
- •Identify what would be genuinely new for you in this role and prepare an honest account of it
- •Refresh consolidation mechanics if your current role is single-entity
Two weeks out
Practise reviewing rather than preparing.
- •Review a management pack critically and list what is missing, inconsistent or unexplained
- •Work through a consolidation with intercompany and currency movements
- •Prepare your position on two control weaknesses you have fixed
- •Draft your ninety-day plan in three short phases
The final week
Rehearse the management and stakeholder material.
- •Rehearse stories on a late close, an underperformer and a stakeholder pushback
- •Practise summarising your ninety-day plan in ninety seconds
- •Prepare six questions on their close, controls, audit history and team structure
- •Reconcile what you plan to claim with what a reference would confirm
The day before and the day of
Consolidate rather than add.
- •Reread the job description and the FD conversation notes together
- •Reduce your ninety-day plan to a single page you can talk from without reading
- •Decide which two examples you most want the panel to remember
- •Plan to ask about the state of the close early, since the answer should shape the rest of your answers
Questions to expect
“Walk me through the close you currently own.”
What they're really asking: What is the real scope of your ownership, and do you manage a process or perform tasks within one?
How to answer: Give the shape first — entities, working days, team — then the dependencies and where it typically strains. Name what you delegate and what you review personally, and say honestly how often the deadline is met.
“Tell me about a control failure on your watch.”
What they're really asking: Do you know where your environment is weak, and are you candid about it?
How to answer: Pick a real one, describe how it was discovered, the exposure, the immediate remediation and the permanent change. Denying that anything has ever failed reads as either inexperience or evasion.
“The close is going to be late. What do you do?”
What they're really asking: Do you communicate early, and can you triage what actually matters in the pack?
How to answer: Say you tell the FD as soon as you know, with a revised time and the reason. Then describe triage — what must be right, what can be estimated with a stated basis and corrected next month, and what can be deferred.
“How would you improve the reporting this business currently gets?”
What they're really asking: Have you thought about their business, and are you appropriately humble about what you do not yet know?
How to answer: Base it on what you can see from their published information and the job advert, phrase it as a hypothesis, and say what you would check in your first month before changing anything.
“How do you handle a member of your team who is missing deadlines?”
What they're really asking: Will you manage the problem or absorb the work yourself until the team is dependent on you?
How to answer: Describe establishing the cause first — capability, capacity or clarity — then a specific intervention, a timeframe and a documented conversation. Include an example that ended with either improvement or an exit.
“What would your first ninety days look like?”
What they're really asking: Will you destabilise a working process, or learn it before you change it?
How to answer: Three phases: understand the close and the team through one full cycle, stabilise what is fragile, then improve one high-value thing. Name the diagnostics you would run in month one.
What to bring as evidence
A one-page description of your current close: entities, working days, team, deliverables
A control you designed or repaired, with the exposure it addressed
An audit you led, including how you managed the PBC list and any adjustments proposed
A consolidation you own, including how you resolve intercompany differences
An example of developing or exiting a team member, handled properly
A ninety-day plan tailored to this employer, kept modest and specific
Common mistakes
Presenting as a senior preparer rather than an owner of a function.
Arriving with a sweeping restructuring plan for a ledger you have never seen.
Claiming no control has ever failed, which reads as evasion to an experienced FD.
Being unable to describe managing an underperformer, in a role that is substantially management.
Talking about the close in tasks rather than dependencies and owners.
Overstating consolidation experience when the reality is a single entity with a group template.
Questions to ask them
- ?
What is the close timetable now, and what is the FD hoping it becomes?
- ?
How did the last audit go, and were there any adjustments or management letter points?
- ?
Which controls are you least comfortable with today?
- ?
How is the split of responsibility between this role and FP&A defined?
- ?
How many entities, on how many systems, and is a migration planned?
- ?
Why is this role open, and what did the previous holder find hardest?
Frequently Asked Questions
How much does the size of my current team matter?
It matters for like-for-like comparison but is rarely decisive. What counts more is whether you owned the outcome — the close landing, the audit closing — rather than the headcount underneath you.
Can I move into a controller role without statutory reporting experience?
Sometimes, particularly where a group parent or an outsourced provider prepares the statutory accounts. Be direct about the gap and specific about the adjacent experience that makes it bridgeable.
Should I expect a technical test at this level?
Frequently, though it usually takes the form of reviewing a pack or a set of accounts rather than building a model. The skill being tested is what you notice and what you ask about, not your speed.
How specific should my ninety-day plan be?
Specific in method, modest in conclusions. Naming the diagnostics you would run reads well; announcing a restructure of a function you have not seen does not.
Is there a sensible way to rehearse the review exercise?
Yes — rehearse under observation rather than alone, because the marks are in what you notice and articulate. Cohesyve can generate a controller-level review scenario from the job advert itself and score your response, with three assessments included free.
Practice
What a Financial Controller assessment tests, and how it's scored →
Career guide
What a Financial Controller actually does, and where the path leads →
Prepare for another role
Cohesyve · Practice for candidates
Don't walk in guessing. Find out where you stand first.
Three free scored practice runs, a full report on every one, and a learning pathway built from what you actually got wrong. No card required.
3
free assessments
$0
no card required
Full
scored report every run
Every
question type included
3 free assessments · No card required · Pro from $16/mo
For hiring teams
Hiring for a Financial Controller role? See how your applicants perform before you spend interview time.