A candidate can give an excellent interview answer and still leave us with very little evidence about how they actually work.
Strong communication is not a problem. For senior and executive candidates, the ability to structure experience clearly and communicate professionally is often part of what we should expect.
The problem begins when the quality of the answer becomes the quality of the assessment.
A candidate says they work well under pressure, take ownership, collaborate effectively or handle conflict well.
All of those statements may be completely true.
But none of them is evidence yet.
For me, candidate assessment becomes useful when we stop evaluating how convincing the first answer sounds and start examining how that answer connects to real experience, context and patterns that appear across different professional situations.
Candidate Assessment Works Best When It Starts With Real Experience
My interviews usually start with experience.
I want candidates to explain the projects they have worked on in enough detail for me to understand what they considered complex, what responsibility they personally held, where problems appeared and how they responded.
Questions about pressure, ownership, autonomy, collaboration or initiative then emerge naturally from that experience.
If, for example, a candidate describes a project with a particularly difficult delivery, I may ask how long the team had been operating at increased intensity, when they first realised the deadline could be at risk, what they personally did and what responsibility they took once the situation became difficult.
From there, I may ask:
“When did you first realise there was a problem?”
“Who did you involve at that point, and why?”
“What was under your control in that situation, and what was not?”
“Looking back from today’s distance, would you do anything differently?”
That last question is particularly useful to me.
I do not expect the candidate to invent a mistake simply because I asked whether they would change something.
What interests me is whether they can step outside their original experience, look at it again from some distance and consider whether there is anything they would approach differently today.
If the answer is:
“No, I would make exactly the same decision again,”
that is neither a good nor a bad answer by itself. I want to understand why.
If the candidate says:
“I would involve the CTO earlier today because I spent too long trying to resolve the problem inside my own team,”
I learned something beyond the original project story.
I can see that the candidate is able to reconsider their own decision, recognise its limits and translate the experience into a possible adjustment for the future.
This also gives the interview a natural flow.
I do not interrupt a project discussion with a generic question about pressure simply because “working under pressure” is the next item on an interview checklist.
The question grows out of something the candidate has already experienced, which means both of us understand why we are exploring it.
When an interviewer moves mechanically through questions such as:
“How do you work under pressure?”
“Are you responsible?”
“How do you resolve conflict?”
“Are you a team player?”
the conversation can easily become a sequence of predictable questions followed by predictable answers.
At the end, the interviewer may have checked many boxes while still understanding very little about the person in front of them.
I find it much more useful to follow the candidate’s actual professional experience and deepen the areas that matter for the role.
The psychological layer of the assessment does not need to appear as a separate block of questions.
It emerges through the way we explore real professional situations together.
The Most Informative Moment Is Often What Changes When We Go Deeper
Several years ago, I was assessing a candidate for a C-level position.
The candidate was exceptionally well prepared.
For roughly the first twenty minutes, the interview was almost flawless. The answers were structured, the communication was professional and the experience was presented extremely well.
For a candidate at that level, none of this was unusual. Strong professional communication was something I would expect.
Then I asked why they were considering leaving their current company.
The first answer again sounded completely reasonable.
The scope of the candidate’s responsibilities had changed after a colleague returned from leave, and the candidate wanted a broader role.
That could have been the end of the answer.
But something in the communication changed while the candidate was explaining it.
The tone became noticeably sharper.
That change was not evidence that the candidate was hiding something, nor was it enough for me to form a conclusion.
It simply gave me a reason to stay with the subject for longer.
I asked what had specifically changed after the colleague returned, how responsibilities had been divided before and after that point, what the candidate had expected to happen with their own role and how the company had explained its decision.
During that exploration, a significant piece of information appeared that had not been present in the original answer.
The colleague had received a promotion that the candidate had expected to receive.
From that point onward, the conversation changed substantially.
What had initially been presented as a relatively neutral change in workload became a long and highly negative discussion about the company, colleagues and the people responsible for the decision.
The problem for me was not that the candidate was angry.
People can have completely legitimate reasons to feel angry, disappointed or unfairly treated by an employer.
The professionally relevant question was what happened to that emotion inside the context we were in.
This was an interview for a C-level position.
At that level, I would expect someone to be able to discuss an unpleasant experience, disagreement or perceived injustice while maintaining enough professional self-regulation to explain what happened, what their own role in the situation was and what they learned from it.
I do not expect an absence of emotion.
I do expect an ability to place that emotion inside the professional context.
In this case, one follow-up question opened almost twenty minutes of increasingly aggressive and dismissive commentary about people in the organisation.
That was not enough for me to diagnose the candidate or define their personality.
It was enough to change my assessment hypothesis and give me several areas that needed further exploration: how the candidate responds to frustration, how they relate to authority, what happens when recognition does not match their expectations and how they understand their own role when another person makes a decision they strongly disagree with.
If I had stopped at the first, very well-formulated answer about a “change in scope”, all of that information would have remained invisible.
The Problem Is Not a Good Answer. It Is Believing It Too Soon
A polished answer, professional communication and the ability to present experience clearly are advantages.
The problem begins when we allow the quality of communication to become evidence for areas we have not actually tested.
The candidate says:
“I am very responsible.”
We record: responsible.
They say:
“I always respect deadlines.”
We record: reliable.
They say:
“I work very well under pressure.”
We record: resilient.
But what we actually have are three statements the candidate has made about themselves.
Not three pieces of evidence.
This is also why I do not believe much in universal sets of interview questions that are asked in exactly the same order to every candidate without enough consideration of what each question is supposed to tell us.
Some questions survive simply because they have been asked in interviews for years.
“Where do you see yourself in five years?” is a good example.
For senior and executive candidates, professional development rarely follows a neat five-year calendar.
Someone may know that they want VP or C-level responsibility, a broader business scope or a different type of ownership.
But the right opportunity may appear in one year, three years or five.
I find it much more useful to understand the next professional cycle a person wants to complete than to force that development into an arbitrary period.
The purpose of a good interview is not to invent increasingly unusual questions that candidates cannot prepare for.
It is to understand what we are trying to assess and then test the candidate’s answers deeply enough to know what they actually mean.
Consistency Comes From Different Situations, Not Repeated Questions
If I ask:
“Are you responsible?”
and then continue with:
“Do you respect deadlines?”
“Can your colleagues rely on you?”
“Do you always finish what you start?”
I may easily receive four positive answers.
But I have not tested responsibility four times.
I have simply given the candidate four opportunities to provide a socially desirable answer.
For me, consistency means seeing the same professional theme through different real situations.
I can explore responsibility through a project the candidate led, a problem that escalated, their relationship with a manager, a situation in which they lacked domain knowledge, an unsuccessful delivery or a moment when somebody else made a mistake.
The questions are different in content.
The underlying process I am observing may be the same.
This is also where I separate several layers of information that are easy to collapse into one.
First, what actually happened: the situation, the candidate’s actions and the observable outcome.
Second, how the candidate interprets that experience. What do words such as “difficult”, “intense”, “high responsibility”, “bad manager” or “autonomy” mean to them?
Third, how that context compares with the reality of the role and organisation they may be joining.
And finally, what hypothesis, if any, I still need to test.
That third layer is particularly important when assessing seniority.
A candidate’s subjective experience should be taken seriously.
If someone tells me that a particular project was extremely intense for them, I have no reason to tell them that it was not.
But I still need to understand what that intensity actually consisted of and how it compares with the level of complexity that may be normal in companies similar to the client’s.
Someone can genuinely experience a project as extremely demanding even though, in the environment they are considering joining, the same level of pressure, scope or responsibility would be relatively normal.
The problem is not that the candidate found it difficult.
The potential problem is a lack of awareness of that difference.
Strong senior candidates often show much more precise calibration.
They may say:
“That was the most intense project I had led at that point in my career, although I know it was not particularly large by industry standards.”
Or:
“Technically it was not the most complex product, but it was demanding for me because it was the first time I was personally responsible for the client relationship.”
Those answers tell me much more than the words “complex” or “intense” on their own.
A candidate does not need to have worked on the largest project in the industry.
But seniority often includes understanding the real scale of what you have done and your own position within that reality.
This is one of the strongest Gestalt influences on the way I conduct recruitment interviews.
I do not try to define a person from a single statement.
I follow how they approach similar professional situations across different contexts, while continuously separating observation from interpretation and interpretation from a hypothesis that still needs to be tested.
For Technical Interviewers and CEOs, Better Assessment Starts With Better Follow-Up
If you are a technical interviewer or CEO hiring a senior developer, architect, Engineering Manager or another key professional, you do not need to be a psychologist to conduct a better assessment.
There is one principle that can already make a significant difference:
Do not allow the quality of the first answer to finish the assessment of an area that matters to you.
If ownership is critical for the role, do not only ask:
“Do you take ownership?”
Take a project the candidate has already described and explore where their ownership started and where it ended.
If the role requires a high level of autonomy, do not only ask:
“Do you like working independently?”
Ask what the candidate did the last time they did not have enough information to continue.
Who did they ask?
How long did they try to resolve the situation themselves?
When did they escalate?
How did they decide that it was time to involve someone else?
If collaboration with business stakeholders matters, do not only ask for an example of “good communication”.
Ask about a situation in which the candidate strongly disagreed with a stakeholder and follow what happened next.
A technical interviewer does not need to know Gestalt methodology.
But if they know what they are trying to test and stay with the candidate’s concrete experience long enough, they are much less likely to hire the person who performed best in the interview instead of the person who best fits the reality of the role.
This has a very practical business consequence.
If a company evaluates candidates primarily through the quality of their first answers, the process naturally rewards people who are strongest at the interview format.
That is not necessarily the same person who will perform best in the job.
A company does not need someone who can give the most convincing answer about ownership.
It needs someone whose previous behaviour shows a level of ownership that matches what the role will actually require.
It does not need someone who knows how a good answer about conflict is supposed to sound.
It needs someone whose way of handling disagreement is compatible with the responsibility, team and organisational context they are about to enter.
A Good Interview Should Help Us Understand What Happens After the Interview Ends
No recruitment assessment can predict human behaviour with certainty.
Context changes.
A different leader can bring out very different behaviour.
A different organisation may allow someone to perform extremely well after they struggled in a previous environment.
One difficult event does not define a candidate.
An emotional reaction during an interview is not a diagnosis.
And a recruitment interview is not psychotherapy.
The objective is much more practical.
It is to reduce the number of untested assumptions on which the company makes its hiring decision.
The more senior the role, the more expensive those assumptions can become.
A candidate who communicates exceptionally well may deserve the excellent impression they create.
But the purpose of candidate assessment is not to determine who is best at interviewing.
It is to understand whether what the candidate says is supported by the way they have previously made decisions, taken responsibility, solved problems, learned from experience and worked with other people.
That is why the first answer is rarely the most interesting one for me.
Much more often, the useful part of the interview begins with a simple follow-up:
“Could you walk me through what actually happened there in a little more detail?”