How to interview candidates more senior or more expert than you
On this page
- What goes wrong when you are the less expert person
- Before the interview: define success in your terms
- What you can judge well
- 14 questions, with strong answers and red flags
- Checking claims you cannot evaluate directly
- References and backchannels
- Handling the dynamic in the room
- Questions people ask
To interview a candidate more senior or more expert than you, stop trying to test knowledge you do not have and assess what you can judge well: the results they personally drove, how they make decisions and trade-offs, whether they can explain expert work to a non-expert, how they would approach your situation, and whether you can work together. Borrow an expert for the technical depth you cannot evaluate, and verify claims through specifics, numbers and references rather than impressions.
This happens more than people admit: a founder hiring a first head of finance, an operations manager hiring a data scientist, a new manager hiring someone with twice their experience. It is different from a standard leadership interview, which is covered in how to interview for leadership roles. The challenge here is the gap between you and the candidate.
What goes wrong when you are the less expert person
- You are dazzled. Confident jargon, a famous employer and a large previous team read as competence, and you stop asking follow-up questions.
- You over-correct. Feeling out of your depth, you ask trick questions or challenge everything, and a strong candidate decides not to work for you.
- You defer. The candidate steers the interview to their strongest stories, and you leave with a pleasant conversation and no evidence.
- You hire a clone of the last expert you met, because you had no criteria of your own to compare against.
All four come from the same place: walking in without a clear view of what this person must achieve in your organization. Fix that first.
Before the interview: define success in your terms
You may not know how to do the job, but you know what the business needs from it. Write down, in plain language:
- The outcomes for the first year. "Monthly close in eight working days, with numbers the board trusts" rather than "strong finance leadership".
- The situation they walk into. Budget, team, systems, the mess, the politics, what has been tried.
- How they will work with you. How often you meet, which decisions are theirs, which are yours, what you need explained.
- The areas you cannot assess. A short list you will hand to an expert interviewer.
Then turn it into a scorecard with four or five areas, each with a line on what good looks like. The interview scorecard template works for this.
Borrow an expert for the depth you cannot judge
Find someone who can assess the specialist part: a senior practitioner in another team, an advisor, an investor's operating partner, or a former colleague paid for an hour. Brief them properly:
Expert interviewer brief
Role: [title]. Outcomes for year one: [2-3 outcomes].
Please assess only: [e.g. "depth in revenue recognition and audit
readiness" / "ability to design and run production ML systems"].
I will cover: results, decision-making, communication, fit with our team.
Please score 1-4 on each area with one piece of evidence, and tell me:
- What would they do well here from day one?
- What would they need support with?
- Anything that did not add up?
Please send scores before we discuss.What you can judge well
| Area | Why you can assess it |
|---|---|
| Results they personally drove | Outcomes are described in business terms: cost, time, revenue, risk, people |
| Decision-making and trade-offs | Every good decision has options, reasons and costs, which anyone can follow |
| Explaining to non-experts | You are the non-expert; this is what working with them will be like |
| Fit to your situation | You know your constraints better than they do |
| Working relationship | You are the manager; only you can judge how you would work together |
14 questions, with strong answers and red flags
Results they personally drove
| Question | Strong answer sounds like | Red flags |
|---|---|---|
| 1. What is the result you are proudest of in the last three years, and what exactly was your part? | A clear before and after, with their decisions separated from the team's | Only "we"; the result belongs to the company, not to anything they did |
| 2. What would have gone differently if you had not been there? | A specific decision or intervention and its consequence | "It would have been harder" |
| 3. Tell me about something you led that did not work. | What they misjudged, when they noticed, what they changed | A failure caused entirely by others, or no failure at all |
| 4. How did you measure success in your current role, and what were the numbers last year? | Specific measures, stated plainly, including a miss | Cannot name measures, or only vanity measures |
Decisions and trade-offs
| Question | Strong answer sounds like | Red flags |
|---|---|---|
| 5. Walk me through a big decision where the options were close. What did you give up? | Real alternatives, the criteria used, the cost accepted | An obvious choice presented as hard; no cost |
| 6. When did you change your mind on something important at work? | New evidence, how they recognized it, what it cost to reverse | Never has; or changed because a boss insisted and still resents it |
| 7. What do people in your field commonly get wrong? | A considered view with reasons, and some humility | Contempt for others, or a generic answer anyone could give |
Explaining to non-experts
| Question | Strong answer sounds like | Red flags |
|---|---|---|
| 8. Explain the most technical part of your last big project as if to our board. | Plain words, a concrete example, checks whether you followed | Jargon, then impatience when you ask what it means |
| 9. How do you tell a non-specialist leader that their plan will not work? | Leads with the risk in business terms and offers an alternative | "I just tell them straight" with no sense of how it lands |
| 10. What will I need to understand about your area to support you well? | Two or three specific things, and how they would keep you informed | "You don't need to worry about it" |
Your situation and the working relationship
| Question | Strong answer sounds like | Red flags |
|---|---|---|
| 11. Here is our situation [two minutes]. What would you want to find out in your first month? | Questions before answers; what they would look at and who they would talk to | A ready-made plan from their last company, without asking about yours |
| 12. What would make this role hard for you here? | An honest read of your constraints: smaller budget, less structure, fewer specialists | "Nothing" |
| 13. You would be reporting to someone less experienced in your field. How would you want that to work? | Clear, respectful expectations about decisions, updates and disagreement | Visible reluctance, or expecting to bypass you to your manager |
| 14. What did the best manager you have had do that you want from your next one? | Specific behaviors you can judge whether you would offer | Only autonomy, with no sense of what they owe in return |
Checking claims you cannot evaluate directly
You do not need expertise to test whether a story holds together. Use these moves on any claim:
- Ask for numbers and a baseline. "Reduced costs significantly" becomes "from what, to what, over what period, and how was it measured?"
- Go one level down, twice. "How did you do that?" and then "What was hard about that part?" Real experience produces detail and difficulty. Rehearsed stories repeat themselves.
- Ask who else would tell the story differently. People who did the work know where the disagreements were.
- Ask them to teach you one thing. "Teach me how you decide X, in five minutes." Deep expertise usually simplifies well; shallow expertise hides behind terms.
- Compare with the expert's notes. Where your impression and the expert's score disagree, trust the evidence each of you wrote down, and ask a follow-up question in the next round.
Keep a written record of the answers, including the numbers the candidate gave, so you can check them against references and the expert's view. Interview Signal can take those notes on your computer without a bot joining the call, which leaves you free to follow the conversation rather than write it down.
References and backchannels
References matter more when you cannot judge depth yourself. Ask for a former manager, a peer and someone who worked for the candidate, and ask each one the same focused questions: what the candidate personally achieved, what they needed from their manager, and what they would want the next manager to know. The reference check template has a full script.
Do not call people at the candidate's current employer without permission. For senior hires, confidential backchannel checks need care; the executive search screening questions page covers the etiquette.
Handling the dynamic in the room
- Open plainly. "I'm not a specialist in your area, so I'll ask you to explain some decisions in plain terms, and [name] will go deeper on the technical side."
- Keep control of time. Tell them the plan for the hour and when they will get to ask questions. Senior candidates respect a well-run interview.
- Answer their questions honestly. They will ask about budget, authority and your plans. Vague answers here lose the strongest candidates.
- Do not pretend. If you do not understand an answer, say so and ask again. Nodding along is how you end up hiring on charisma.
- Score alone, straight after. An impressive conversation is not evidence; what you wrote down is.
Questions people ask
Should I admit to the candidate that I don't know their field?
Yes, briefly and without apology. Saying you are not a specialist and will ask them to explain their decisions in plain terms sets up the most useful part of the interview: whether they can make expert work understandable to the people they will work with.
Who can assess technical depth if I can't?
A trusted practitioner from elsewhere in the organization, a paid advisor, or a former colleague with the expertise, given a clear brief and a scorecard. Keep them to the areas you cannot judge, and make the hiring decision yourself.
What if the candidate seems to be interviewing me instead?
Senior candidates should interview you; they are deciding whether to work for you. Answer honestly, then bring the conversation back: tell them you will leave time at the end for all their questions, and that you want to use the next half hour on their experience.
How do I stop being impressed by a big-company resume?
Separate the company's results from the candidate's. For every achievement, ask what they personally decided, what the team did, and what would have happened without them. Brand names describe where someone worked, not what they did there.