Questions to Ask in Finance Interview
Questions for candidates interviewing for a corporate finance, FP&A, controllership, or treasury role. They cover which team you would join, how long the close takes, what systems you would live in, and whether the team's analysis changes any decisions.
The questions
Open any question for the note
Which team would I be joining: FP&A, controllership, treasury, or something else?
Why ask it
Finance is several very different jobs behind one word. Ask whether the boundaries are firm, because a hybrid role usually means carrying both sets of deadlines rather than half of each.
What does the monthly close look like, and how many days does it take?
Why ask it
Close length is the best available proxy for how well the function runs. A ten-day close means most of your month goes to it, whatever the job description promises about analysis.
How much of the role is reporting, and how much is analysis someone acts on?
Why ask it
Nearly every finance advert promises business partnering and delivers reporting. Ask for a rough percentage, then ask who received the last piece of analysis.
Who reads what I'd produce, and what do they do with it?
Why ask it
If nobody can name a reader, the report exists out of habit. A role producing unread output is a difficult one to grow out of, however senior the title sounds.
What systems would I work in, and how much still lives in spreadsheets?
Why ask it
This describes your actual days. A current ERP with a planning tool is a different life from consolidating fifteen workbooks by hand every month, and only one of them leaves time to think.
How many people are in the team, and how is the work divided?
Why ask it
Team size sets how specialised you would be. Three people means you touch everything, including the parts nobody wants. Thirty means one process, done deeply.
What does the busy period look like, and how long does it last?
Why ask it
Year end, audit, and budget season are unavoidable. Ask when they fall, how many weeks each runs, and whether anyone actually takes time back afterwards.
How is the budget built here: targets handed down, or built up from the teams?
Why ask it
This shows where power sits. Targets from above mean defending numbers you did not set. Bottom-up means negotiating with every department head, which is a people job more than a modelling one.
How often is the forecast revised, and how accurate has it been?
Why ask it
Forecast variance is measurable and rarely volunteered. A team that tracks its own accuracy has a working process. A team that has never checked is guessing with confidence.
Is finance in the room when decisions get made, or asked to model them afterwards?
Why ask it
This is the real line between influential and clerical finance work. Ask when the team was last consulted before a decision rather than after one.
What was the last recommendation from this team that changed a decision?
Why ask it
A concrete example is the test. If nobody can produce one, the function is scorekeeping, whatever the recruitment material said about partnering with the business.
Who audits you, and when is year end?
Why ask it
The auditor and the year end date shape a large part of your calendar. It is also the natural way into asking how the last audit went.
Have there been restatements, control findings, or material weaknesses I should know about?
Why ask it
A fair question asked plainly, and often answered honestly because much of it is public. Findings are not disqualifying, but they predict how your first year would be spent.
Is the company profitable, and if not, how long is the runway?
Why ask it
Adjust for the stage of the company, then ask directly. Joining a finance team without knowing the cash position is a risk you can remove with one question.
Who owns the number when finance and the business disagree?
Why ask it
Every finance function has this tension. What matters is whether there is a defined way to resolve it, or whether it comes down to who escalates loudest.
What's broken in this team's process that you'd want fixed?
Why ask it
Naming a problem invites candour and hands you a first project. If the answer is that nothing is broken, you are either being managed or joining a team with no ambition.
What qualification support is there, and does study leave happen in practice?
Why ask it
Study support is frequently written into policy and unavailable in reality. Ask how many people are on the programme now and whether anyone took their leave last year.
Where do people from this team go next, inside or outside the company?
Why ask it
Exit routes tell you what the role is worth on the market. A team nobody ever leaves can mean loyalty or stagnation, so ask which and expect a specific example.
Why is this role open?
Why ask it
Growth, a resignation, and a restructure produce three different first years. If the last person left, ask how long they stayed and whether they moved elsewhere internally.
What would make you say, a year from now, that hiring me was the right call?
Why ask it
This closes on something concrete, and the answer is usually your first-year objectives stated informally. Note whether it resembles the job description you applied to.
Interviewing for a finance role
Practical guidance for the conversation itself
Work out which finance job this actually is
Reporting and control
Close, consolidation, audit, and compliance. The calendar is fixed and the deadlines do not move, so the skill is accuracy at speed. Ask about close length and audit timing.
Planning and analysis
Budget, forecast, and decision support. Its value depends entirely on whether the business listens, so ask when the team was last consulted before a decision rather than after it.
Treasury and cash
Liquidity, funding, and banking relationships. Ask about covenant headroom and who holds the relationships with lenders.
Ask for numbers rather than adjectives
- Days to close, and whether that figure has been improving.
- Forecast variance across the last four quarters.
- Team headcount now compared with two years ago.
- How many spreadsheets sit between the ERP and the board pack.
How to press when an answer stays vague
- If the close is described as quick, ask which day last month's numbers were final. A named date is much harder to soften than an adjective.
- If business partnering comes up, ask who received the last piece of analysis and what they did with it. You want a name and a decision, and if neither exists you have your answer.
- If study support is described as available, ask how many people are on the programme right now and whether anyone took their leave last year.
- If a system replacement is mentioned, ask what the go-live date was originally and what it is now. Finance implementations slip, and mid-slip is a specific kind of year to join.
Common mistakes
- Asking only technical questions. Technical competence is assumed by the final round, and the differentiator is whether you can talk to people outside finance.
- Not asking about the close or the busy season, then discovering the shape of your year in the first month.
- Ignoring the company's own financial position, which is public for listed companies and a fair question everywhere else.
- Treating study support as settled because it appears in the handbook.