What Are You Actually Trying to Understand When You Hire Someone?

When you are hiring someone, what are you actually trying to understand?

Their experience? Their knowledge? Their capability? Their personality?

All of these are valuable signals. But they are not interchangeable. Each tells you something different about a candidate, and each requires a different approach to evaluate effectively.

One of the challenges in recruitment is that hiring processes often try to answer all of these questions in the same way. We review a CV, conduct an interview, check references and then make a judgement.

But if we want to make better hiring decisions, we need to be more deliberate about what we are trying to understand and what evidence will actually help us understand it.

Experience tells you what someone has done

Experience is often one of the first things we look at.

How many years have they worked in the industry? What roles have they held? Which businesses have they worked for? What responsibilities have they had?

This information provides useful context. It can tell you what environments someone has been exposed to and the types of challenges they may have encountered.

But experience alone does not necessarily tell you how capable someone is.

Two candidates can have held the same title for the same number of years and have very different levels of capability. One may have continuously developed, taken on increasingly complex challenges and built a deep understanding of their function. The other may have accumulated years without developing to the same degree.

Ten years of experience does not automatically equal ten years of growth.

Knowledge tells you what someone knows

Knowledge is another important part of performance.

Does the candidate understand the principles, processes and technical requirements of their role? Can they explain what good practice looks like? Do they understand why certain decisions are made?

Knowledge can be assessed relatively effectively through technical questions, structured assessments or scenario-based discussions.

But knowing the right answer and being able to apply it are two different things.

A candidate may be able to explain exactly how they would approach a difficult situation in theory but struggle to execute when faced with competing priorities, incomplete information or pressure.

That distinction matters.

Capability tells you what someone can actually do

Capability goes beyond knowing.

It is about whether someone can take their knowledge, experience and judgement and apply them effectively to the demands of the role.

Can they analyse a problem? Make an appropriate decision? Prioritise effectively? Interpret information? Manage complexity? Deliver an outcome?

This is particularly important when hiring for roles where two candidates with similar backgrounds can perform very differently once they are in the job.

Capability is also difficult to judge from a CV alone.

A CV can tell you where someone has worked and what they were responsible for. It cannot necessarily tell you how well they performed those responsibilities.

That is why practical assessments, work samples, case studies and structured capability testing can add another layer of evidence to the hiring process.

Personality tells you how someone is likely to operate

Personality can help you understand how someone approaches their work and interacts with others.

How do they communicate? How do they respond to pressure? Do they naturally prefer structure or flexibility? How do they approach collaboration, decision-making or conflict?

These insights can be valuable, particularly when considered in the context of the role and working environment.

But personality should not become a proxy for capability.

Someone can be highly charismatic and interview exceptionally well without having the technical capability required for the position. Equally, a highly capable candidate may be less polished or immediately engaging in an interview.

When hiring processes rely too heavily on rapport or "gut feel", there is a risk that confidence gets mistaken for competence.

Different questions require different evidence

There is no single assessment method that tells you everything you need to know about a candidate.

A CV can provide evidence of experience.

Technical questions can test knowledge.

Practical or capability assessments can demonstrate whether someone can apply that knowledge.

Structured interviews can explore behaviours, judgement and past performance.

Personality assessments can provide insight into working preferences and tendencies.

References can help validate previous performance and experience.

The strength of a hiring process comes from combining the right sources of evidence.

Start with what you need to know

Before deciding how to assess candidates, start with a simpler question:
What do we actually need to know to make a confident decision about this hire?

If technical capability is critical, test it.

If stakeholder management is essential, explore evidence of it.

If the person needs to operate effectively in highly ambiguous situations, create questions or scenarios that allow them to demonstrate how they would approach that ambiguity.

And if future potential matters more than having followed an identical career path, make sure the hiring process gives candidates an opportunity to demonstrate it.

The objective should not be to collect as much information as possible.

It should be to collect the right evidence.

Because experience, knowledge, capability, personality and potential can all contribute to success.

The key is understanding which ones matter for the role and using the right tools to evaluate them.