A senior-level US accounting assessment usually takes one of three forms: a written case study, a take-home reconciliation or flux exercise, or a live walkthrough of your reasoning. All three grade the same qualities, which are whether your conclusion is right, whether your logic is documented, and whether a finance leader can act on your summary. Knowing the format ahead of time lets you prepare the right skills, and this guide explains what each one looks like and how senior candidates stand out.
The written case study is the most common technical screen. It presents a scenario, such as a customer contract with variable pricing, a lease amendment, or the acquisition of a small business, and asks for a short memo within 60–90 minutes. The take-home exercise gives you a file and a few hours of effort, usually a bank reconciliation with unexplained items, a trial balance comparison that needs flux commentary, or a schedule such as a deferred revenue rollforward. The live walkthrough puts you on a screen share, where you explain a workpaper or journal entry while the interviewer changes the facts.
Senior roles often combine formats. A candidate might complete a take-home on Tuesday and defend it live on Thursday, which makes the quality of your documentation as important as the numbers themselves.
Graders score a case study on conclusion, support, and clarity. A correct conclusion carries the most weight, and the support is what separates senior candidates: the specific ASC paragraph or policy you relied on, the facts you treated as important, and the alternative treatment you considered and rejected. A memo structured as issue, relevant guidance, analysis, and conclusion gives the grader everything in the order they expect.
State your assumptions explicitly. When a fact is missing from the scenario, write the assumption you made and how the answer would change under a different one. That habit mirrors real work, where a Controller wants to see what you decided and why, and it protects you when the grader had a different reading of the facts in mind.
Quantify the impact whenever the scenario provides numbers: the journal entries, the effect on revenue or liabilities, and any disclosure implication. A conclusion without the entries behind it reads as theory.
Take-home work gets graded on accuracy and professionalism. Tie every total back to its source, check that subtotals foot, and keep formulas consistent so a reviewer can trace them. Separate inputs from calculations with clear formatting, avoid hardcoded numbers inside formulas, and add a short reviewer-notes tab that lists what you did, what you found, and what remains open.
For a reconciliation with unexplained items, propose a resolution for each one. An aged reconciling item with a suggested adjusting entry and a note on who to ask shows the follow-through a US team expects. For flux commentary, lead with the driver, quantify it, and say whether the movement is recurring or one-time. Commentary that restates the variance without explaining it earns little credit.
Finish with a short cover note that summarizes what's included, the assumptions you made, and any questions you'd ask the business owner. That note is the part of the submission a CFO would read first.
Live walkthroughs test how you think under interruption. Narrate your reasoning as you go, ask clarifying questions before committing to an answer, and keep your screen organized so the interviewer can follow. When the interviewer changes a fact, such as moving the contract's start date or altering a payment term, work through the effect on the entries and disclosures out loud. The process of adapting matters more than reaching an answer instantly.
Admitting a gap is acceptable when you pair it with a method. Saying you'd confirm the treatment in the Codification and review how comparable companies disclose it demonstrates the research habits senior accountants rely on every day.
Time discipline shows up in the result. Read the full instructions first, outline your approach, solve the core problem, and reserve the final stretch for review, because errors in tie-outs and signs often appear when candidates rush the last section. Respect the stated time expectation, since overbuilding a take-home can signal poor prioritization.
The strongest senior submissions share one trait: they read like work product from a colleague. The conclusion is clear, the support is documented, and the summary anticipates the reviewer's next question. Candidates who prepare for each format with that standard in mind turn an assessment into a demonstration of how they'd operate on the team.
Most are unpaid and scoped to a few hours. A request that expects a full day of work, or that uses live company data for real deliverables, deserves a question about scope before you start.
Codification access is generally expected, since real work relies on it. AI tools are worth asking about in advance, and the answer should come from the employer's instructions.
Send one concise email with your clarifying questions, and state the assumption you'll use if you don't hear back. Handling ambiguity that way is part of what the assessment measures.
Revenue-focused roles lean toward contract analysis and deferred revenue schedules, while FP&A assessments often involve a model with scenarios and a short narrative for leadership.
Revenue-focused roles lean toward contract analysis and deferred revenue schedules, while FP&A assessments often involve a model with scenarios and a short narrative for leadership.