Good construction candidates are not applying because the posting is working exactly as designed. It reaches people who are actively looking, and the strongest project managers and estimators are not. Every extra requirement, hidden salary and interview stage narrows the pool further in the wrong direction.

Fourteen bullet points under “Requirements.” A salary line that reads “commensurate with experience.” A five-stage interview process for a project manager who is currently running $30M of work and does not need you.

The posting is not broken. It is a filter, and it is filtering precisely as built. The problem is what it selects for.

Why are good construction candidates not applying?

Because they are not looking. A posting can only reach people who are actively searching, and the strongest project managers and chief estimators are running live work, are known in their region, and move when someone they trust brings them something specific.

This is the structural point and everything else in this article follows from it. Job postings are a supply-side tool for a liquid market. Senior construction hiring is not a liquid market, and in a single metro like Charlotte, Tampa or Austin the qualified pool for a given seat is often small enough to list. The AGC has for years reported that United States contractors struggle to fill salaried positions, with similar workforce findings from ABC. The BLS turnover series tracks the same pressure. Selah runs confidential searches for a senior project manager.

So the pool a posting reaches is made up of three groups: people between jobs, people at firms that are struggling, and people who are unhappy for reasons you have not yet discovered. Some excellent candidates sit in those groups. But the person you actually want, the one delivering well at a stable competitor, is in none of them.

There is a trust problem layered on top, and construction is among the sectors worst affected by postings that never lead to a hire. Think about what that trains. A project manager spends an evening tailoring a resume, writes the cover note, clears the recruiter call for a Tuesday lunch break, and hears nothing for five weeks. Twice. The third posting he sees, from a firm he has never dealt with, is competing against that memory. He does not conclude that your role is fake. He concludes it is not worth the evening.

What is your posting actually screening out?

The requirements list. Every additional “must have” narrows the pool, and the ones that get added are usually proxies rather than the thing you actually need, which means you are filtering on the wrong axis while feeling rigorous.

Look at what a standard posting does, line by line:

  • The fourteen-bullet requirements list. Candidates with options read it as a wish list written by committee and move on. Candidates with fewer options apply anyway. The list selects for persistence, not capability.
  • A degree requirement on an experience-led role. For a project manager with fifteen years and a delivery record, a degree line is a reason not to bother, and it screens out the field-progressed people who are often the strongest.
  • “Commensurate with experience.” A person currently earning well will not spend an hour applying to discover your range is fifteen thousand dollars short. Withholding the range costs you the candidates with alternatives first.
  • Software lists. Naming five platforms as required screens on tooling, which is learnable, rather than on judgment, which is not.
  • “Self-starter, team player, detail-oriented.” These describe nobody and exclude nobody. They are filler where the actual job should be.

What is usually missing is the only thing a strong candidate wants: what the job actually is. Project size and mix, delivery method, who they report to, what is broken and needs fixing, and why the seat is open. On senior seats the deeper issue is that postings reach the wrong population entirely.

That last one matters more than firms expect. A senior candidate reads an unexplained vacancy as risk.

Does your hiring process itself cost you candidates?

Yes, and it is measured differently than you think. A candidate running a live job treats your process as evidence of how you operate. Five stages over seven weeks tells them your decisions are slow, which is a statement about the firm rather than about the role.

Compare what each side reads into the same process:

Your processWhat you intendWhat a working candidate reads
Five interview stagesThorough diligenceYou cannot decide, or nobody owns this hire
Three weeks between stagesCoordinating schedulesWe are not a priority
Salary undisclosed until stage fourNegotiating positionYou may waste my time entirely
Panel of eightInclusive decisionNobody here is accountable
A test estimate or takeoff exerciseVerifying skillFree work, from a person who has a job

None of that means you should lower the bar. It means the bar should be applied in a way that respects a person who is currently employed and busy. Three stages, decided in two weeks, with the range stated up front, will out-recruit a more thorough process almost every time.

Two hiring processes, stages and weeks Comparison, Two hiring processes, stages and weeks: Interview stages Typical process 5 versus Faster process 3; Weeks to a decision Typical process 7 versus Faster process 2. Two hiring processes, stages and weeks Three stages decided in two weeks, with the range stated up front, out-recruits a five-stage,seven-week process almost every time. Typical process vs Faster process Interview stages 5 3 Weeks to a decision 7 2 Source: Worked example in this section
Three stages decided in two weeks, with the range stated up front, out-recruits a five-stage, seven-week process almost every time.

How do you reach construction candidates who are not looking?

Direct approach, with a specific reason for approaching that specific person. It works because it inverts the assumption: instead of waiting for the small set of people who are looking, it reaches the much larger set who are performing well and would consider the right move.

This is the practical difference between advertising and search, and it is covered more fully in what a construction executive search firm actually does. The short version: a posting is a broadcast to available people, and search is a targeted approach to unavailable ones.

For a subset of roles, advertising is not merely ineffective but actively harmful. If you are replacing a project manager who is still in the seat, or bringing in preconstruction leadership before a bid without signaling that estimating is exposed, the posting itself is the risk. That is confidential executive search for mandates that cannot be publicly posted, and the reason the role is unpostable has nothing to do with recruiting technique.

Three things that improve outcomes whether or not you use a search firm:

  • State the range. You will lose fewer good candidates to a number they never saw than to a number they disagreed with.
  • Explain why the seat is open. Growth, a departure, a new office. Silence reads as trouble.
  • Cut a stage. Whichever one exists because it always has.

To be clear about where this does not apply: for assistant project managers, project engineers, coordinators and early-career estimating roles, postings work well. Those markets are liquid, applicants are strong, and paying a search fee would be waste. The argument here is specific to senior roles where the market is thin and the best people are not in it.

Your posting is not failing. It is succeeding at reaching available people, and then you are surprised that the available people are not the ones you wanted. The fix is not better copy. It is deciding whether the seat is one you should be advertising at all.

Not sure which category your open seat falls into? Ask us, and we will tell you if a posting is the right answer.

Sources and further reading

  • AGC workforce survey reporting on salaried hiring difficulty
  • ABC construction workforce data
  • BLS job openings and labor turnover survey
  • BLS occupational data for construction managers