The scenario: an issue buried in the facts
A fact pattern describes a vendor contract dispute, a side conversation that may have modified the written terms, and a payment made under protest, with no single sentence in the recitation actually stating what the legal issue is.
A technical interview built for this role hands over that pattern and asks the candidate to work through it live: what issues does this actually raise, in what order should they be analyzed, what additional facts would change the read entirely. There's no memo to draft, just the reasoning a candidate would have to produce on the spot if a partner asked the same thing across a desk.
What gets tested in this session
Expect fact patterns built around contract disputes, procedural questions, or a scenario with a hidden ethics wrinkle folded into the facts, each one asking for the analytical process rather than a single correct answer. The AI interviewer follows up the way a real interviewer would, asking what a different fact would change or pushing on an issue left unaddressed.
What this session does not cover is any actual drafting. For a firm that also tests a written memo or an issue-spotting write-up, that lives in technical challenges, a separate feature supporting a written format alongside coding and SQL for firms with a technology practice that also test those, and it's worth treating as this session's companion rather than a substitute for it.
Scoring
How the five dimensions apply here
Technical is the dimension doing the most work in this session, and its written reasoning explains whether the issue-spotting was complete and the analysis well-ordered, not whether a single predicted conclusion got reached. Communication matters nearly as much, since a candidate who spots every issue internally but can't lay them out clearly loses the part of a callback that actually gets evaluated.
Calibration floors and caps apply the same way here as elsewhere, so a confident answer that names one issue and stops won't outscore a slower one that works through the full fact pattern.
Frequently asked questions
Will I be asked to draft a memo or write anything in this session?
No. The technical interview type is a spoken issue-spotting conversation. Drafting an actual memo or written analysis happens in the separate technical challenges feature's written format.
How is this different from a job-description session for the same role?
The job-description type reads a specific posting and questions you on its named practice area. The technical type presents a fresh issue-spotting hypothetical without needing a posting to draw from.
What if the firm I'm targeting also gives a written writing sample?
That's a common, separate part of many legal hiring processes. Pair this session with technical challenges, which supports a written format for exactly that kind of exercise.
Does naming one issue quickly score better than working through several slowly?
No. Calibration floors and caps apply to this session the same as every other Intervieux interview, so a fast answer that stops at one issue won't outscore a slower one that spots and orders the full set.
Related pages
Practice the issue-spotting hypothetical out loud
Run a technical AI interview to rehearse spoken legal analysis, then pair it with technical challenges if the firm also tests a written memo.