Let's be real: Writing a long job description full of wish list items is easy.
Assessing those same capabilities in a real human being? That's a whole different beast.

Take a look at this actual assessment takeoff from a client hiring a superintendent for high-end residential construction:

  • Project & Site Management – Full-time, on-site coordination of trades and teams.
  • Scheduling & Coordination – Build and run a CPM schedule.
  • Quality Control & Compliance – Hold the line on architecture, code, and OSHA.
  • Safety & Risk Management – Proactive site safety management.
  • Financial & Budgeting Knowledge – Track costs, code labor, manage budgets.
  • Technical Expertise – MEP fluency in custom homebuilding.
  • Problem-Solving & Decision-Making – On-the-fly fixes and warranty issues.
  • Communication & Stakeholder Management – Subcontractor, team, and client alignment.
  • Technology Proficiency – Excel, Dropbox, file management.
  • That's nine heavy categories, each with real weight.

And most companies try to size that up over… a couple of hours of meetings?

The Wish List Trap

We see it all the time:
Companies pour time into job descriptions that look like a contractor's Christmas list.
But then they walk into interviews with no game plan to assess those capabilities.

No assigned lanes.
No structured questions.
No coordination between interviewers.
No feedback process that actually checks whether these skills were covered.

So what happens?

You think you hired someone great, then six months later you're wondering why the schedule is blown, the team is frustrated, and you're knee-deep in warranty work.

We Can't Help the Ignorantly Proud

Here's the hard truth:

We can't help interview teams who won't admit they don't know how to assess.

If your team thinks just having the title of “Project Executive” or “VP of Ops” magically makes them great interviewers, And they resist structure or strategy, You're going to keep spinning your wheels.

You can't teach someone who's proud of not knowing.
That's not humility. That's a liability.

What Interviewing Should Look Like

1. Assign Accountability by Skillset
Each interviewer owns a slice of the pie.
Give your PM the scheduling questions. Let your GM dig into budget handling.
Don't double up. Don't wing it. Assign lanes.

2. Use Structured Interview Strategy
Freewheeling interviews are charming until they fail.
We help teams build real assessment strategies:
→ What questions reveal skill depth?
→ What observable behaviors are you looking for?
→ How do you calibrate “good enough” vs. “rockstar”?

3. Collect Feedback That Drives Decisions
Not just “thumbs up” or “gut feel.”
Real, written feedback mapped to job criteria.
That's how you avoid hiring someone just because they “seemed confident.”

Interviewing Isn't Just Talking, It's Testing

Think of it like a jobsite inspection.
If you don't check every system, every detail, every safety requirement…
You're signing off on risk.

Interviewing is the same.
It's not about getting along with the candidate. It's about verifying they can do the job you need done.
And that takes more than a few casual conversations.

Build an Interview System That Works

If you want hires who actually perform, stop leaving interviews to chance.
Let us help you build a system that matches the complexity of the role.

You deserve a team you can count on. Let's help you build it.

You've got this.

Questions, answered

The short version.

Why do detailed job descriptions still produce bad hires?
Because writing a wish list is easy and assessing it in a real human is not. A superintendent role can carry nine heavy assessment categories, from CPM scheduling to MEP fluency to budget tracking, and most companies try to size all of that up in a couple hours of unstructured meetings. With no assigned lanes, no structured questions, and no feedback process, you think you hired someone great until the schedule blows up six months later.
How should a hiring team structure interviews for a complex construction role?
Three moves: assign accountability by skillset so each interviewer owns a slice, such as the PM taking scheduling and the GM digging into budgets; use a structured strategy that defines which questions reveal skill depth, what observable behaviors to look for, and how to calibrate good enough versus rockstar; and collect real written feedback mapped to job criteria instead of thumbs up or gut feel, using a disciplined interview feedback system. That is how you avoid hiring someone just because they seemed confident.
Is interviewing really a skill, or can any senior leader do it?
It is a skill, and a title does not confer it. A Project Executive or VP of Ops is not automatically a great interviewer, and teams that resist structure while assuming their titles carry them will keep spinning their wheels. Pride in not knowing how to assess is not humility; it is a liability.
What is the right mindset for interviewing a candidate?
Treat it like a jobsite inspection: if you do not check every system, every detail, and every safety requirement, you are signing off on risk. Interviewing is testing, not just talking. The goal is not getting along with the candidate but verifying they can do the job you need done, and that takes more than a few casual conversations.