# Technical AI interview practice for accountants

A technical AI interview for an accountant reasons out loud through questions like when to recognize revenue on a multi-year service contract or whether a cost should be capitalized or expensed, with the AI interviewer following up on the reasoning behind the answer rather than accepting a memorized rule.

The difference between reciting a rule and actually understanding it shows up fast once a follow-up lands. This session is built around that gap.

## A revenue recognition question that doesn't stop at the first answer

The interviewer describes a company that just signed a two-year service contract, paid upfront in full. The first question asks how much revenue should be recognized in month one, and why. A candidate who answers correctly, that revenue gets recognized as the service is delivered rather than all at once when cash arrives, gets a harder follow-up next: what happens to that answer if there's real doubt about whether the customer will actually pay out the full contract term. That second question is where a memorized rule stops being enough, since it asks for judgment about collectibility layered on top of the timing rule already explained. A separate line of questioning might swap in a capitalize-versus-expense call instead, a large repair to equipment, and ask what would change the answer if the repair extended the asset's useful life versus just kept it running as before.

## What gets covered

Expect conceptual questions framed as scenarios rather than definitions: when revenue actually gets recognized on a multi-period arrangement, whether a specific cost belongs on the balance sheet or the income statement, how a depreciation method choice affects reported earnings in the near term versus later. The AI pushes for the reasoning behind each answer, not just the conclusion, and will change a scenario's details mid-conversation, adding a collectibility concern, extending a useful life, to see whether the candidate's answer holds up once the facts shift. Before the voice conversation starts, the flow opens with a hands-on challenge stage matched to the role, which for accounting work means a written or SQL exercise rather than software code. A written challenge format exists separately for candidates who want to draft an answer instead of speaking it, closer to how a memo or a working paper would actually get written.

## How scoring applies here

The Technical dimension carries real weight in this session specifically, and the written reasoning behind that score explains what held up in the answer and what didn't, not just whether the final conclusion was correct. Calibration floors and caps matter more here than in a session with no checkable content, since revenue recognition timing and a capitalize-versus-expense call both have a defensible right answer underneath them. A fluent explanation that skips past the collectibility question or ignores the useful-life detail in a follow-up won't outscore a shorter answer that actually addresses what changed. Communication still gets graded alongside it, since an accountant who reasons correctly but can't explain the logic clearly is still missing part of what the role needs.

## Frequently asked questions

### Will I have to type or run any code in this session?

No. The technical interview is a spoken conversation about accounting reasoning. Writing something out instead of speaking it is available separately through the written challenge format.

### Does it ask about revenue recognition specifically?

It can. Revenue recognition timing on multi-period contracts is a common scenario in this session, along with capitalize-versus-expense calls and depreciation method reasoning.

### How is a technical session scored differently from a general one?

The Technical dimension carries more weight here, backed by written reasoning tied to whether the accounting logic given actually holds up, not just whether the conclusion sounds confident.

### Will the interviewer change the scenario partway through?

Often, yes. A follow-up might add a collectibility concern to a revenue question or extend an asset's useful life in a capitalize-versus-expense scenario, to see whether the first answer still holds.

## Related pages

- [Accountant interview questions](/interviews/accountant)
- [Technical AI interviews](/features/technical-interviews)
- [Browse open roles](/jobs)

## Practice explaining accounting reasoning out loud

Run a technical AI interview and work through revenue recognition and capitalize-versus-expense reasoning, then review a scored report on where the logic held up.

Start practicing free: https://www.intervieux.ai/register · Hire with Intervieux: https://www.intervieux.ai/employers/signup