Accountant Interview Questions

Not "tell me your life story." They want the through-line: what kind of accounting, at what scale, on what systems.

Three beats, ninety seconds. Where you are now and what you own. The one thing you've done that maps to this job. Why this role.

Skip your GPA unless you graduated last year.

The only wrong answer is a grievance. Not because they'll disagree — half the time they'll agree with you — but because the person interviewing you is imagining how you'll describe them in two years.

Say what you're moving toward. If you were laid off, say so plainly; in this market it carries no stigma and hedging does.

Give a range you've actually researched, with the bottom of it a number you'd sign. In several US states they have to give you theirs first if you ask — so ask.

If yes, say which parts you've passed and your timeline. If no, don't apologize — say what you're doing instead, and mean it. Plenty of controllers never sat the exam.

The real one.

They are testing your politics, not your eyesight.

The failure modes are equally bad. The candidate who describes marching into a colleague's cube and correcting them publicly will not get an offer at a company with a functioning team. The candidate who says they quietly fixed it and said nothing will not get one either, because silent corrections are how material misstatements survive.

What they want: you verified it first, you went to the person before you went above them, and it got documented.

"I'm a perfectionist" is not an answer, and neither is a mistake so small it's obviously chosen for safety. Pick something that cost real money or real time.

Three parts: how it was caught, what you did in the first hour, and what changed afterward. The third part is the entire question. If your answer ends with "I double-check now," you've said nothing — double-checking is not a control.

It's worth seeing the two versions side by side, because most candidates give the first one and think it went well.

An ethics question wearing plain clothes, and it comes up more in companies that have been through a rough audit.

Don't play the whistleblower who resigns on principle, and don't play the soldier who books whatever they're told. The mature answer: you asked for the rationale, you asked for it in writing, you escalated to whoever owned the decision, and you documented what you were told. "I asked him to put the instruction in an email" is a sentence controllers love, because it's what they'd have done.

Don't say you thrive under pressure. Describe the system: what you pre-close before the month ends, how you sequence days one through five, what you cut when the calendar slips.

Usually sales, usually about missing documentation, usually about revenue timing. Keep the resolution procedural. "We agreed on a cutoff and I built the reminder into the workflow" beats any story about winning an argument.

Name the real hierarchy: statutory and payroll obligations first, then anything that blocks another person, then everything else. Say out loud that you tell people early when something will slip. That last part is what they're checking.

An honesty test. Name something real and small — repetitive data entry is the standard answer for a reason — then say what you've automated to reduce it. "I love every part of it" is not believed by anyone.

The most-asked technical question in finance interviews, and people still just list the three.

The answer is the linkage. Net income from the income statement flows into retained earnings on the balance sheet and starts the cash flow statement. Depreciation is added back on the cash flow statement because it never left as cash. Ending cash on the cash flow statement is the cash line on the balance sheet.

If you can say that in thirty seconds without stumbling, you've cleared the bar most candidates trip on.

The classic follow-up to the three-statements question, and the reason to over-prepare that one.

Work it out loud, and state your tax assumption before you start — that's the part interviewers grade. Income statement: pre-tax income down 10, and at a 25% rate net income down 7.5. Cash flow: start at net income down 7.5, add back the full 10, so cash up 2.5. Balance sheet: PP&E down 10, cash up 2.5, retained earnings down 7.5, and it balances.

Slow is fine here. Confident and wrong is not.

Two sentences and one example. Rent incurred in December, paid in January: expensed in December under accrual, January under cash. Then the reason: matching revenue to the period that earned it.

An invoice you've received versus an expense you've incurred but not been billed for. Candidates blur these constantly.

A liability, and saying "liability" quickly is most of the answer. You've been paid and still owe the work. Expect a follow-up about how it unwinds.

These three are the same question in different clothes, and you'll usually get one, not all: payroll with withholdings, a credit sale with tax, and an accrued expense at period end. Prepare them together. The payroll one catches the most people, because employer-side taxes are a separate expense from the employee withholdings sitting in a liability account — get that split right and the rest follows.

Don't define reconciliation. Describe a search order.

Timing differences first — outstanding checks, deposits in transit. Then bank-side items you never booked: fees, interest, FX charges. Then transposition errors, which is why you check whether the difference divides evenly by nine. Then duplicates.

Tie it to future benefit and to the company's capitalization threshold — then say that the threshold is a policy that varies by company. That last clause signals you've worked somewhere real.

FIFO and weighted average are fine everywhere. LIFO is permitted under US GAAP and prohibited under IFRS (IAS 2). Knowing that split is the point of the question, and it's a fast way to show you know which framework you're actually working in.

ASC 606 in the US, IFRS 15 elsewhere, converged and five-stepped: identify the contract, the performance obligations, the transaction price, allocate it, recognize as obligations are satisfied. Name the five steps and give one example from a business you've worked in. If you've never dealt with multi-element contracts, say so.

Timing. The book and tax treatments diverge — usually depreciation — and you'll owe it later. Keep it short; if they want depth they'll ask.

Be precise and do not inflate. Name the system, the modules you actually touched, and for how long. Someone who claims SAP fluency and then can't name the transaction screen they lived in every day loses the room instantly.

If you only know one system, say so and describe how fast you picked it up, with an example. Controllers hire for that more often than for a specific package.

The second half is the actual question, and it ambushes people who just said "advanced."

Have one function ready that you used on a real task, and say what it solved. XLOOKUP, SUMIFS, INDEX/MATCH, a pivot that replaced a manual report — any of these are good if they're true. Many employers give a short Excel test; assume you'll get one.

Segregation of duties, approval thresholds, three-way match, reconciliation sign-offs. Give one you personally operated or built, and what it caught.

They want to see you go from a number to a cause to a conversation with a non-finance person. The cause is rarely accounting — it's usually an operational decision nobody told finance about.

PBC lists, schedules that tie to the trial balance, and being the person who answers within a day. If you've been through a first-year audit or a system migration during one, lead with it.