Controller interview questions from someone who ran a close

Explore the Finance interviews hub and the finance careers guide.

Every controller interview question circles one test. Pick any number off the balance sheet. Can you walk it back to where it came from, the same way, every time?

I've run the month-end close, posted the entries myself and walked the auditors through them. The questions sound like accounting. They get scored on whether your close would still work on a day you're not in the room. (The rest of our finance interview guides work the same way.)

What is a controller interview really testing?

It's testing whether your numbers can be reproduced by someone who isn't you.

The U.S. Bureau of Labor Statistics says controllers direct the preparation of financial reports that summarize and forecast an organization's financial position. That's the job on paper.

In the room it comes down to a rule I gave my own AI workflows: AI never becomes the source of a number, and every number gets reconciled back to the data source.

Swap "AI" for "the person who posted it" and you have the controller's job, where the source is the invoice, the bank statement or the contract, never the ledger.

"Walk me through your month-end close"

Give them the calendar, then the one account you watch.

In one role I ran the monthly, quarterly and annual close across about four legal entities, and I posted most of the entries myself: deferred revenue and manual revenue recognition, expense accruals, the allowance for doubtful accounts and commission reconciliations.

Then sort the numbers in two: exact, like cash, and estimates by design, like an accrual for a bill that hasn't arrived yet.

One estimate I worked on was an incentive accrual, recalculated from the company scorecard at every forecast refresh. It went into public books, so we avoided true-ups as much as we could. If results were coming in really strong, we couldn't keep accruing at 100 percent.

Name one estimate you owned, and say how you kept the true-up small.

Finish with the account you watch closest. In a subscription business that's usually deferred revenue, where a small timing mistake compounds for months.

My worst reconciliation lived there: deferred revenue out of a billing system, close to 100,000 line items a month, with manual journal entries buried in them. I had to sort manual from automated billing from FX. I reconcile with sums and comparisons, pushing the difference as close to zero as I can. It kept going down, then three big journal entries took it almost to zero, and I knew those were the ones. I only knew to look for them because I'd been in the process when they happened.

"What do you do when something doesn't reconcile?"

They're checking whether one break stops your whole close.

My rule for any batch of work is short. Record the snag and move on, finish everything that isn't blocked, then come back to the snags together.

My own log came from a forecast deadline, when everything had to reconcile by morning. I kept a list of the manual adjustments, each with a note, and a before-and-after reconciliation back to the reported numbers, so the next person in line couldn't count the same adjustment twice.

A controller keeps the same list for top-side entries, with the reason and the effect of each. Say you keep one.

Then tell them about the break that took longer than a close.

Mine was a deferred revenue balance across four legal entities and two billing systems. I traced the history back, worked out the correct accounting and the fixing entry, and wrote the conclusion down. Anything that touched external reporting went up to the senior accounting team with the write-up.

A controller doesn't quietly fix a reporting problem. They document it and escalate it, even when the fix is already posted.

"How do you work with the auditors?"

Show them you can walk someone through the flow, with the files as backup.

I prepared the audit evidence myself and walked external and internal audit through the whole path, billing system to ledger to reporting, with the reconciliations, controls and accounting treatment at each step.

The files answer "what". The walkthrough answers "how", and that's what ends the back and forth.

I learned that early. An auditor asked me for evidence of why an invoice had been written off, out of my allowance for doubtful accounts entries. I'd been running that process without understanding what auditors look at, so I fumbled my way toward an answer. I opened a file to look for the invoice, and she spotted it first: "Oh okay, there it is. Okay, I understand your process, we're good."

Know the mechanics, and know the downstream effects: who else reads your files, and what they look for. It's the same lesson as the process I simplified too far.

A good walkthrough has three things.

• The flow in plain words, where a transaction starts and every system it touches.
• The control at each handoff, who checks what, and how you'd know if it failed.
• The judgment calls, like a revenue treatment, written down with the reason.

"How do you strengthen internal controls?"

They're checking whether the same break shows up again next month.

You can fix this month's number, or you can change the process that produced it. Only the second is the controller's job.

Every break you log is a hint about where the process is weak, and a break you've logged three times is a design brief.

Earlier in my career I taught myself enough to build a reconciliation sheet for each business unit, fed straight from the data warehouse, so every unit could tie out its planning inputs without a fight. It got adopted across the organization.

One control I put in had nothing to do with a recurring break. A mistake on that one transaction would have been catastrophic. It was payments to a joint venture partner, and the rule was: no payment goes out until accounts receivable has marked the customer's payment collected. I didn't care that we'd billed them, or that they'd said they'd pay on time.

I've asked for the same kind of gate on the AI agents that send email for me: a hard block without an approval, a record of who approved what and when, and one action per approval. Authorization, an audit trail and single use are what a panel means when they ask about manual journal entries. If you've built a control like that anywhere, name it.

If they ask about SOX or ICFR, name a control you owned, what it checked and how you evidenced it. The PCAOB's auditing standard on internal control over financial reporting has the audit side of the language.

"How would you use automation or AI in the close?"

They're checking whether you'd automate a mess.

I used to think a tool could rescue a rough process. When I first set up AI workflows, I took a rough concept, threw AI at it, and hoped that because AI was there it would figure everything out.

It didn't. What came out was generic stuff that was fine, and I kept spending more time babysitting it and fixing what it produced.

So now the process comes first: rethink it from the beginning, rebuild it step by step, then hand it to the tool and check every run.

Say what you'd standardize before you'd automate anything. Then say the rule out loud: the tool never becomes the source of a number, and a person still signs.

"How do you balance reviewing and signing off with doing the close yourself?"

They're checking whether the close depends on you being there.

I managed two analysts, which meant assigning the work, reviewing their output and holding the deadlines. Say the same about your team, and where your review hours go. Revenue, accruals and anything new deserve them more than re-ticking someone's math.

Then tell them about a handover, and what went wrong. Mine came when accounting got centralized into a shared team, and I was the guinea pig. I trained that team on the entire close, and one person on all of my journal entries.

The hardest part to explain was the history and nuance, what I call silly history: I know this doesn't make sense when I say it out loud, but this is just the way it is.

The next two closes were my worst. It was about a five-day close with most entries due on day four or five, and midway through day five I'd hear that an entry couldn't be done. Could I do it? If I'd known on day one, I could have finished every entry by day three and gone about my day.

Then, midway through a close, that person was let go and everything came back to me. I did it as a favor, but it was my business unit and the entries had to be in, so I had no real choice.

Training isn't the handover. The handover is done when the work stops coming back, so on day one of each close, ask for the list of what the new person can't do yet.

A close you can teach is a close that's written down, silly history included. A close that lives in your head is a risk the company is carrying for you.

"Won't you get bored in this role?"

Answer it with the part of the work you'd still want in ten years.

This one comes up when your résumé looks bigger than the seat.

When I weigh an option, I ask one question. If you asked me in ten years, would I still want to be doing this work? The actual work, week to week, whatever the title says.

If the answer is yes, say why, and name the work. Mine is a new process: put a system together, put controls around it, and make sure the system and the controls hold.

If you're still weighing the seat, the controller career guide covers the job day to day.

Technical controller interview questions

A panel usually tests the accounting directly, so answer short, then stop.

• Accrual versus deferral. An accrual records revenue or expense before the cash moves. A deferral records the cash before the revenue or expense is earned. Give one example of each from a real close.
• Revenue recognition. Identify the contract, find the performance obligations, set the price, allocate it, and recognize revenue as each obligation is met. IFRS 15 and ASC 606 follow the same model.
• Flux analysis. Compare each line to last month and last year. Set a threshold, and explain every move above it before anyone asks.
• Allowance for doubtful accounts. Start from the aging, apply loss rates by bucket, then adjust for anything you know about specific customers.
• Intercompany. Match balances between entities before consolidation, eliminate them, and chase any mismatch before close.
• Materiality. The audit threshold is one answer. The better answer is the size of mistake that would change a decision. My analyst brain still wants every threshold at zero, but a variance that's a red flag in a small business is noise in one hundreds of times bigger. I'm still working out where that line sits.
• Cutoff. Recording each transaction in the right period. It matters most at quarter end, when a few days of revenue changes the story.

Are financial controller interview questions different?

Not by much, since the title changes by country and company size more than the job does.

The difference is scope. A smaller company adds tax filings, cash and banking. A larger one adds consolidation, the team and reporting deadlines.

An assistant controller interview leans toward doing the work. A corporate controller interview leans toward review, policy and the auditors.

If you're coming from FP&A, expect the doubt I got, when a recruiter worried my role didn't show much technical accounting and I was pretty sure I could pull it from the memos we'd written. People who know me well have always told me I sell myself short. So have one technical accounting example ready: the issue, the memo and the treatment you landed on.

What should you ask a controller in an interview?

Ask about their close, since it shows you're already picturing the work.

• How many days the close takes today, and where they'd like it to be.
• What the last audit flagged, and whether it's fixed.
• Which reconciliations this seat owns, and which it reviews.
• What's still done by hand that they'd like gone.
• Whether the seat is replacing someone or new, and if it's new, what broke.

The audit question is the one I'd never skip. Their answer tells you what your first 90 days will be about (build your 30-60-90 day plan around it).

How do you prepare for a controller interview?

Write your answers down, then say them out loud until they sound like you.

I work better with a script. Some people find that stiff, but once the words are on the page I can stop thinking about them and just talk.

The reps matter more than the reading. I wasn't a natural at high school biology, so I built a stack of flash cards, ran the system over and over, and biology came out as one of my higher grades.

If you're coming from the analyst or FP&A side, the FP&A interview questions guide and the financial analyst interview guide cover the questions that overlap.

Show them the way back to the source.