Accounting Interview Questions to Ask Employer
Questions for an accountant assessing an employer, whether the role is in industry or at a firm. They cover what you would own in the close, the hours in a normal month and the worst one, how much of the work is still manual, who reviews you, what the last audit found, and what support exists for exams.
The questions
Open any question for the note
What would my first month look like, day to day?
Why ask it
A concrete question that most interviewers answer honestly, and it exposes whether onboarding exists. Listen for whether you are shadowing, taking over a task immediately, or arriving mid-close. Being handed a reconciliation on day two is not necessarily bad, but you should know it in advance.
Why is the role open?
Why ask it
Growth, a resignation, a retirement, and a dismissal are four different situations. If the previous person left, ask how long they were in the role and where they went. A role that has been filled twice in two years is worth several follow-up questions before you go further.
Which parts of the close would be mine, and by which day are they due?
Why ask it
This gives you the actual job description. Ask for the close calendar itself if there is one. If nobody can say which tasks belong to the role by which working day, the close is probably run on memory and evenings, and you will be part of that.
How long does the close take now, and where does it get stuck?
Why ask it
The number sets your monthly rhythm and the bottleneck tells you what you would inherit: a late bank feed, a subsidiary that reports slowly, a manual consolidation. An interviewer who names the bottleneck precisely is usually working on it. One who says it varies has not measured it.
What are the hours like in a normal month, and in the busiest one?
Why ask it
Asking about both prevents the reassuring average. The honest answer usually contains one or two weeks that are much heavier than the rest. Follow up by asking what happened during the last one, since a specific account is harder to soften than a general policy.
When is your busy season, and what did the last one look like?
Why ask it
In practice this varies by employer, year-end close, audit fieldwork, tax deadlines, or a budget cycle. What you want is the calendar, so you can see whether it collides with anything in your own year, and whether the team was given extra help or simply worked longer.
Which systems would I be in every day?
Why ask it
Ask which ones you would use daily rather than which the company owns, since the two lists differ. It matters for your next job as well as this one, and you should ask whether any implementation or migration is planned, because that is a year of extra work either way.
How much of the work is still manual?
Why ask it
Manual exports, rekeying between systems, and reconciliations built by hand each month are the main reason finance roles overrun. Ask for an example of something done manually now, and whether anyone has been given time to fix it. The answer describes most of your working week.
Who reviews my work, and how does that review happen?
Why ask it
Real review, someone checking before it goes out, is how you learn and how you are protected. Ask who signs off and whether it happens under time pressure. If nothing is reviewed, that is worth knowing at any level and is a reason to insist on your own checks.
Who's on the team, and who would I work with most?
Why ask it
Ask for the structure and where the role sits in it. A team of two means broad exposure and no cover when someone is away; a team of thirty means depth in one area. Neither is better, but they suit different people, and the answer tells you which one you are being offered.
What state is the documentation in for the tasks I'd inherit?
Why ask it
Undocumented processes mean weeks of reverse engineering, particularly if the previous person has already left. Ask whether there are written procedures and whether you would overlap with the person leaving. This one question predicts the difficulty of your first quarter better than most.
What happened at the last external audit?
Why ask it
You are asking about workload and pressure as much as anything. Look for how long fieldwork took, whether requests were met on time, and whether the relationship is workable. A description of the audit as painful every year usually means the underlying records are the problem.
Were any control or process issues raised recently that this role would help fix?
Why ask it
A fair question that often gets a candid answer, because they need someone to fix them. It tells you whether the role is maintenance or repair. It also gives you something specific to point at later if you want to negotiate scope, title, or salary.
What's the one process here that everyone agrees is broken?
Why ask it
Asked lightly, this usually gets an honest answer, and the phrasing gives the interviewer permission to be frank. Whatever they name, ask who owns it and whether anyone has time allocated to it. If the answer is that the new hire will fix it, that is your first year.
Who does finance report to, and does anyone outside finance push back on the numbers?
Why ask it
Reporting lines determine whether finance can hold a position. Pressure to reclassify, defer, or accelerate items is a serious matter, and it is easier to ask about in the abstract now than to discover later. Note the reaction as much as the answer.
Do you support exam study: fees, paid study leave, and time off before exams?
Why ask it
Ask about all three separately, because reimbursement without study time is worth much less than it sounds. Also ask whether there is a repayment clause if you leave within a period, since that condition is common and rarely mentioned unprompted.
What has the last person in this role gone on to do?
Why ask it
More informative than asking about career paths in general, because it is a fact rather than an intention. An internal move upward is a good sign. A departure to a competitor at the same level suggests the progression described to you did not materialise.
Who's been promoted out of this team in the last two years?
Why ask it
Ask for names of roles, not a policy. Companies that promote internally can list examples immediately. If the answer is about how much they value development without a single case, treat the progression conversation as aspiration rather than a plan.
What would my first-year review be based on?
Why ask it
You want the measures written down: close timeliness, clean audit, a specific process improved, exam progress. Vague criteria mean you will be judged on impressions and availability, which in finance often means the person who stays latest looks the most committed.
What's the hardest part of this job that isn't in the description?
Why ask it
A good closing question because it invites a candid answer and interviewers usually give one: a difficult stakeholder, a system that fails monthly, chasing other departments for information. Whatever it is, it will be true on your first day, and it is the thing worth thinking about overnight.
Assessing a finance role before you accept
Practical guidance for the conversation itself
Do the reading first
Look at the numbers if they are public
For a listed company, the annual report tells you about growth, debt, any restatements, and who the auditors are. For a private one, filings in the relevant register still show size, filing timeliness, and any auditor changes. Late filings and a recent change of auditor are both worth asking about.
Read the job posting for scope creep
A single posting that covers payables, payroll, close, tax, and reporting usually describes work that was previously done by more than one person. Ask how it was covered before, and what has been given up.
Know which kind of employer you are talking to
A practice role brings chargeable hours, utilisation targets, and a defined busy season. An industry role brings a monthly cycle and closer contact with operations. The questions that matter differ, so decide which you are optimising for before you interview.
Write down your own limits
The hours you will accept in a peak month, the study support you need, the salary floor. Answers only become useful when you have something to compare them with.
Who can answer what
Ask each question of the person who can actually answer it:
- Recruiter or HR: salary range, benefits, exam support policy, flexible working arrangements, why the role is open.
- Hiring manager: the close calendar, your specific tasks, review arrangements, systems, the state of documentation.
- A peer at your level: hours during the last busy period, what is manual, whether review actually happens, what surprised them.
- The controller or finance director, if you meet them: audit history, control issues, reporting lines, plans for the function.
- Anyone: what the last person in the role went on to do. Compare the answers you get.
Mistakes candidates make
Asking about growth and skipping the workload
Career path questions are comfortable and vague. The close calendar, the hours in a peak month, and how much is manual will determine your experience of the job far more than the progression chart will.
Accepting a policy where you needed an example
Exam support, flexibility, and internal promotion all exist on paper in most companies. Ask who last used them and what happened, which is the only version that tells you anything.
Not asking about the previous person
It feels intrusive and it is the most useful factual question available. How long they stayed, and where they went, describes the role better than any answer about responsibilities.
Leaving the ethics question out
You carry professional and sometimes personal exposure for what you sign. Asking about reporting lines and pressure on the numbers is legitimate, and a defensive reaction to it is information.
Signals worth weighing
Nobody can describe the close calendar
In a functioning finance team this exists and people know their own deadlines. Its absence usually means the month ends in improvisation, and new joiners absorb the difference.
The role has turned over quickly before
Two departures in two years is a pattern rather than bad luck. Ask directly what changed after the last one, and whether anything was done differently.
A specific answer about what is broken
A positive signal. Teams that can name their weakest process, and say who is working on it, are usually reasonable places to work even when the work is hard.
Pressure in the process itself
An offer that requires an immediate answer, or resistance to letting you speak with a peer, tends to reflect how the department operates. Ask for the peer conversation and a reasonable window to decide.