One-way interview questions for finance and accounting, with model answers

A one-way interview for a finance or accounting role is a pre-recorded screen. You answer set questions to camera on your own time, with no interviewer on the other end. A hiring team reviews your recordings later, often before an assessment center or a live panel.

For finance jobs the questions usually split three ways: why you want the role, behavioral questions about deadlines and accuracy, and at least one role-specific question that can be technical.

Large finance employers and graduate schemes lean on this format because they screen in volume and want a consistent first read before they spend a panel’s time. Candidates report recorded rounds for graduate finance programs like ARM’s, and for bodies like the OECD, where a written test and a HireVue round were both part of the process. The format catches a lot of strong candidates off guard, mostly because there is no interviewer to react to. Once you know what they ask and how to shape an answer, that awkwardness drops fast.

This page covers the questions finance and accounting candidates actually get in a one-way interview, three model answers in the STAR format, and the traps that are specific to finance roles.

The format you are walking into

Time limits vary by employer. You typically get a short window to think, often under a minute, then a minute or two to record. One candidate described having 30 seconds to prepare a two-minute answer. Some setups let you re-record. Some are one take, no retake, with the timer counting down. You usually will not know which until you start, so set up as if you only get one shot. If you want the full pre-record routine, the HireVue guide covers the tool most finance employers use.

A finance screen is typically three to five questions. The pattern is consistent across firms:

1. A motivation question. Why finance, why this firm, why this division.
2. One or two behavioral questions. A deadline you hit under pressure, a mistake you caught or made, a time you explained numbers to someone who is not in finance.
3. At least one role-specific question. For an accountant, often a process question (the month-end close, how you reconcile). For an analyst or grad-scheme seat, often a light technical prompt (“walk me through a DCF”) or a markets question.

Spend most of your prep on the third bucket. Anyone can say they like finance. The role-specific answer is what separates people on a recording.

Motivation questions (and how to answer)

These are easy to underestimate. They are not throwaways. On a recording, the first ten seconds set whether the reviewer leans in or starts skimming. Be specific and be quick.

“Why do you want to work in finance / for us?” Skip “I’m good with numbers and I like a challenge.” Name one concrete reason tied to the role. For an audit or accounting seat: “I want the early-career rotation through different industries that audit gives you. I learn a business fastest by reading its books.” For a specific firm, name something real about them. Their division, a recent deal, the sector they cover. Pull one fact off their site before you record so this answer lands on something true. Thirty seconds, then stop.

“Why this division / desk / specialty?” Graduate schemes often ask you to choose. Do not hedge across all of them. Pick one and give a reason that shows you understand what the work actually is. “I want FP&A over financial reporting because I’d rather be forward-looking, building the forecast and explaining the variance, than closing the prior period.” That tells the reviewer you know the difference, which a surprising number of candidates do not.

Behavioral questions, answered with STAR

Behavioral prompts are where the STAR method earns its keep. With no interviewer to nudge you, structure is the only thing keeping you on track. Keep it light: one line of situation, the action you took, the result with a number.

“Tell me about a time you worked under a tight deadline.”

Situation: At my last role we ran a five-day month-end close, and one month a system migration knocked two days out from under us. Action: I owned the bank and intercompany reconciliations. I built a quick checklist of the accounts most likely to break, cleared those first, and flagged a 12K variance to my manager the same morning I found it instead of sitting on it. Result: We still closed on day five. The 12K turned out to be a timing difference on a prepaid, and because I’d raised it early we resolved it before it hit the reported numbers.

That lands in about 90 seconds and every sentence has a number or a specific action. No “I work well under pressure.”

“Tell me about a mistake you made, or an error you caught.”

Situation: Early on, I posted an accrual to the wrong cost center, so one department’s spend looked about 8K too high in the month-end pack. Action: I caught it during my own review the next day, before it went to the budget holder. I reversed it, reposted it correctly, and then added a second check to my process: I now tie the accrual schedule back to the cost-center list before I post, not after. Result: The corrected pack went out on time and the budget holder never saw a wrong number. I haven’t miscoded an accrual since I added that check.

Reviewers are not looking for someone who never makes mistakes. They are looking for whether you catch them, own them, and close the gap. In finance, “here’s the control I added” is the whole answer. A clean correction beats pretending you are flawless.

“Tell me about a time you explained financial information to someone outside finance.”

Situation: I supported a sales director who kept overspending against budget because he read the report as cash in the bank, not a monthly limit. Action: Instead of resending the same spreadsheet, I built him a one-page view with three numbers: budget, spent, remaining, refreshed weekly, with a short note on what drove the change. I walked him through it once on a call. Result: His overspend stopped that quarter. He started forwarding me his commitments before he signed them, which made my forecast more accurate too.

This question matters more in finance than people expect. A lot of the job is translating numbers for people who do not live in them. Show that you can.

The role-specific questions (this is where it is decided)

Here is where a finance one-way interview separates people, and where the right prep pays off most. What you get depends on the seat.

Accounting and audit: process questions

For accountant, bookkeeper, and audit roles, the technical question is usually about a process you should know cold.

“Walk me through the month-end close.”

The close is about making sure the period’s numbers are complete and accurate before we report. I’d start by posting accruals and prepayments so costs land in the right period. Then reconciliations: bank, intercompany, key balance-sheet accounts, so the ledger ties to the supporting detail. Then I’d review the P&L against budget and prior month and chase any variance that doesn’t have an obvious cause. Last, I’d prepare the reporting pack and flag anything the business needs to know. The whole point is to catch the problem before it’s in a number someone relies on.

Say the steps in order. The reviewer is checking that you understand the logic of the close, not that you can recite a textbook. Order and reasoning matter more than completeness.

“What is the difference between accounts payable and accounts receivable?” or “Explain the accounting equation.” These basic checks come up for early-career roles. Answer them plainly and do not over-talk. “Assets equal liabilities plus equity. Every transaction keeps that in balance, which is why double-entry works.” Done. Padding a simple answer reads as nerves.

Analyst and grad scheme: “walk me through” and markets questions

For FP&A, corporate finance, and banking grad schemes, expect a light technical prompt.

“Walk me through a DCF.”

A DCF values a business on the cash it’s expected to generate. First I’d project the company’s free cash flows over a forecast period, usually five years. Then I’d discount each year back to today using WACC, the weighted average cost of capital, because a pound next year is worth less than a pound today. Then I’d add a terminal value to capture the cash flows beyond the forecast, discounted back the same way. Summing those gives enterprise value. From there you can bridge to equity value by netting off debt and adding cash.

You do not need to derive WACC or debate terminal-value methods in 90 seconds. Name the steps in the right order, define the one term that matters (WACC), and stop. Correct and structured beats exhaustive and rushed.

“How are the three financial statements connected?” A classic grad-scheme prompt. Keep it tight: net income from the income statement flows into retained earnings on the balance sheet and is the starting line of the cash flow statement. Changes in balance-sheet items drive the cash flows. Ending cash on the cash flow statement is the cash line on the balance sheet. If you can say that cleanly to a camera, you are ahead of most.

“Tell me about a recent deal or something happening in the markets.” Have one prepared. One real story, two or three sentences on what happened, and one sentence on why it matters or what you think. The reviewer is checking that you follow the industry you are asking to join, not that you can predict rates.

Traps that sink strong finance candidates

• Over-talking a simple technical answer. “Explain the accounting equation” wants one clean sentence, not three minutes. Padding a basic answer to fill the timer reads as nerves. Answer it and move on.
• Getting the order wrong on “walk me through.” On a DCF or a close, the steps have a logic. Saying them out of sequence tells a reviewer you memorized rather than understood. Practice the order out loud until it is automatic.
• No numbers in behavioral answers. “I helped with the close” is invisible. “I owned the bank and intercompany recs on a five-day close and flagged a 12K variance” is hireable. Use real figures, even rough ones.
• Hiding a mistake. Finance reviewers are reading for whether you catch and own errors. “I’ve never really made one” is the wrong answer. The right one names the error, the fix, and the control you added.
• Reading a script. A few notes on a sticky note are fine, and a short step list for technical prompts is sensible. A full script read word for word flattens you. Bullet points, not paragraphs.
• Buying or memorizing the question bank. You will find candidates on forums asking for, and even offering to pay for, leaked question lists for big-name programs. Memorizing answers to specific questions backfires on camera. A reviewer can hear a recited answer, and grad schemes change their question sets. Prep your stories and your technicals, not a script for a list you found online.
• Running out of time mid-explanation. Watch the timer. A correct DCF walkthrough that the clock cuts off at “and then you discount” is worse than a slightly shorter one you finished on purpose.

Prep in fifteen minutes

You do not need hours. Before you hit record:

• Pull one real fact off the firm’s site (their division, a recent deal, the sector they cover) so your “why us” answer lands on something true.
• Write four sticky-note bullets: one deadline story, one error-and-control story, one “explained numbers to a non-finance person” story, and the step list for whatever technical prompt your seat is likely to get (close, DCF, three statements).
• Say your most likely technical answer out loud once. Out loud, not in your head. The first time you hear yourself walk through a DCF should not be on the take that counts.
• Set up your shot: light from the front, camera at eye level, talk to the lens.

A finance one-way interview rewards the same things a live interview does, plus the discipline to stay structured with no one in the room. Put a number on your behavioral answers, get the order right on your technicals, and own the mistakes you have caught.

For the structure that holds your behavioral answers together under a timer, read the STAR method on a one-way video interview. For the full pre-record checklist on the tool most finance employers use, see how to do well in a HireVue interview.