Assistant Controller interview questions and how to answer them
An assistant controller interview is really a test of whether the controller can hand you the close and stop worrying about it. Expect technical questions about reconciliations, revenue and audits, but the people across the table are listening hardest for how you run a team and a process under deadline. Bring real examples from closes you've owned, including the ones that went badly.
What happens in each round
- 1
Recruiter or HR screen
What happens
Whether your background matches the company's size, ERP and audit situation, whether you hold or are working toward a CPA license, and whether your expectations fit the role.
- 2
Controller interview
What happens
How you'd run their close, how you review other people's work, and whether you can take problems off their desk. This is the round that decides it.
- 3
Technical round or case exercise
What happens
Your hands-on accounting: a reconciliation with a planted error, a revenue scenario, a flux analysis or a set of journal entries to review. Some companies send this as a take-home file in Excel.
- 4
Team and peer meetings
What happens
Whether the accounting managers and senior accountants you'd lead can work with you, and whether FP&A and operations people find you easy to deal with.
- 5
CFO or VP of finance conversation
What happens
Judgment, communication with leadership and whether you could grow into the controller seat later.
Questions you're likely to get
1.Walk me through how you'd run our month-end close.
Why they ask
This is the core of the job. They want to hear a process, not a list of tasks, and they want to know you'd ask about their setup before redesigning it.
How to answer
- Start by asking what the close looks like today, what the ERP is and where it slips
- Describe a close calendar built backward from the reporting deadline, with owners and due times for each task
- Explain how reconciliations get prepared, reviewed and signed off in a tool like BlackLine or FloQast
- Cover the flux review and how you get explanations from the business before the controller asks
- End with how you'd run a retrospective after each close to cut the slowest step
2.Tell me about the biggest audit adjustment you've dealt with.
Why they ask
Every assistant controller has had one. They're checking whether you own the mistake, understand the root cause and changed the control so it didn't happen again.
How to answer
- Name the account and what went wrong in plain terms
- Explain how the error got past review
- Describe how you worked with the auditors on the fix and the disclosure question
- Say what control or checklist step you added afterward
3.How do you review a reconciliation someone on your team prepared?
Why they ask
Review is most of what you'll do. They want to know if you actually look at support or just check that the balance ties.
How to answer
- Check that the balance ties to the general ledger and the prior month's reconciliation rolls forward
- Look at aged and unusual reconciling items first, since that's where problems hide
- Trace a sample of items to support, such as invoices, bank statements or contracts
- Leave written review notes and follow up until they're cleared, instead of fixing it yourself
4.A customer signs a contract with software, setup services and ongoing support. How would you think about revenue?
Why they ask
Revenue recognition is the area auditors push hardest on, and many assistant controllers write the memo for it.
How to answer
- Walk through the revenue model steps: contract, performance obligations, price, allocation, recognition
- Ask whether the setup is distinct or tied tightly to the software
- Explain allocating the price on standalone selling prices
- Describe recognizing support over time and the software at a point in time, if distinct
- Mention documenting the judgment in a memo the auditors can follow
5.What would you do if the close was going to miss its deadline?
Why they ask
Deadlines slip. They want to see whether you surface it early and make a trade-off, or hide it and hope.
How to answer
- Say you'd flag it to the controller as soon as you saw it, with a new date
- Explain how you'd decide what can be estimated and trued up later versus what has to be exact
- Describe moving people from low-risk tasks onto the blocking item
- Mention fixing the cause afterward so it doesn't repeat
6.How have you worked with external auditors?
Why they ask
You'll likely be the main contact for the audit team. They want someone who keeps the audit on schedule without giving away the store.
How to answer
- Describe running the request list with owners and due dates
- Explain how you prepare a PBC package ahead of fieldwork
- Talk about pushing back respectfully when a request goes beyond what's reasonable
- Give an example of resolving a disagreement over a judgment call
7.Tell me about a process you changed that shortened the close.
Why they ask
The controller is hiring you to make the close better, not just to keep it running. They want proof you've done it before.
How to answer
- Describe the old process and why it was slow
- Explain the change, such as automating a bank reconciliation, moving accruals earlier or adding a pre-close checklist
- Say how you got the team and other departments to adopt it
- Give the result in days saved or errors avoided
8.How would you approach SOX controls if we're preparing to go public?
Why they ask
Pre-IPO and newly public companies often hire assistant controllers to build controls from scratch.
How to answer
- Start with a risk assessment of the significant accounts and processes
- Describe documenting processes in narratives or flowcharts and identifying key controls
- Explain walkthroughs, testing and remediation of gaps
- Mention segregation of duties and system access reviews in the ERP
9.Tell me about someone on your team who wasn't performing.
Why they ask
You'll manage managers and senior staff. They want to know you'll deal with problems instead of quietly absorbing the work.
How to answer
- Describe the gap specifically, such as reconciliations coming in late or with errors
- Explain the direct conversation and the clear expectations you set
- Describe the support you gave, like training or pairing
- Share the outcome honestly, whether they improved or left
10.How do you explain a big variance to someone outside accounting?
Why they ask
You'll talk to department heads, FP&A and sometimes leadership. They're checking whether you can translate the books.
How to answer
- Lead with the answer: what moved and why, in business terms
- Separate timing differences from real changes in spend or revenue
- Keep the journal entry detail ready but don't open with it
- Say what they should do about it, if anything
11.Why do you want to be an assistant controller rather than stay an accounting manager?
Why they ask
They want to know you understand the step up and actually want the management and ownership that comes with it.
How to answer
- Say you want to own the full close and the audit, not just part of it
- Point to times you've already done pieces of the bigger job
- Show you know the trade: less time doing entries, more time reviewing and fixing process
- Connect it to where you want to be later, such as controller
Mistakes that sink good candidates
Talking only about entries you posted yourself, which makes you sound like a senior accountant rather than someone who runs a team
Criticizing your current controller or auditors in detail
Not knowing the basics of the revenue recognition model or lease accounting
Having no example of a process you actually improved
Need more Assistant Controller interviews to prep for?
HeroApply applies to Assistant Controller jobs that match you, every day. 120 jobs are open today.