What the rounds actually test
| Round | Looks like | Actually tests |
|---|---|---|
| Screening | 30 min, HR or junior consultant, CV walk-through | Communication, seniority calibration, visa/rate basics — and whether your project stories have dates and clients that hold together |
| Technical panel | 60–90 min, 2–3 interviewers, module scenarios | Diagnostic order under pressure; vocabulary precision; whether experience is lived or read. See our Payables scenario set for the exact shapes |
| Manager / client round | 45 min, delivery manager or the end client | Can we put this person in front of a controller? Composure, expectation-setting, saying "I'd verify" without sounding weak |
The three interviewers on every panel
Titles differ; the types never do. We built Tools Releases around them because fifteen years of sitting on these panels shows the same trio every time:
The Architect — tests technical depth
Asks configuration and design questions and then goes one level deeper than your answer, every time. Primary ledger to secondary ledger. Ledger to legal entity. SLA rule to the actual journal line. The Architect's follow-up chain only stops when you either demonstrate the floor of your knowledge honestly ("beyond that I'd check the setup, I haven't touched that variant") or pretend — and pretending is instantly visible.
The Partner — tests business judgment
Wraps every question in a client situation: the escalation, the month-end panic, the CFO who wants the impossible cutover date. The Partner doesn't care that you know the config path; they care that you ask about the process and the people before touching setup. Their favorite failure: candidates who answer a stakeholder question with a configuration answer.
The Skeptic — tests whether your stories are real
Says little, then: "Which month was that go-live?" "What was the actual error?" "How many invoices a day?" The Skeptic knows that real experience has texture — an exact hold name, a specific ugly workaround — and that borrowed experience never does. One concrete detail satisfies The Skeptic faster than ten fluent paragraphs.
Module-by-module: where panels spend their minutes
- General Ledger: ledger and legal-entity design decisions, intercompany balancing, allocation logic, period close orchestration — and "walk me through a close that went badly."
- Payables: the richest scenario territory — holds, PPR failures, prepayments, supplier data quality. Ten worked examples with panel commentary are in the Payables scenario post.
- Receivables: transaction sources and AutoAccounting design, receipt application and lockbox exceptions, revenue recognition boundaries with projects/contracts.
- Assets & Cash: fewer minutes, sharper questions — mass additions from AP, depreciation reruns, bank-statement reconciliation exceptions.
- Cross-module (senior roles): SLA design, FBDI/ADFdi data-load strategy and error recovery, OTBI vs BIP judgment, and — new since 2025 — AI agents: which finance tasks would you hand to one, and which never.
The follow-up chain: where offers are decided
First answers are table stakes; panels decide on the second and third question. The chain has a rhythm: your answer → "why?" → "what if that's not it?" → "how would you prove it?" Candidates fail chains in two ways: retreating to generic method ("I would analyze the issue thoroughly") or inventing specifics under pressure — The Skeptic's favorite meal. The only preparation that works is rehearsing chains against something that pushes back; reading, by definition, cannot push back.
Preparation plan (two weeks, evenings)
- Days 1–3: pick your two strongest modules; write one lived, textured story per module (with the ugly detail included).
- Days 4–7: drill scenario chains in those modules — one per evening, out loud, against The Panel or a merciless friend.
- Days 8–10: cover the cross-module layer: SLA, data loads, reporting judgment, and one evening on AI agents vocabulary — the newest visible differentiator.
- Days 11–14: full mock rounds, mixed modules, no notes. Rehearse saying "I haven't touched that; here's how I'd verify" until it sounds like strength — because to panels, it is.
Meet all three interviewers before they're real.
The Panel runs the exact follow-up chains this guide describes — and scores you the way a real panel hears you. First drill free.
Face the Panel — free →Updated July 2026 · Written from real hiring-panel experience. Related: Payables scenario questions · Oracle Fusion AI agents field guide.