How to measure hire feasibility

One of the most uncomfortable conversations in Recruiting isn't about salary. It's about feasibility.

Is it actually possible to fill this role in the timeline and conditions we're defining?

Often the implicit answer is "yes, obviously." But the answer isn't boolean. And months later, frustration shows up: the market "isn't responding," the hiring manager "can't find the profile," the business "needed this yesterday."

Feasibility isn't a gut feeling. It's an analysis. And there's no universal rule: every company has to build its own based on its business model, urgency, and positioning.

But there are variables you can't ignore.

1. Do you have 100% ownership of the hire?

Hiring for your own company isn't the same as hiring when you depend on a third party.

Key questions:

  • Is the final decision internal?
  • Can you adjust requirements, budget, or process if the market doesn't respond?
  • Or do you depend on external client approval?

If the hire depends on clients (consultancies, software factories, BPOs), the level of control changes radically.

And if you don't have exclusivity, feasibility drops even further. You're competing for the same talent against other companies also presenting candidates to the same client. Speed and aggressiveness, as well as your ability to reach the market, become more decisive.

The first rule of feasibility is understanding how much real control you have over the equation.

2. Role difficulty level: real talent supply

This is where simplification usually appears: "it's a hard profile."

What does hard mean?

  • How many people with that stack actually exist in the market?
  • In which geographies?
  • At what seniority?
  • What level of specialization does it require?

A role can have little available talent, but that doesn't automatically mean low feasibility.

The critical variable is the relationship between supply and demand.

3. Market demand: the other side of the equation

Having little talent doesn't always mean high competition for that talent.

There are ultra-specific roles with low candidate volume—but also low demand. That can make the hire perfectly viable.

On the other hand, there are profiles with thousands of people available and still extremely high demand (for example, certain tech profiles during expansion periods).

Feasibility plays out at the intersection:

  • Low talent + high demand → low feasibility
  • Low talent + low demand → feasible
  • High talent + high demand → depends on the offer
  • High talent + low demand → high feasibility

Without market analysis, any estimate is optimism.

4. Aging: when do you need this?

Every req has a clock, even when nobody makes it explicit.

  • Is there a real deadline?
  • Does the business critically depend on this hire?
  • What happens if it fills 30 days later than expected?

Some roles can wait. Others have an expiration date. The more rigid the deadline, the less room for negotiation and the less tolerance for iteration.

Feasibility isn't just "does the talent exist." It's whether the talent exists in the time available.

5. Process vs. value proposition

This variable often gets ignored.

How long and tedious is your process relative to the strength of your offer?

  • How many interviews?
  • How long does each feedback take?
  • Are there extensive tests?
  • Are there multiple redundant rounds?

If your process is demanding but your employer brand and conditions aren't particularly attractive, feasibility decreases.

The market doesn't wait.

A long process can be reasonable if the brand is strong, the challenge is compelling, and compensation holds up. But if there's no clear differentiator, friction works against you.

Build your own feasibility rule

Every company should define a simple matrix that combines:

  • Level of control (ownership / client dependency)
  • General conditions (salary, work model, etc.)
  • Exclusivity (if applicable)
  • Talent supply
  • Market demand
  • Urgency (real aging)
  • Process rigor vs. offer attractiveness
  • MOST IMPORTANT: business priority

Not to discourage reqs. To adjust expectations and strategy from the start.

Because often the problem isn't that Recruiting "can't close." It's that the business assumed a feasibility that was never validated.

Next time you open a req, before posting the job, ask yourself an uncomfortable question:

Are we evaluating this hire as a wish… or as a real probability?