What Solicitor Interviews Actually Test

Who is actually in the room

For a training contract or NQ role, you will usually face a panel of two or three: a partner or senior associate from the practice group you're applying to, someone from graduate recruitment or HR, and sometimes a more junior fee-earner who sat in your seat last year. The HR person is not there to make small talk — they're checking you'll survive supervision, deadlines, and client contact without needing constant reassurance. The partner is checking something narrower: can this person be put in front of a client or opposing counsel without embarrassing the firm.

For a lateral move at associate or senior associate level, expect the practice group head and one other partner, and increasingly a conversation with someone from business development if the role has a book-building expectation attached. In-house roles are different again: you'll meet the General Counsel, sometimes the CFO or a commercial director, and the questions shift from "can you draft this" to "can you tell a business person what the risk actually is in language they'll act on".

What rarely changes: someone on the panel has read your application in enough detail to ask about a specific matter you listed, not just the practice area. If you wrote "advised on a £40m share purchase" and can't describe what the disclosure letter was for, that's noticed immediately.

The technical or practical assessment

Most firms still use some form of written exercise, and it tends to fall into one of three shapes:

• A drafting task under time pressure — write a client care letter, an attendance note, or a short letter of advice from a set of facts. This isn't testing your prose. It's testing whether you can identify the one or two points that actually matter to the client and put them near the top, rather than burying them under boilerplate.
• A case study or scenario paper — you're given a fact pattern (a dispute, a lease, a proposed transaction) and asked to spot the issues. Property seats will ask about SDLT thresholds or overage clauses; corporate seats about warranty and indemnity gaps; private client about the nil-rate band and residence nil-rate band; family about the difference between a consent order and a clean break.
• A critical reasoning test, most commonly Watson Glaser, still used by a number of larger firms at training contract stage. It measures argument evaluation, not legal knowledge, and candidates who've never sat one before tend to underperform simply from unfamiliarity rather than ability — worth doing a timed practice paper beforehand.

What interviewers are actually watching for in all three isn't recall of the law. It's whether you narrow a broad set of facts down to what's relevant, and whether you flag what you don't know rather than guessing confidently. A trainee who says "I'd need to check the current SDLT bands, but the structure would be..." reads as more capable than one who states a number that's wrong.

The questions that separate competence from conversation

The questions that sound like they're building rapport are usually the ones doing the real work.

"Tell me about a time you had a conflict of interest, or thought you might." This isn't asking whether you know the SRA's rules on conflicts in the abstract. It's asking whether you noticed one in practice, said something before it became a problem, and can describe what you actually did — ran a conflict check, spoke to your supervising partner, declined to act. A candidate who answers with the definition of a conflict rather than an instance of catching one hasn't demonstrated anything.

"A client asks you to do something you're not comfortable with — what do you do?" This is testing your grip on the SRA Principles, specifically acting with integrity and upholding public trust, and whether you understand the difference between advising against something and refusing to act. The weak answer is "I'd tell them no" with no explanation of what comes before that — checking instructions, explaining the risk, documenting the conversation, escalating internally if it persists.

"Walk me through a deal or matter you worked on, focusing on where it nearly went wrong." This is deliberately not asking for the highlight reel. Anyone can describe a transaction completing smoothly. What's being tested is whether you can describe a disclosure that surfaced late, a limitation issue you spotted, or a client who wanted to move faster than due diligence allowed — and what you or your supervisor did about it.

For litigation and dispute resolution roles specifically, expect something like "how would you advise a client who wants to litigate a claim that's commercially weak but they're determined to bring?" This tests whether you can separate legal merit from client instructions and cost-benefit realism, including proportionality under the Civil Procedure Rules, without simply refusing the instruction outright.

For corporate and commercial roles, "what deal have you been following in the market and why does it matter to clients like ours?" is a commercial awareness check, but the follow-up — "what would you have flagged if you'd been running due diligence on that?" — is where the shallow answers get caught out.

What a shallow answer actually sounds like

To someone who does this job, a shallow answer has a particular texture. It's fluent, it uses the right vocabulary, and it says nothing that couldn't have been said by someone who'd only read about the matter rather than worked on it.

Reciting the SRA's seven Principles in order, when asked an ethics question, is a shallow answer even if every word is correct — because the question was never testing whether you'd memorised them, it was testing whether you'd apply them to the specific facts you were just given. Similarly, "I'd escalate to a partner" as the entire answer to a dilemma question is shallow, because escalation is the last step, not the whole process, and the interviewer wants to hear what you'd check and say before you got there.

Describing a transaction using only the language from the deal's press release — value, parties, sector — rather than anything about the mechanics you were actually responsible for (a schedule you drafted, a warranty you negotiated, a completion condition that nearly didn't clear) tells the panel you were on the matter but not really in it. And in competency answers generally, a response that describes what a good solicitor would do in the abstract, rather than what you did on a specific file, is the single most common way candidates undersell themselves without realising it.

What to do before the interview

Go back through your own matter list and, for two or three matters per practice area you're being interviewed for, write down: what nearly went wrong, what you actually did about it, and what you'd do differently. That's the raw material for most of the competency and ethics questions above, and it's far more useful preparation than rehearsing a generic answer to "tell me about yourself".

If the role names a specific practice area, refresh the current thresholds, rules, or recent case law that a working solicitor in that area would be expected to have live in their head — SDLT bands, the current IHT nil-rate bands, recent Court of Appeal decisions in your field — not because you'll be quizzed on trivia, but because getting a basic figure wrong under pressure undermines confidence in everything else you say.

jobmarket.pro reads the advert in full against your actual matter history and drafts the application from that, rather than from a generic solicitor CV template, before you get anywhere near the interview stage.