How to Explain Your Expertise to a Non-Technical Interview Panel

A common mistake candidates with deep expertise make is assuming everyone on the interview panel knows as much about the subject as they do. In reality, interview panels are often built from people with different backgrounds on purpose (Queensland Government guidance, for example, says panel diversity must be considered as a key factor) — and answering every question at maximum technical depth can quietly work against you.

Why interview panels are rarely uniform

Interview panels are often intentionally mixed. The hiring manager may understand every technical detail of your work because they lead the function you're applying to join. The recruiter may have a broad understanding of the role but is mainly listening for evidence of capability, communication, and fit with the selection criteria. A senior leader from another department may have little technical knowledge of your field at all — they're evaluating something different: whether you can communicate clearly, influence others, and explain complex ideas to people outside your discipline.

I saw this play out clearly during a Project Manager interview for a Regional Project Delivery team. The panel had three people: the hiring manager and one other panel member with a strong grasp of project management methodology, and me — without that background.

One candidate noticed this immediately. Whenever we asked something involving delivery concepts or methodology, he'd briefly pause and say something like: "Before I answer, would it help if I gave a quick overview of the project context, just so we're all on the same page?"

He wasn't simplifying his answer — he was adapting his communication to his audience. In under 30 seconds he'd give just enough context for everyone to follow, then move straight into his answer. He still answered every question within a couple of minutes, but every panel member could follow his thinking from start to finish. That stood out, because it showed a skill that matters just as much as the technical answer itself: recognising that different people need different amounts of context to follow a complex idea.

That's what strong communicators do in any workplace. They don't assume everyone shares their expertise — they adjust the message to the audience without diluting the thinking behind it. As your career progresses, you'll spend less time talking to people who do exactly what you do, and more time explaining your work to people who don't: executives, Finance, HR, Legal, project sponsors, clients. None of them need every detail — they need to know what matters, why it matters, and what you need from them.

The interview isn't testing everything you know

This is the hardest mindset shift for a lot of candidates: treating every question as a chance to demonstrate the full depth of their expertise. But interview questions aren't asking for everything you know — they're asking for evidence.

If you interviewed a surgeon and asked, "tell me about a difficult operation," you wouldn't expect a lecture covering every procedure they've ever performed. You'd expect one clear example that demonstrates skill. The same applies to you. Rather than showing off everything you know, share only what actually answers the question — if the panel wants more, they'll ask.

A useful test when preparing: can someone summarise your answer in under a minute? If they can't, it probably contains too much. Aim instead for this shape:

• What was happening?
• What challenge existed?
• What did I personally do?
• What was the outcome?
• What did it demonstrate?

This is essentially the STAR method again, and it works for the same reason here: it gives your answer enough structure to stay focused without losing the depth of what you actually did. It turns a complex situation into a story a mixed panel can follow and remember.

Common mistakes to avoid

• Assuming technical depth impresses everyone equally. A detail that lands well with the hiring manager may lose a non-technical panel member entirely — and you're being evaluated by the whole panel, not just the expert in the room.
• Skipping the context-setting step. A 20-30 second framing before a technical answer costs you almost nothing and keeps everyone with you.
• Treating every question as a chance to prove expertise. The goal is evidence, not a comprehensive download of everything you know on the topic.
• Over-simplifying to the point of losing substance. Adjusting your message to your audience isn't the same as diluting it — you're still expected to demonstrate real capability, just in a way everyone in the room can follow.

The real difference

I've interviewed candidates with extraordinary technical expertise who couldn't communicate it effectively and candidates with less experience who explained their thinking so clearly that the panel walked away with complete confidence in their capability. The difference wasn't intelligence or experience. It was communication.

An interview isn't an exam where you score points for including every fact or term you know. It's a conversation, and your job is to make it effortless for the whole panel — technical or not — to understand your value.

Practice it out loud

It's hard to judge from your own head whether an answer is landing at the right level of detail for a mixed audience — that's exactly the kind of thing that's easier to catch out loud than on paper. If you want a quick check on how your answers actually come across, the Interview Practice Lab has a free 3-question mock interview with structured feedback, no signup required.