What auditor interviews actually test, beyond the CV chat

Who is actually in the room

For external audit roles at the Big Four or a mid-tier firm, you will usually meet an audit manager first, then a senior manager or partner if you get through. The manager is checking whether you can be put on a client next month without causing rework. The partner interview, when it happens, is shorter and more about judgement and client-facing risk than technique — they are asking themselves whether they would let you sit across the table from a finance director.

For internal audit roles, the panel is different. You will often meet the head of internal audit and, for more senior roles, a member of the audit committee. Internal audit interviews spend more time on stakeholder handling and independence than external audit ones do, because the internal auditor's problem is different: you have to raise findings with people you will still be working with next quarter.

For a first-time senior associate or newly qualified role, expect a competency interview built around your ACA, ACCA or CIMA training contract experience, plus a technical screen. For manager and above, expect a case study or a client scenario, because by that point the firm already assumes you can do the mechanics — they are testing whether you can run an engagement.

What the technical assessment looks like

The most common format is not a written test but a scenario walked through verbally: "You're auditing revenue for a SaaS business recognising income over a contract term. Walk me through your approach." They want to hear you move through risk identification, the relevant assertions (existence, completion, cut-off, accuracy), and how you'd design a test of detail or a control test to address the specific risk — not a recitation of ISA 315 from memory.

Some firms use an in-tray or case-study exercise before the interview: a set of extracts from a client's trial balance, a control narrative, and a request to identify the two or three areas you'd focus testing on and why, given a materiality figure. This is testing whether you can prioritise. A candidate who tries to test everything equally has told the interviewer they don't understand what materiality is for.

Materiality calculations come up often, and not as arithmetic. They'll give you turnover, profit before tax, and net assets, and ask which benchmark you'd use and why. The answer they want references the nature of the business and the users of the accounts, not a fixed percentage rule recited without context — although you should be able to state the rough ranges auditors commonly apply (a percentage of profit before tax is the usual anchor for a profit-making entity, adjusted down for public interest entities).

Expect at least one question on a control weakness or a fraud risk: "You find that the person who raises purchase orders also approves supplier payments. What do you do?" They are checking you know the difference between a control deficiency, a significant deficiency and a material weakness, and that you know what goes in the report to those charged with governance versus what gets fixed quietly with management.

If you're going for a role with a Public Interest Entity audit client, or anything under PCAOB or FRC oversight, expect a question that tests whether you understand independence and rotation rules in practice — not the theory, but what you'd actually do if you discovered a conflict partway through a job.

The questions that are really testing something

A few questions recur because they separate people who have done the work from people who have watched it being done.

"Tell me about a time you disagreed with a senior on a judgement." This is not really about conflict management. It's checking whether you have ever pushed back on a technical position — an accounting estimate, a going concern assessment, a provision — and whether you understood the accounting standard well enough to make the case, or just deferred. A candidate who says "I raised it and they were right so I dropped it" has answered a different, safer question than the one that was asked.

"How do you decide your sample size?" is a trap for people who learned the formula but never applied professional judgement to it. The interviewer wants to hear you talk about risk of material misstatement, tolerable error, and the population characteristics — not just "25 items for a large population," which is a rule of thumb some firms use as a starting point, not an answer in itself.

"Describe a control you tested that failed, and what you did next." This tests whether you understand the difference between a control failing in your test and a control being ineffective for the business — and whether you know to extend testing, consider compensating controls, and think about the knock-on effect on your substantive strategy, rather than just flagging it and moving on.

For internal audit specifically: "How would you handle a finding that the finance director disagrees with?" This is testing independence in substance. They want to know you'd stand behind the evidence and escalate through the audit committee if needed, not soften the finding to keep the relationship comfortable.

A question that's increasingly common at manager level: "How are you using data analytics or exception testing in your audits?" Firms want to know whether you can run or interpret a full population test rather than relying purely on sample-based testing, and whether you understand what the tool is actually flagging rather than just accepting its output.

What a shallow answer sounds like

To someone who does this job, a shallow answer has a particular shape: it's correct in the abstract and empty in the specific.

Asked about materiality, a shallow answer states the percentage range and stops. It doesn't say what benchmark was chosen and why, doesn't mention performance materiality, and doesn't connect it to what testing that materiality level actually drove.

Asked about a disagreement with a senior, a shallow answer describes the disagreement but not the standard or the reasoning — "I thought the provision was too low" without saying which IAS or FRS governed it, what the recognition criteria were, or what evidence changed the outcome.

Asked to walk through an audit approach, a shallow answer lists procedures without linking them to risk: "I'd do a substantive analytical review, test a sample, and check cut-off," recited in the order they were taught rather than in response to what's actually risky about this client's revenue stream this year.

Asked about a control failure, a shallow answer says "I told my manager and we increased the sample," with no mention of why the sample increased, what threshold triggered it, or whether the deficiency needed reporting upward.

Interviewers on the other side of the table have sat through hundreds of these. The tell isn't wrong technical knowledge — most candidates know the standards. The tell is an answer that could have been given by someone who read the file afterwards rather than someone who was in the room deciding what to test.

What to do with this before the interview

Go through your last two or three engagements and, for each, write down one judgement call you made or influenced — not a task you completed, a decision. What was the risk, what did you decide, and what would have happened if you'd decided differently. That's your answer bank for the disagreement and control-failure questions, and it's specific in a way that general preparation isn't.

If the role sits under a regulatory regime you haven't worked in before — moving from FRC-regulated UK audit to PCAOB-inspected US-listed clients, for instance — read the actual scope difference before the interview, not a summary of it. Interviewers notice when a candidate has only read that something exists.

If you're short on time to prepare for a specific advert because you're sending out a lot of applications and getting little back, jobmarket.pro reads the advert in full, matches it against your actual audit experience, and tells you where the gap really is before you walk in.