Some construction leaders interview the way other people speed date. They rush through the conversation, barely engage, make a snap call, and tell themselves they were just being efficient. They were too busy to slow down. Their time was too valuable. They could read the person in five minutes anyway.

That instinct is the tell. A hire is a risk decision, and the leader is the underwriter. The quality of the hire is not decided by the candidate pool. It is decided by the depth of judgment the leader brings to the table, and that judgment only goes as deep as the leader's self-awareness. A leader who cannot slow down to see the candidate clearly has usually lost the ability to see himself clearly first. The fix is never a better stack of resumes. It is a leader who owns the underwriting.

Here is what rushing actually buys you.

What the leader skips when the interview is too smooth

When a leader treats hiring as a side task, three habits show up every time:

  • The belief that their calendar is too important to spend real time assessing a person.
  • The assumption that they can figure anyone out in a few minutes.
  • An over-reliance on gut instinct, with structured evaluation and the harder conversations skipped entirely.

I have sat across from leaders who do all three, and the outcome is predictable. They set wrong expectations for both sides. They miss the warning signs that would have stopped a bad hire. They drop good people into the wrong situations and then call the turnover bad luck. And they lose the best leaders to the firms that took the conversation seriously.

The irony is the math. The thirty minutes saved by rushing is nothing against the months and the dollars lost when the hire does not hold.

To rush your hiring process, to not greatly invest in your skill set and perspective for hiring, is like trying to build an organization with balsa wood beams or on an unlevel foundation. It is just difficult to build a company that way.

The hidden costs of a speed-dated hire

You hire people who are not ready for the job. When a leader does not dig into the details, they hire for the experience they assumed was there rather than the experience that was. The new person struggles, underperforms, or leaves.

Too often, our interviews are too smooth. They are too short, they are too shallow. They are not preparing people to understand the complexity they are going to handle.

You set expectations you never actually set. A quick, surface-level interview gives the candidate no real view of the company, the team, or the work. They start the job, hit the reality, and realize it was not what they signed up for. Success is properly set expectations. Failure is improperly set expectations. There is not much in between.

You miss the red flags. A rushed interview does not surface the things that matter: thin accountability, a job-hopping pattern, an inability to work inside your leadership style, a mismatch with the pace and culture of the company. Skipping the deep conversation does not remove those risks. It hides them until they are expensive.

You make the job worse for everyone already there. A bad hire does not stay contained to the org chart. Your best people burn out covering for the underperformer. Morale drops as good employees quietly lose faith in how decisions get made.

How expensive is a project manager mishire? How expensive is a superintendent mishire? How quickly can you lose $100,000 on a project, or a million?

Thirty minutes saved today against months of stress, lost revenue, and cultural damage. That is the trade a rushed interview makes.

Why "too busy" is the wrong answer

Hiring is not a task to delegate to whatever time is left over. It is one of the few decisions a leader makes that compounds. The leader who claims to be too busy for it is making a quiet claim that they can read people without doing the work, and that their schedule this week matters more than the company's health for the next three years. Neither claim survives contact with a real mishire.

Leaders prioritize hiring. Make this your calling. This is something very, very serious to get focused on.

If you are too busy to interview properly, you are too busy to lead.

How to underwrite a hire instead of speed dating one

Block the time the way you block any major decision. If you do not have time to interview properly, you do not have time to hire. Treat the gap as the warning it is.

Define what great looks like before anyone walks in. Most leaders cannot name what they are looking for past a few vague qualifications. Before the first interview, get specific: what success in this role actually looks like, which traits fit the way your company runs, and which problems this person is being hired to solve.

Run a structured process, not a vibe. Gut instinct is not a system, and it does not survive your absence. A repeatable process evaluates people consistently. Each interviewer should own a clear lane of accountability, know how to ask questions that mean something, and write down honest feedback before comparing notes with anyone else.

Use assessments to find your own blind spots, not just theirs. Self-awareness is the first move in good hiring. An instrument like PXT Select shows where a leader and a candidate align and where they do not, which is information most hiring managers never get.

A lot of leaders are like fish in water. If you ask a fish to tell you about the water they live in, they cannot. They do not realize how unique their environment is, or how different competitors operate.

Set expectations that outlast the offer. The work does not end when the offer is accepted. Build an onboarding plan so the new person is not left to figure it out alone. Check in often enough to keep expectations aligned. Treat the hire as an investment you are underwriting, not a transaction you closed.

Do this consistently and you build teams that build companies that build projects. Rush it and you pay the premium later, with interest.

You already know whether your last interview was an underwriting decision or a speed date. The only question is which one the next one will be.