Accounting Interview Questions to Ask Candidates
Questions for a hiring manager interviewing accountants and finance staff. They ask about work the candidate has actually done, the last close they ran, a reconciliation that would not balance, an error they caught and one they missed, rather than inviting descriptions of how detail-oriented they are.
The questions
Open any question for the note
Walk me through the last month-end close you worked on. Which parts were yours?
Why ask it
The most efficient opening question, because a candidate who has done the work describes it in order and names their own scope without prompting. Watch for a switch from I to we when you ask about specific tasks, and follow up on any step they skip: accruals and intercompany are the usual gaps.
Which systems have you worked in, and which did you set up or administer rather than just use?
Why ask it
Separates familiarity from ownership. Someone who has built a chart of accounts, run an implementation, or managed permissions can talk about what went wrong in the process. A list of system names with no detail behind any of them usually means view-only exposure.
How long did your last close take, and what made it slow?
Why ask it
The number tells you the scale they are used to; the reason tells you how they think. Strong answers name a specific bottleneck, waiting for a bank feed, a subsidiary that reported late, a manual journal. Answering that it always just took that long suggests they have never questioned the process.
Tell me about a reconciliation that wouldn't balance. How did you find the problem?
Why ask it
The most reliable technical question you can ask, because the method is hard to fabricate. Look for a structured search: checking totals both ways, isolating by period, looking for transpositions or a duplicated entry, testing whether the difference equals a known amount. Vague persistence is not a method.
What's the largest error you've caught before it went out, and how did you catch it?
Why ask it
You want the mechanism, not the heroism. Answers that credit a checklist, a variance review, or a second pair of eyes describe someone who works within a system. A candidate who catches everything by instinct is describing luck, and their next employer inherits the risk.
What's an error that got past you, and what changed afterwards?
Why ask it
Everyone with real experience has one, so a denial is the answer. What matters is whether they changed a process rather than resolving to be more careful. Note also how they describe telling people, since the response to an error usually causes more damage than the error itself.
How do you check your own work when nobody else reviews it?
Why ask it
Common in small finance teams, and a genuinely different skill from working under review. Good answers include reasonableness checks against prior periods, a deliberate gap before rereading, and tie-outs to an independent source. Answering that they are simply careful means they have not thought about it.
How would you explain a variance to a manager who has no finance background?
Why ask it
Ask them to do it rather than describe how they would. Watch for whether they lead with the number and its cause in one sentence, or start with methodology. The ability to say what happened, why, and what it means for the budget is what makes an accountant useful outside finance.
What's the most complex spreadsheet you've built, and what did it do?
Why ask it
Most finance work still runs on spreadsheets, so this is a practical skills question. Look for structure, separated inputs and calculations, checks that flag when totals do not tie, documented assumptions. Candidates who mention having to hand a model to someone else usually build better ones.
Tell me about a deadline you missed or nearly missed. What did you tell people, and when?
Why ask it
The timing of the warning is the whole answer. Someone who raised it as soon as the risk was clear is safe to hire; someone who worked through the night and told nobody will one day do the same on a filing deadline. Ask what they would do differently now.
What do you do when you're not sure of the correct treatment?
Why ask it
Tests judgment and honesty at once. Reasonable answers name a source and a person: the standard itself, a technical helpline, the auditors, a former manager. Be wary of anyone who says this never happens, and equally of anyone whose only answer is to ask someone else.
What have you had to look up recently, and where did you look?
Why ask it
A better test of currency than asking how they keep up with standards, because it requires a specific example from the last few months. It also shows whether they use primary sources or search results, which matters when a treatment is contested.
Describe a control you added or tightened. What was the risk?
Why ask it
Distinguishes someone who follows controls from someone who understands what they are for. Look for a named risk, duplicate payments, an unreviewed journal, one person holding both approval and payment, and for awareness of the cost the control added. Reciting the phrase segregation of duties is not an answer.
What's the most tedious recurring task you've simplified, and how?
Why ask it
Practical, and it tends to produce the most enthusiastic answer of the interview. The scale does not matter: a template, a report, a reordered process. What you learn is whether they accept inherited work as fixed or look at what it costs each month.
Tell me about an auditor request you couldn't satisfy. What happened?
Why ask it
Reveals experience of scrutiny and how they behave under it. Good answers describe explaining the limitation, offering the closest available support, and agreeing a fix for the following year. Candidates who say auditors were never a problem may not have been the person answering them.
Has anyone ever asked you to record something you weren't comfortable with?
Why ask it
Ask it plainly and let the silence run. What you want is a proportionate response: a question asked, an explanation sought, escalation only if needed. Both extremes are informative, someone who has never noticed a questionable request, and someone who describes every disagreement as a matter of principle.
Where would you expect a business like ours to have problems in its books?
Why ask it
A good late-stage question because it tests whether they have thought about your business rather than the role. Strong candidates name something plausible for your size and sector: revenue cut-off, inventory, expense approvals, intercompany. It also tells you what they would look at first if hired.
What kind of work do you want more of, and what do you want less of?
Why ask it
Fit matters more in finance than in most functions because the work is repetitive by design. Someone who wants analysis and reporting will not stay long in a role that is mostly transactional, however well they interview. Better to hear it now than in month four.
What would you need from us in your first month to be useful?
Why ask it
Experienced hires answer with specifics: access, a walkthrough of the close calendar, sight of last year's file, an introduction to whoever owns the source data. Candidates with no requests either have not thought about starting or expect to be told everything, and both are slow to become productive.
What do you want to ask me about the team or the work?
Why ask it
Their questions show what they have understood about the role. Asking about close timelines, who reviews their work, and where the numbers come from indicates someone imagining the actual job. No questions at all, at the end of a technical conversation, is worth weighing against everything else.
Interviewing for finance roles
Practical guidance for the conversation itself
Decide what you are hiring for first
Transactional, reporting, or advisory
Payables and reconciliations, month-end and statutory reporting, and analysis or business partnering call for different people. Write down which of the three dominates the role before you interview, and weight your questions accordingly.
Match the scale
Someone from a large finance function may never have run a full close alone, and someone from a small company may never have worked under formal review. Neither is a defect, but the questions and expectations should differ.
Check what is genuinely required
Be clear about which credentials, licences, or standards knowledge the role actually needs, and verify those directly rather than treating them as a proxy for competence.
Do not interview during close
Interviews squeezed into the busiest week of the month get shortened, and the shortened part is usually the practical assessment. Schedule around your own calendar.
Getting past rehearsed answers
Accounting interviews attract prepared answers about accuracy and attention to detail. A few habits get past them:
- Ask for the last time rather than a typical example. Recency limits how much can be reconstructed.
- Ask for numbers: how many entities, how many journals, how many days to close, how large the discrepancy was.
- Follow every general answer with "what did you actually do first?" once.
- Give a small practical exercise, twenty minutes with a short trial balance or a broken reconciliation, rather than a quiz on definitions.
- Ask the same technical question of every candidate so you can compare answers rather than impressions.
Mistakes interviewers make
Testing memory instead of judgment
Asking someone to recite a standard tests what they revised the night before. Asking how they would decide a treatment, and where they would check, tests what they will actually do at their desk.
Asking about stress and personal life
Questions about how someone copes with pressure, their health, their family arrangements, or their own finances risk straying into areas that are unlawful to consider in many jurisdictions. Ask about workload management with a concrete work example instead.
Hiring for tidiness over reasoning
Accurate work is necessary and easy to test with an exercise. What is harder to replace is someone who notices that a number is implausible before it is wrong, so leave room for questions that probe reasoning.
Skipping the ethics question
It feels awkward and is the one question that occasionally saves a company from serious trouble. Ask it as a matter of routine, in a neutral tone, of every candidate at every level.
Not being honest about the role
If the close is chaotic, the systems are outdated, or the last person left because of the workload, say so. Candidates who accept a role on an inaccurate description tend to leave within the year, and the cost of that lands on your team.
Reading the answers
Method beats outcome
Whether they eventually found the discrepancy matters less than how they narrowed it down. A clear search process transfers to problems they have not seen before.
Ownership of mistakes
The strongest signal in a finance interview is a candidate who describes their own error plainly, including who they told and when. It predicts behaviour when something goes wrong on your books.
Curiosity about the source data
Candidates who ask where the numbers come from, who enters them, and what happens when the source is wrong tend to prevent problems rather than report them afterwards.
Consistency across the loop
Compare notes with other interviewers on specifics rather than overall impressions. Discrepancies in what a candidate claimed to have owned are the most common thing a single interviewer misses.