Interview preparation that actually changes the outcome

Almost all interview advice is generic because generic advice is easy to write. It is also nearly useless, because by the time you are at interview the employer already believes you can probably do the job — your CV got you there. What they are now deciding is something else entirely.

What the interview is actually assessing

Three things, roughly in this order: will this person be straightforward to work with, will they still be here in two years, and can they handle the parts of the job that go wrong. Technical capability is usually the least of it at this stage. Prepare accordingly.

The preparation that works

1. Build six stories, not thirty answers

Do not try to prepare an answer for every possible question. Prepare six substantial stories from your career — a success, a failure, a conflict, a change you led, a time you were out of your depth, and a time you changed your mind. Almost every competency question is a door into one of those six. You will sound considered rather than rehearsed.

2. Structure them, but lightly

STAR works — situation, task, action, result — but candidates who recite it audibly sound robotic. Use it as scaffolding: thirty seconds of context, ninety seconds on what you specifically did, and thirty seconds on the outcome with a number in it if you have one. The single most common failure is spending three minutes on context and never reaching what you did.

3. Know your own CV forensically

• Be able to explain every gap and every short tenure in one calm sentence without sounding defensive
• Have a real number attached to at least three achievements you list
• Know why you left each role, phrased in terms of what you moved towards rather than what you escaped

4. Prepare questions that reveal something

'What does a typical day look like' wastes your only chance to assess them. Better questions get you information you cannot obtain any other way:

• What would make you look back in twelve months and say this hire went really well?
• What's the hardest part of this role that isn't obvious from the job description?
• Why is the role open, and what happened with the last person in it?
• How is success measured here, and how often is that reviewed?
• What's something about working here that you'd want a candidate to know before accepting?

For legal interviews specifically

• Expect detailed questions on your caseload: volume, value, complexity and how much ran without supervision
• Have a matter you can talk about at length, with the commercial reasoning as well as the law
• Ask about billing targets in hours, and how many of the team hit them last year. A vague answer is itself an answer
• Be ready on supervision — who reviews your work now, and what you would want from a supervisor next
• Know the firm's practice areas and recent work well enough to ask something specific. In a market this small it is noticed

The last hour

Re-read the job description and your own application. Check the names and roles of everyone on the panel. Test the video link if remote, and have the dial-in number as a fallback. Then stop preparing — candidates who cram in the final hour interview worse, not better.

If Sowers put you forward, you will get panel names, format, what they asked previous candidates, and a prep call before the day. That is standard, not a favour.