An accountant or auditor interview usually runs in three layers. First, technical grounding: how you build and review financial statements, prepare adjusting journal entries, reconcile accounts, apply accrual concepts, and judge materiality. Second, control and compliance thinking: how you scope an audit, test whether transactions are recorded under accepted accounting procedures, spot deficient controls, duplicated effort, extravagance, or fraud, and evaluate financial and information systems for data integrity. Third, communication: how you write audit findings, report asset utilization results to management, and confer with company officials who may not welcome your conclusions.
Prepare by rehearsing specific engagements or close cycles you have owned. Know the numbers you touched, the systems you used, the reconciling items you chased, and what changed after your recommendation. Be ready to walk through a bank reconciliation, an accrual versus prepaid decision, and a revenue cut-off test out loud. Have one story about a discrepancy you traced to root cause and one about pushing back on a supervisor or client. Refresh the reporting framework relevant to the employer (public company reporting, governmental, or private company standards) and the regulations that govern their industry. Expect a spreadsheet or case exercise: a trial balance with planted errors, or a set of documents to test against a control.
1. Walk me through how you would reconcile an account where the subledger and general ledger disagree by a material amount.
What they're testing
Systematic reconciliation method and comfort tracing differences to source documents.
A strong answer
Describe confirming the balances and cut-off dates first, then isolating the difference by timing items, unposted entries, duplicated postings, and manual journal entries hitting the control account. Explain narrowing by period or transaction type rather than scanning line by line, then documenting the reconciling items and clearing them with an adjusting journal entry. Close with how you would prevent recurrence, such as restricting direct postings to the control account.
Common failure mode: Naming tools instead of a method, or declaring the difference immaterial without testing whether offsetting errors are hiding inside it.
Likely follow-up: What if the difference nets to zero but is made of two large opposite errors?
2. Tell me about a time you found an error or discrepancy that others had missed.
What they're testing
Monitoring, professional skepticism, and follow-through.
A strong answer
Give the context, what triggered your suspicion (an unusual fluctuation, a stale reconciling item, a vendor that did not fit), the steps you took to confirm it, and the correcting entry or control change that resulted. Quantify the impact in relative terms and say who you told and when.
Common failure mode: A vague 'I catch mistakes because I'm detail-oriented' answer with no traceable investigation or outcome.
Likely follow-up: How did the person who made the error respond?
3. How do you determine the scope of an audit or review before you start fieldwork?
What they're testing
Risk-based planning and judgment about where to spend effort.
A strong answer
Explain starting from objectives and risk: prior findings, changes in systems or personnel, transaction volume and value, regulatory exposure, and areas with weak segregation of duties. Describe setting materiality, choosing which cycles to test, and deciding sample sizes and whether to rely on controls or go substantive. Mention documenting the scope so it can be defended and adjusted if fieldwork turns up surprises.
Common failure mode: Describing a fixed checklist applied identically to every engagement, with no risk assessment.
Likely follow-up: What would make you expand scope mid-engagement?
Reading answers isn't rehearsing them.
Run these exact questions with a voice AI interviewer and get scored on your real answers — the first five minutes are free.
4. Describe your role in a month-end or year-end close. What did you own?
What they're testing
Practical ownership of the close cycle and understanding of dependencies.
A strong answer
Lay out the sequence: cut-off, accruals and prepaid amortization, intercompany, reconciliations, adjusting journal entries, review of the trial balance for unusual variances, and statement preparation. State clearly which pieces you prepared versus reviewed, and how you kept the close on schedule when a dependency slipped.
Common failure mode: Overclaiming ownership of the whole close, then failing on specifics when probed.
Likely follow-up: What was the longest pole in your close and how did you shorten it?
5. How do you decide whether a cost should be expensed or capitalized?
What they're testing
Core technical accounting judgment and ability to reason from principles.
A strong answer
Frame it around future economic benefit beyond the current period, the entity's capitalization threshold and policy, and whether the spend extends useful life or merely maintains it. Give a real example you handled, including how you documented the conclusion and what the auditors or reviewers asked about it.
Common failure mode: Answering only with the dollar threshold and skipping the substance of the transaction.
Likely follow-up: How would you treat internally developed software costs?
6. Walk me through the adjusting journal entries you prepare most often and why each is needed.
What they're testing
Fluency with accrual accounting mechanics.
A strong answer
Name the recurring categories: accrued expenses and revenue, prepaid amortization, depreciation, allowances for uncollectible accounts, inventory adjustments, and reclassifications. For two or three, state the debit, the credit, and the reason the entry exists. Explain your support documentation and review trail for each.
Common failure mode: Reciting entries without saying which account is debited and credited, or without the business reason.
Likely follow-up: How do you support an estimate-based accrual?
7. You are examining records and the pattern of transactions suggests possible fraud. What do you do next?
What they're testing
Judgment, escalation discipline, and awareness that fraud handling differs from error handling.
A strong answer
Say you would preserve evidence and stop discussing it with the people who could be involved. Describe quietly extending testing to confirm the pattern, documenting facts rather than conclusions, then escalating through the defined channel, typically above the level of the suspected party, to audit leadership, the audit committee, or legal. Emphasize you do not confront the individual or announce a conclusion prematurely.
Common failure mode: Saying they would interview the suspected employee directly or report a firm accusation before the evidence supports it.
Likely follow-up: What if the person you suspect is the one you report to?
8. How do you evaluate whether a client's internal controls are actually working, not just documented?
What they're testing
Ability to distinguish control design from operating effectiveness.
A strong answer
Describe walking a transaction end to end, inspecting evidence of the control being performed, testing a sample across the period rather than a single date, and interviewing the people who perform the control to see whether their description matches the policy. Note that you look for compensating controls and for whether exceptions were investigated when the control flagged something.
Common failure mode: Confusing existence of a written policy with evidence that the control operates, or relying entirely on management's assertion.
Likely follow-up: What is your response when a key control fails your test?
9. Tell me about a time you had to report unfavorable audit findings to management or a company official.
What they're testing
Speaking skill under pressure and ability to stay factual with a resistant audience.
A strong answer
Describe preparing by nailing down the facts, quantifying impact, and drafting a recommendation before the meeting. Explain how you led with the finding and its business consequence rather than the technical rule, gave the other side room to respond, and separated confirmed facts from open questions. End with what management agreed to and whether the change stuck.
Common failure mode: Framing the story as winning an argument, or softening the finding so much it disappeared.
Likely follow-up: What did you do when they disputed your facts?
10. What makes an audit finding report useful to the reader?
What they're testing
Writing skill and understanding of audience.
A strong answer
Explain the standard structure: condition, criteria, cause, effect, and recommendation. Emphasize stating the criteria you tested against, quantifying the effect, naming an owner and a date for the remediation, and writing so an operations manager understands what to change. Mention keeping working paper detail out of the executive summary.
Common failure mode: Describing long narrative reports full of technical citations that leave no clear action.
Likely follow-up: How do you handle a finding management refuses to accept?
11. How do you inspect cash, notes receivable and payable, or negotiable securities to confirm records are accurate?
What they're testing
Substantive testing knowledge on high-risk balance sheet accounts.
A strong answer
Describe independent confirmation with third parties, agreeing balances to bank statements and reconciliations, inspecting the reconciling items for old or unusual entries, verifying cut-off around period end, and physically inspecting or confirming custody of securities. Note checking for restricted balances, kiting indicators, and unrecorded liabilities on the payable side.
Common failure mode: Only mentioning tying to the bank statement, with no consideration of cut-off, confirmations, or old reconciling items.
Likely follow-up: What does a large stale reconciling item tell you?
12. Describe how you have used accounting systems, ERP, or spreadsheets to analyze large volumes of transaction data.
What they're testing
Working with computers and ability to move beyond manual review.
A strong answer
Name the classes of tools you have used and the specific analysis: extracting the full ledger, running duplicate payment tests, aging analyses, gap and sequence testing, or filtering entries posted on weekends or by unusual users. Explain how you validated that your extract was complete before drawing conclusions.
Common failure mode: Listing software names without describing an analysis or without confirming data completeness.
Likely follow-up: How do you prove your data extract is complete and accurate?
13. A supervisor asks you to record an entry you believe is not supportable. How do you handle it?
What they're testing
Ethics, judgment, and escalation without burning the relationship.
A strong answer
Start by assuming you may be missing information and asking for the support and rationale. If the support is not there, state your concern in terms of the standard and the risk, propose an alternative treatment, and put your position in writing. If it still stands, escalate through the defined chain — controller, CFO, internal audit, or audit committee. Note you would not book it silently.
Common failure mode: Either instant refusal with no fact-finding, or agreeing to book it and 'flagging it later.'
Likely follow-up: What if the amount was small?
14. How do you decide what is material?
What they're testing
Judgment beyond mechanical thresholds.
A strong answer
Explain the quantitative benchmark relative to the entity's key measure, then the qualitative factors: whether the item changes a trend, affects a covenant or a bonus, involves fraud or an illegal act, or moves a result across a threshold. Give an example where a numerically small item was material for a qualitative reason.
Common failure mode: Giving only a numeric rule of thumb and never mentioning qualitative materiality.
Likely follow-up: Would you adjust for an immaterial error found late in the engagement?
15. Tell me about a recommendation you made to management that changed how they operated.
What they're testing
Whether the candidate's work produces action, not just documentation.
A strong answer
Describe the deficiency you observed — a duplicated effort, a weak approval step, an underutilized asset — the analysis behind your recommendation, and how you sold it in business terms. State what management implemented and how you verified it later.
Common failure mode: Stopping at 'I recommended it' with no evidence of adoption or follow-up testing.
Likely follow-up: How did you follow up to confirm implementation?
16. How do you handle interviewing employees as part of examining records for compliance?
What they're testing
Active listening and interpersonal handling of a process people find threatening.
A strong answer
Explain opening with the purpose and scope so people are not defensive, asking open questions about what they actually do rather than what the policy says, walking a real transaction with them, and then corroborating what they said against documents. Mention documenting the conversation promptly and confirming your understanding back to them.
Common failure mode: Treating interviews as interrogation, or accepting statements without corroborating evidence.
Likely follow-up: What do you do when someone's description contradicts the documented procedure?
17. How do you stay current on accounting standards and regulations relevant to the entities you work with?
What they're testing
Reading comprehension, self-direction, and knowledge of the applicable framework.
A strong answer
Name the standard-setting and regulatory sources you actually read, the industry-specific rules that apply, your CPE approach, and a recent standard or rule change you had to implement. Describe how you translated it into a policy or process change rather than just reading about it.
Common failure mode: Naming a newsletter subscription with no example of applying a change in practice.
Likely follow-up: Walk me through a recent standard change and how it affected your work.
18. You are supervising a junior on an engagement whose workpapers do not support the conclusion. What do you do?
What they're testing
Review discipline and people development.
A strong answer
Describe reviewing against the test objective rather than for tidiness, giving specific review notes about what evidence is missing, and coaching on the reasoning gap rather than fixing it yourself. Explain you would reperform enough to know whether the conclusion is wrong or only undersupported, and adjust supervision on the rest of their sections.
Common failure mode: Silently redoing the work, which hides a competence gap and creates an unreviewable file.
Likely follow-up: How do you keep a review from becoming demoralizing?
19. Walk me through how you would review a set of financial statements you did not prepare.
What they're testing
Analytical review skill and knowing where errors hide.
A strong answer
Describe tying the statements to the trial balance, checking that the statements cross-foot and articulate (net income to equity, cash flow to the balance sheet change in cash), running period-over-period and ratio analytics to find unexplained swings, testing the largest and the estimate-driven balances, and reading the disclosures against the underlying numbers.
Common failure mode: Checking arithmetic and formatting only, without analytics or disclosure review.
Likely follow-up: Which line item do you scrutinize first, and why?
20. How do you manage competing deadlines when close, an audit request list, and a management question all land in the same week?
What they're testing
Prioritization under real workload pressure.
A strong answer
Explain sorting by hard external deadlines versus internal ones, identifying which items block others, negotiating explicit dates rather than going silent, and delegating or batching the routine items. Give a concrete example including what you renegotiated and how you communicated it before the deadline slipped.
Common failure mode: Saying they just work longer hours, with no triage or communication.
Likely follow-up: What did you drop, and who did you tell?
21. Why this role, and what kind of accounting or audit work do you want to be doing?
What they're testing
Motivation and fit with the specific position — public versus industry, audit versus reporting, size of team.
A strong answer
Connect the work you have enjoyed to the concrete duties in this posting: the reporting framework, the industry's regulations, the systems, the mix of preparation versus examination. Be honest about what you want more of and what you want less of, and show you understand what this employer's close cycle or engagement calendar actually looks like.
Common failure mode: A generic answer about liking numbers, or one that describes a different job than the one posted.
Likely follow-up: What part of this job do you expect to like least?