Accounting Interview Questions to Ask Candidates
These are accounting interview questions to ask candidates, written for whoever is doing the hiring: a controller, a finance manager, or an owner filling a first finance role and unsure what questions to ask an accounting interviewee at all. The 69 questions are grouped as openers, technical knowledge, the close and systems, accuracy and controls, reporting and judgment, and fit. Most ask about work the person has done, such as the last close they worked on, a reconciliation that would not balance, or an error that got past them, and the notes say what a strong or a weak answer sounds like. Eleven are written for accounting clerk candidates, on invoices, supplier statements, petty cash and data entry, and the guide lists which.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Openers
Why did you choose accounting, and which part of the work do you like most?
Why ask it
An easy start that still sorts people. The part they like most, whether that is making a ledger tie, finding out why a number moved or advising whoever spends the money, should resemble the job you are filling. If it does not, say what the role is mostly made of and watch the reaction.
Walk me through the last month-end close you worked on. Which parts were yours?
Why ask it
Someone who has done the work describes it in order and names their own tasks without being asked. Notice a switch from I to we when you press on a specific step, and ask about anything the account skips, such as accruals or intercompany balances.
Which accounting software have you worked in, and which did you set up or administer rather than just use?
Why ask it
The second half is the one that matters. Someone who has built a chart of accounts, run an implementation or managed user permissions can tell you what went wrong along the way. A list of product names with no detail behind any of them usually means they entered data in a system someone else ran.
Tell me about a reconciliation that wouldn't balance. How did you find the problem?
Why ask it
Hard to bluff, because the method either exists or it does not. Listen for a structured search: checking the totals both ways, narrowing the difference to a period, looking for a transposed figure or a duplicated entry, testing whether the difference matches a known amount. Saying they kept at it until it turned up is not a method.
How do you check your own work when nobody else reviews it?
Why ask it
In a small finance team this is most days, and it is a different skill from working under review. Good answers include comparing figures with prior periods, leaving a gap before rereading, and tying totals to an independent source such as a bank statement. Saying they are simply careful means they have not thought about it.
Which areas did you handle in your last role: payables, receivables, payroll, the general ledger, reporting, tax? Which were yours alone?
Why ask it
A title like staff accountant covers very different jobs from one company to the next, so map the ground before going deeper. Mark the areas they owned alone and spend your technical questions there. An area they only assisted on tends to run dry by the second follow-up.
Which industries have you worked in, and what was different about the accounting in each?
Why ask it
Sector changes the work more than a resume shows: a builder's books turn on job costing, a subscription business's on deferred revenue, a nonprofit's on restricted funds. Ask what caught them out when they moved from one to another. If your industry would be new to them, name the part that is unusual and see what they ask about it.
If you have worked as an accounting clerk, which tasks filled most of your week, and which came round only at month end?
Why ask it
In one office an accounting clerk opens the post and keys invoices; in another the same title runs the whole payables cycle. The weekly tasks are the ones they can do on day one, and the month-end ones show how close they have been to the ledger. Say how your own split differs and note what they ask about it.
Technical
How do the income statement, the balance sheet and the cash flow statement connect to one another?
Why ask it
The standard technical opener at any level. A sound answer follows profit into retained earnings, shows closing cash on the cash flow statement agreeing with cash on the balance sheet, and explains that movements in working capital are one reason profit and cash differ. Reciting what each statement contains without linking them is a textbook answer, so push once.
We buy a machine and pay cash. What changes on each statement this year and next?
Why ask it
A transaction shows more than a definition does. On the day, cash falls and fixed assets rise, with nothing in profit; after that the cost reaches the income statement a slice at a time as depreciation, which is added back in operating cash flow. If a candidate expenses the whole purchase at once, ask how they decide what belongs on the balance sheet.
How do you decide whether a cost is capitalized or expensed?
Why ask it
Listen for a threshold set by policy, a test of whether the spending brings benefit beyond the current period, and an example where the call was not obvious, such as a repair that extends an asset's life or software built in-house. Thresholds differ between companies, so the reasoning matters more than the figure they quote.
What is the difference between cash and accrual accounting, and have you kept books on both?
Why ask it
Basic for a qualified accountant and a fair screen for a bookkeeper or a junior. Beyond the definition you want an example: an invoice dated after the work was done, a bill paid in advance. If your own books are kept on a cash basis, say so here and ask whether that is familiar ground.
Tell me about an accrual or a prepaid expense you booked recently. What were the entries, and how did it unwind?
Why ask it
This gets you the debit and the credit without turning the interview into a quiz. Someone who books these monthly gives the accounts, the basis for the estimate and the reversal without pausing. Hesitation over which side the expense sits on suggests the entries were prepared by someone else or by the system.
A customer pays in January for twelve months of service. How do you record it, and what happens each month after that?
Why ask it
Deferred revenue in one concrete case: the cash is a liability on receipt and moves into revenue as the service is delivered. A good candidate then asks you something back, such as whether the customer can cancel, whether there is a setup fee, or whether anything is delivered up front. Count those questions in their favor, because recognizing revenue on a real contract starts with asking them.
What is the difference between accounts payable and accounts receivable, and which have you run day to day?
Why ask it
For a clerk or a first accounting job this is close to the whole interview, and for a senior candidate you can skip it. Past the definition, ask about the work itself: matching an invoice to an order and a receipt, running a payment batch, chasing an overdue customer, clearing unapplied cash.
An invoice lands in your tray with no purchase order number and no name on it. What happens before you enter it?
Why ask it
This is the daily judgment in a payables seat. A careful clerk finds out who ordered it and whether the goods or the service turned up, and knows who is allowed to approve it, before anything reaches the ledger. Entering it now and sorting it out later is how unapproved bills get paid.
A supplier's statement lists three invoices you have no record of. How do you sort that out?
Why ask it
Checking statements is unglamorous and catches a great deal: invoices sent to the wrong person, credits never issued, payments set against the wrong bill. Listen for asking the supplier for copies, finding out whether they are sitting unapproved on someone's desk, and telling the accountant before month end in case the cost needs accruing.
A customer phones to say they have already paid an invoice your records show as open. What do you check, and what do you tell them?
Why ask it
The receivables counterpart, and a test of manner as much as method. The checks are unapplied cash, a payment posted to another customer or another invoice, and a remittance that never arrived. On the phone you want someone who takes the payment date and reference and promises a call back, neither arguing nor conceding.
Have you looked after petty cash, bank deposits or a company card log? How was it counted, and who checked your count?
Why ask it
Small sums are where trust gets tested first. Someone who has kept a float can describe counting it against the vouchers, having a second person sign the count, and what happened the day it was short. If they have never handled cash, describe how yours works and ask what they would want in place before taking it on.
An employee hands in an expense claim with a receipt missing and one item that looks personal. What do you do?
Why ask it
A clerk usually has to raise this with someone senior to them, which is the hard part. Good answers lean on the written policy, send the claim back with the gap named, and pass anything doubtful to the approver instead of deciding it alone. Then ask how they would handle the same claim from a director.
The trial balance balances. What could still be wrong with the books?
Why ask it
A balanced ledger proves less than it seems to, and this shows whether they know it. Expect an entry posted to the wrong account, one left out entirely, one posted twice, a correct entry in the wrong period, or two errors that cancel. Anyone who says nothing could be wrong has been letting the system do their thinking.
What is working capital, and where would you look first if ours suddenly tightened?
Why ask it
The definition takes ten seconds: current assets less current liabilities. The second half is the real question. Listen for receivables aging, inventory building up, payment terms that changed on either side, and a check on whether one customer or one supplier explains most of the movement.
Have you accounted for inventory? Which costing method was used, and how were the counts tied back to the ledger?
Why ask it
Skip it if you carry no inventory. If you do, listen for the mechanics: what the costing method did to cost of sales when prices moved, how count differences were investigated before they were booked, who decided to write down slow or damaged items. Which methods are allowed depends on the reporting framework, so ask which one they were working under.
How have you estimated an allowance for doubtful accounts, and how did you test that the figure was reasonable?
Why ask it
Estimates are where accounting stops being arithmetic. A solid answer covers an aging analysis, a look at specific accounts in trouble, and a comparison of last year's allowance with what was eventually written off. Ask who challenged the figure, because an estimate nobody questions can drift toward whatever suits the result.
Which reporting standards have you worked under, and where did the framework change what you did?
Why ask it
US GAAP, IFRS and local standards differ in ways that matter a great deal for some roles and hardly at all for others, so ask for a case and not a list: leases, revenue, inventory costing, consolidation. If your framework would be new to them, ask how they would get up to speed and who would check their first few calls.
Which taxes have you prepared or filed yourself: sales tax or VAT, payroll taxes, income tax?
Why ask it
Tax experience is easy to overstate, since plenty of accountants have sat near a return without preparing one. Ask what they filed, how often, and what happened the time a filing was late or queried. The rules differ by country and state, so if they trained elsewhere, ask how they would learn yours and what they would pass to an adviser.
Close and systems
How long did your last close take, and what made it slow?
Why ask it
The number tells you the scale they are used to; the reason tells you how they think. Strong answers name a specific bottleneck: a bank feed that lagged, a subsidiary that reported late, a journal keyed by hand. Answering that it always just took that long suggests they have never questioned the process.
How many entities, bank accounts and journals did you handle in a typical month?
Why ask it
Volume changes the job. Twenty journals a month and two bank accounts allow habits that collapse at two thousand journals and six entities, and the reverse move can leave someone bored. Compare their numbers with yours out loud and ask what they think would have to change.
Which reconciliations were yours each month, and what did you do with items that stayed open?
Why ask it
Old reconciling items are where problems hide, so the second half matters more than the list. Listen for a rule on how long an item may sit, who approves a write-off, and whether anyone besides the preparer read the schedule. Carrying the same unexplained difference forward every month is a habit you do not want to import.
What's the most complex spreadsheet you've built, and what did it do?
Why ask it
A lot of finance work still runs on spreadsheets, so treat this as a skills question. Listen for structure: inputs kept apart from calculations, checks that flag when totals do not tie, assumptions written down. Then ask who took the file over and whether that person could follow it.
What have you automated or handed to software, AI tools included, and what do you still check by hand?
Why ask it
Bank rules, invoice capture, scheduled journals and drafting tools all save hours, and all of them make confident mistakes. You are listening for someone who knows which outputs they sample and how often, and who can describe a time the automation coded something wrongly. Ask too what data they would refuse to paste into an outside tool.
Tell me about an accounting process you improved or simplified. What did it replace?
Why ask it
The scale does not matter: a template, a report nobody has to rekey, two approval steps turned into one. What you learn is whether they treat inherited work as fixed or ask what it costs every month. Ask how they brought round the people who liked the old way.
Tell me about a system change or migration you lived through. What was your part, and what went wrong?
Why ask it
Worth asking if you have a migration coming. People who were close to one talk about opening balances that did not tie, a chart of accounts mapped badly, and a stretch of running two systems side by side. People who watched from a distance say it went smoothly.
In a heavy week of data entry, how did you know that nothing had been missed or keyed twice?
Why ask it
Ask for the weekly count first, since fifty invoices and five hundred are different jobs. Then listen for a batch total, a log of what came in set against what went on the system, or the duplicate invoice number warning and what they did when it fired. A clerk who relied on memory loses track the first week the volume doubles.
At month end, what did the accountant need from you, and by which day?
Why ask it
Clerks feed the close even when they do not run it: invoices entered up to the cut-off, the bank matched, a list of bills received but not yet approved. Someone who knows their own deadline, and what happened downstream when it slipped, understands the job beyond their tray. Not knowing there was a deadline is common in a first role, so explain yours.
How did you file and name documents so that someone else could find an invoice a year later?
Why ask it
Auditors, tax inspectors and the next clerk all come looking eventually. Listen for a consistent naming rule, the approval kept with the invoice, and a scan attached to the entry in the system. How long records must be kept depends on the country and the kind of record, so ask what rule they worked to and tell them yours.
Accuracy and controls
What's the largest error you've caught before it went out, and how did you catch it?
Why ask it
You want the mechanism, not the heroism. Answers that credit a checklist, a variance review or a second pair of eyes describe someone who works within a system. An answer that comes down to instinct describes luck, and luck cannot be handed to whoever covers for them.
What's an error that got past you, and what changed afterwards?
Why ask it
Anyone who has done the work for a few years has one, so a denial tells you something too. What matters is whether they changed a process or only resolved to be more careful. Notice how they describe telling people, because an error owned up to on the day is far easier to fix than one somebody else finds a quarter later.
Entering a couple of hundred lines in an afternoon is dull work. What do you do to stay accurate through it?
Why ask it
Honest answers are practical: working in batches, checking a total at the end of each, a break before the last run of the day, never keying while on the phone. It suits a clerk interview better than asking whether the interviewee is detail-oriented, which everybody is for the length of an interview. If accuracy matters most to you, follow it with a ten-minute entry exercise.
You find a mistake in a period that has already been closed and reported. What do you do?
Why ask it
A good answer has two parts: size it, then tell someone. Listen for how they would judge whether it matters, who decides between correcting the earlier figures and fixing it in the current period, and whether auditors or lenders need to hear. Quietly netting it off next month is the answer that should worry you.
A set of accounts lands on your desk for review. What do you look at first?
Why ask it
Good for anyone who will review other people's work or sign off their own. Experienced reviewers start with what moved: margins against prior periods, balances that should be zero and are not, suspense and clearing accounts, round-number journals near the period end. Starting at the first line and reading down is diligence without a method.
Describe a control you added or tightened. What was the risk?
Why ask it
Following a control and knowing what it is for are different things, and this finds out which you have. Listen for a named risk, such as duplicate payments, an unreviewed journal or one person both approving and paying, and for some sense of the time the control cost. The phrase segregation of duties on its own is a memory, not an example.
You are asked to pay an invoice from a supplier you don't recognize, marked urgent by a senior manager. What do you do?
Why ask it
Urgency and seniority are the two pressures a fraudulent payment request leans on, whether the manager is real or impersonated, so this is an ordinary day in payables. You want the steps: confirm the supplier exists, verify the bank details through a channel other than the message that supplied them, look for an order and an approval. Paying first and tidying the paperwork later is the wrong reflex.
What was your part in the last audit or review: which schedules did you prepare, and who answered the auditors' questions?
Why ask it
Audit experience on a resume can mean anything from running the whole thing to pulling invoices from a cabinet. Ask what they prepared, how many queries came back on it, and what they did differently the following year. If your accounts are not audited, ask the same about a lender's review, a tax inspection or a board pack.
Tell me about an auditor request you couldn't satisfy. What happened?
Why ask it
Missing support is where you see how someone behaves under scrutiny. Good answers describe explaining the gap, offering the closest evidence available, and agreeing a fix for the following year. Someone who says the auditors were never a problem may not have been the person answering them.
Has anyone ever asked you to record something you weren't comfortable with?
Why ask it
Ask it plainly and let the silence run. What you want is a proportionate response: a question asked, an explanation sought, escalation only if needed. Both extremes tell you something: the person who has never noticed a questionable request, and the one who describes every disagreement as a matter of principle.
A colleague you like asks what someone else on the team earns, and you post the payroll journals. What do you say?
Why ask it
Finance staff see salaries, bonuses and restructuring plans before almost anyone else, and the test usually arrives as a friendly question in the break room. The answer should be a quick, unembarrassed no. Ask as well how they have stored and shared sensitive files, since a careless attachment does as much damage as loose talk.
Reporting and judgment
What reports did you produce each month, and what did the people who received them do with them?
Why ask it
Some accountants send a pack and never hear another word; others know which page the operations director turns to first. The second kind trim reports nobody reads and add the one figure somebody keeps asking for. If they cannot say who used their work, ask what questions came back after it went out.
What part have you played in a budget or a forecast, and how close did it land?
Why ask it
Plenty of accountants only meet the budget as a column to compare actuals against, which is fine if that is all your role needs. For anything closer to planning, ask what they built, whose assumptions went in, and what they concluded when actuals came in well away from the forecast.
How would you explain a variance to a manager who has no finance background?
Why ask it
Have them do it on the spot: pick a line, say travel has run well over budget, and play the manager yourself. Watch whether they lead with the cause in one sentence or start with how the report is built. What happened, why, and what it means for the rest of the year is all that manager wants.
Tell me about a number you reported that changed a decision.
Why ask it
This marks the line between recording what happened and having a hand in what happens next. Examples might be a product line shown to be losing money, a customer whose payment record changed their credit terms, or a cost trend caught early. For a purely transactional role, do not hold a thin answer against them.
Tell me about a time your work saved the company money or recovered money it was owed.
Why ask it
Duplicate payments spotted, a supplier credit never claimed, a subscription nobody used, customers billed late: the examples are usually small, and small is fine. Ask for the amount and how they found it. A candidate with no example at all may have treated the ledger as a record to keep and never as something to read.
Tell me about someone outside finance who kept sending you information late or incomplete. What did you try?
Why ask it
Every close depends on people who do not report to finance and do not share its deadlines. Useful answers involve making the request easier to meet: a shorter form, an earlier reminder, an estimate booked now and trued up later, a conversation about why the date matters. Going to the person's manager is sometimes necessary, but it should not be the first move they describe.
Tell me about a deadline you missed or nearly missed. What did you tell people, and when?
Why ask it
The timing of the warning is the whole answer. Someone who raised it as soon as the risk was clear gave their manager the chance to move the date or add help; someone who worked through the night and told nobody may one day do the same with a filing deadline. Ask what they would do differently now.
Month-end close, an auditor's request and an urgent ask from the CEO all land on the same morning. What goes first?
Why ask it
There is no single right order, which is why it is useful. Good answers ask what each deadline really is, tell at least one of the three people when to expect their answer, and protect anything with a filing date behind it. Saying they would simply stay late and do all three is the habit that hides a slipping deadline.
What do you do when you're not sure of the correct treatment?
Why ask it
Reasonable answers name a source and a person: the standard itself, a technical helpline, the auditors, a former manager. Be wary of anyone who says this never happens, and equally of anyone whose only move is to ask someone else. Follow up with the last time it came up and where the conclusion was written down.
How do you keep up with changes in accounting standards and tax rules?
Why ask it
Nearly everyone names a newsletter or a professional body, so ask for one change from the past year and what it did to their own work. Someone who really follows the rules can point to the entry, disclosure or filing that changed. Which changes matter depends on the country and the framework, so judge the habit and not whether they already know yours.
What have you had to look up recently, and where did you look?
Why ask it
It can only be answered with a real case from the last few months, which makes it hard to prepare for. Where they looked matters as much as what they found: when a treatment is contested, the standard or the tax authority's own guidance carries more weight than the first search result.
Tell me about a time you and a manager or colleague disagreed about how to account for something. How was it settled?
Why ask it
Technical disagreements are normal and say a lot about temperament. Look for someone who went back to the standard or the contract, set the two treatments side by side with their effect on the numbers, and accepted the outcome once a decision was made. Ask whether they still think they were right; an honest yes is fine.
Where would you expect a business like ours to have problems in its books?
Why ask it
The accounting version of asking what a candidate knows about your company. Someone who has read up names something plausible for your size and sector: revenue cut-off, inventory, expense approvals, intercompany balances. Their answer is also a preview of where they would look first if hired.
Fit
Which area of accounting are you strongest in, and which would you need the most help with in this job?
Why ask it
Strengths and weaknesses, asked so that a rehearsed line about perfectionism will not fit. A useful answer names an area, consolidations or payroll tax for instance, and says what would close the gap: a review of their first two closes, a course, someone to call. A weak spot in work you do twice a year is cheap to cover, and one in the daily work is not.
Are you working toward a CPA or another professional qualification, or planning to? Where are you with it?
Why ask it
CPA, ACCA, CIMA, CA and their equivalents vary by country, and so does what each one allows a person to sign, so check what your role truly requires before using the letters as a filter. For someone part-way through, ask how many exams remain and what support they would hope for. Study leave and exam fees are better agreed now than argued over later.
What did the busiest weeks of the year look like in your last job, and how did the team get through them?
Why ask it
Year end, tax season and audit fieldwork mean long weeks in most finance teams, and candidates deserve to hear what yours are like before they answer. Describe your own peak honestly, then listen for planning ahead, work brought forward and a team that shared the load. Keep it to the work; their home arrangements are not yours to ask about.
What has you looking now, and when in the finance calendar could you start?
Why ask it
Accountants often time a move around year end, an audit sign-off or a bonus date, and a responsible one will not want to walk out mid-close. The reason for leaving is the standard half of the question. The timing shows how they treat the employer they are leaving, which is how they will one day treat you.
Where do you want to be in a few years: deeper into technical work, running a team, or closer to the business?
Why ask it
Finance careers fork early, toward technical accounting, management, or analysis and business partnering. Offering the three routes gets a more honest answer than asking for a five-year plan. Be straight about which of them your team can offer, because a future controller in a role with no way up will soon be interviewing somewhere else.
Have you trained someone or reviewed their work? What did you look for first?
Why ask it
For senior roles, this shows whether they can pass on a standard or only meet one. Reviewers worth hiring describe checking the logic and the tie-outs before the formatting, and returning work with the reason attached so the same error does not come back. With a junior candidate, ask what the best reviewer they ever had did for them.
Much of this job is the same tasks on the same days every month. What do you like about work with that rhythm?
Why ask it
Worth asking of accounting clerk candidates in particular, because the role really is repetitive and pretending otherwise ends in a resignation within the year. Some people enjoy a routine they can get fast at, and some are passing through on the way to an accountant's seat. Either can be a good hire, as long as you know which you are getting and whether the job has room for it.
What would you need from us in your first month to be useful?
Why ask it
Experienced hires answer with specifics: system access, a walkthrough of the close calendar, sight of last year's file, an introduction to whoever owns the source data. A candidate with nothing on the list may not have pictured the first week yet, so prompt once by asking what they would want open on their screen on day one.
What do you want to ask me about the team or the work?
Why ask it
Their questions show what they have understood about the role. Asking about close timelines, who reviews their work, and where the numbers come from indicates someone imagining the actual job. No questions at all, at the end of a technical conversation, is worth weighing against everything else.
How to interview accounting candidates
Practical guidance for the conversation itself
Decide what you are hiring for first
Transactional, reporting, or advisory
Payables and reconciliations, month-end and statutory reporting, and analysis or business partnering call for different people. Write down which of the three dominates the role before you interview, and weight your questions accordingly.
Choose from the list
No interview has room for every question here. For an hour, eight to ten is plenty: two or three openers, the technical questions that match the level, and at least one each on errors, controls and ethics. A first-job candidate gets the basics on accruals, payables and receivables and the three statements. An experienced hire can skip those for the close, estimates, review and audit questions.
Interview questions to ask accounting clerk candidates
A clerk's work is accurate processing at volume, so choose for that: the weekly tasks question in the openers; the unmarked invoice, the supplier statement, the customer who says they have paid, petty cash and the expense claim in the technical group; then data entry, the month-end handover, filing, staying accurate and the rhythm of the job. Leave the estimates, standards and audit questions for accountants.
Match the scale
Someone from a large finance function may never have run a full close alone, and someone from a small company may never have worked under formal review. Neither is a defect, but the questions and expectations should differ.
Check what is genuinely required
Be clear about which credentials, licenses or standards knowledge the role actually needs, and verify those directly rather than treating them as a proxy for competence. What a given credential permits differs by country, so check the rule where you are.
Do not interview during close
Interviews squeezed into the busiest week of the month get cut short, and the practical exercise is usually what goes. Schedule around your own calendar.
Getting past rehearsed answers
Accounting interviews attract prepared answers about accuracy and attention to detail. A few habits get past them:
- Ask for the last time rather than a typical example. A recent, specific case is harder to tidy up.
- Ask for numbers: how many entities, how many journals, how many days to close, how large the discrepancy was.
- Follow every general answer with "what did you actually do first?" once.
- Give a small practical exercise, twenty minutes with a short trial balance or a broken reconciliation, rather than a quiz on definitions.
- Ask the same technical question of every candidate so you can compare answers rather than impressions.
Mistakes interviewers make
Testing memory instead of judgment
Asking someone to recite a standard tests what they revised the night before. Asking how they would decide a treatment, and where they would check, tests what they will actually do at their desk.
Asking about personal life
Questions about health, family arrangements or a candidate's own finances are off limits in many places, and the rules differ by country and state, so check what applies to you before the interview. If what you want to know is how someone handles a heavy month, ask for a work example.
Hiring for tidiness over reasoning
Accurate work is necessary and easy to test with an exercise. What is harder to replace is someone who notices that a number is implausible before it is wrong, so leave room for questions that probe reasoning.
Skipping the ethics question
It feels awkward, which is why it gets dropped. Ask it as a matter of routine, in a neutral tone, of every candidate at every level, so that nobody is singled out by being asked.
Not being honest about the role
If the close is chaotic, the systems are outdated, or the last person left because of the workload, say so. A candidate who takes the job on a rosier description finds out during the first close, and you may be hiring again sooner than you planned.
Reading the answers
Method beats outcome
Whether they eventually found the discrepancy matters less than how they narrowed it down. A clear search process transfers to problems they have not seen before.
Reasoning on the technical questions
A candidate who slips on a detail but asks about cancellation terms, policy thresholds or which framework you report under is often stronger than one who recites a rule cleanly. Treatments vary with the standards and with company policy, so mark the reasoning in the room and confirm the facts that matter for your role with a short exercise afterwards.
Ownership of mistakes
Give weight to a candidate who describes their own error plainly, including who they told and when. It is the nearest an interview gets to showing how they would act when something goes wrong on your books.
Curiosity about the source data
Candidates who ask where the numbers come from, who enters them, and what happens when the source is wrong tend to prevent problems rather than report them afterwards.
Consistency across the loop
Compare notes with other interviewers on specifics rather than overall impressions. Check in particular whether the candidate claimed the same work as their own in each conversation.