Key findings
- A job description describes a role; it does not automatically define the hiring decision.
- Candidate requirements should be connected to the business outcome they are intended to support.
- The reason a role exists now can materially change the profile required, even when the job title remains the same.
- Market evidence should test the assumptions made during role definition without turning the search into an constantly moving specification.
- Better role definition creates a stronger basis for structured candidate evaluation later in the search.
A job description describes a position.
A hiring decision defines what the organization actually needs from the person occupying it.
Confusing the two can make an executive search look precise while leaving the most important questions unanswered.
“A job description describes a position. A hiring decision defines what the organization actually needs from the person occupying it.”
A job description can be accurate and still be insufficient
Most executive searches begin with a document.
It contains a title, responsibilities, reporting lines, required experience, preferred qualifications and perhaps a list of personal characteristics.
The document may be detailed. It may have been reviewed by HR, the hiring manager and headquarters. It may accurately describe the position as it exists today.
And it can still leave the central hiring question unresolved.
A job description primarily describes a role.
A hiring decision needs to define why the organization is hiring, what it expects to change because of that hire and what evidence should ultimately make one candidate more convincing than another.
Those are different questions.
For routine positions, the distinction may matter less. For leadership, commercial and specialized technical roles, it can determine the entire quality of the search.
The problem begins when inherited requirements become search criteria
Job descriptions accumulate history.
Requirements are often carried forward because the previous person had them, because another company uses them, because they appeared in an older version of the role or simply because they sound reasonable.
Five years of experience becomes eight.
A particular industry becomes mandatory.
A specific degree remains listed.
A certain job title becomes the assumed benchmark.
None of these requirements is necessarily wrong.
The problem is that they can enter the search without being connected to the actual business decision.
A requirement should not be important merely because it appears in the document.
It should be important because it helps explain why a candidate is likely to succeed in the specific context of the organization.
That distinction changes the search.
Start with why the role exists now
Before defining the candidate, define the situation.
Why is the organization hiring this person now?
Is the role replacing someone?
Has the business grown beyond the existing structure?
Is the company entering Mexico?
Does a founder need to delegate responsibility?
Does the organization need stronger commercial development?
Has the technical complexity of the operation increased?
Does headquarters need stronger local leadership?
The same job title can represent fundamentally different hiring decisions depending on the answer.
A Sales Manager hired to open a market is not the same profile as a Sales Manager hired to manage an established customer base.
A Plant Manager brought into a stable operation is not necessarily the same person required to transform an underperforming site.
A Service Manager replacing an operational manager may require a different profile if the organization also wants the role to assume broader leadership or commercial responsibility.
The position title has not necessarily changed.
The hiring decision has.
Define what should be different after the hire
A useful hiring discussion therefore moves beyond responsibilities and asks a more demanding question:
What should be different twelve months after this person joins?
The answer does not need to become an artificial list of performance metrics.
But it should clarify the intended contribution of the role.
Perhaps the new leader needs to build a team.
Perhaps customer relationships need to become more structured.
Perhaps headquarters needs better visibility into the Mexican operation.
Perhaps the commercial pipeline needs to become less dependent on one individual.
Perhaps processes that currently exist informally need to become repeatable.
Perhaps a technical organization needs stronger leadership without losing its operational depth.
These outcomes create a much stronger basis for defining candidate requirements.
They also make it easier to distinguish between experience that is genuinely relevant and experience that merely looks similar on paper.
Separate requirements from assumptions
Once the business context is clear, the traditional candidate specification can be examined more critically.
Some requirements will remain essential.
Others may become preferences.
And some may disappear entirely.
Consider industry experience.
For certain positions, exact industry knowledge may be critical because the technical environment, customer relationships or regulatory requirements are difficult to learn quickly.
For another position, insisting on an exact industry match may unnecessarily reduce the talent market when adjacent sectors contain candidates with highly transferable experience.
The same applies to company size, years of experience, educational background, previous titles and international exposure.
The objective is not to remove requirements.
It is to understand what each requirement is supposed to predict.
If the connection between a requirement and successful performance cannot be explained, it deserves to be questioned before it restricts the search.
The candidate market can also test the definition
Role definition should happen before the search.
But it should not become disconnected from the market.
Once candidate conversations begin, the market provides information.
Perhaps the expected combination of capabilities exists only at a substantially different compensation level.
Perhaps candidates with the desired technical background rarely have the commercial responsibility assumed in the specification.
Perhaps the strongest potential candidates come from an adjacent industry rather than direct competitors.
Perhaps a requirement initially considered essential turns out to exclude otherwise compelling profiles without adding meaningful predictive value.
This does not mean changing the profile every time an interesting candidate appears.
It means treating the search as a source of evidence.
A strong search tests the assumptions made at the beginning against the reality of the available talent market.
Better definition creates better evaluation
The quality of candidate evaluation depends on the quality of the question being evaluated.
If success was never clearly defined, interviewers naturally fall back on proxies:
Do I like this person?
Have they worked for a company I recognize?
Do they have the right title?
How many years of experience do they have?
Have they worked in exactly the same industry?
These signals can be relevant, but they are not a substitute for a clear decision framework.
When the organization has defined the business context, intended contribution and genuinely important capabilities, candidate conversations can become more specific.
Instead of asking whether someone is generally experienced, the interview can examine evidence against what the organization actually needs.
That makes comparison more structured and reduces the influence of assumptions that were never explicitly discussed.
Search quality begins before sourcing
Executive search is often judged by what happens after the market is approached:
How many candidates were identified?
How quickly was the shortlist delivered?
How strong were the profiles?
Those questions matter.
But they assume that the organization is searching for the right thing.
If the underlying hiring decision is unclear, excellent sourcing can simply produce a well-executed search against the wrong specification.
“If the underlying hiring decision is unclear, excellent sourcing can simply produce a well-executed search against the wrong specification.”
This is why the beginning of an executive search deserves more attention.
Before searching for candidates, the organization should be able to explain:
Why does this role exist now?
What needs to change because of the hire?
What will the person actually be responsible for?
Which capabilities are essential to achieving that?
Which requirements are preferences rather than necessities?
What evidence would make the organization confident in one candidate over another?
A job description can contribute to those answers.
It cannot replace them.
Methodology Note
Within the Atlas Method™, role definition takes place before candidate sourcing.
The Discovery Experience™ examines the business context behind the hiring need. The Search Blueprint™ then translates that context into a structured definition of the mandate, including the role’s purpose, success conditions, critical capabilities and relevant search parameters.
The objective is not to create a longer job description. It is to establish a clearer basis for the search and the hiring decision that follows.