Let me be blunt and human about it. I sit in on interviews where two very capable people get along, swap war stories, feel the chemistry, and walk out saying the meeting went great. Then I read the notes and realize there was no interview. There was a pleasant conversation and a gut verdict. That pattern is burning schedules, margins, and trust.

Interviewing is a different craft than building. Doing the work well does not equal diagnosing who can do it well here. When leaders skip structure, they leave the decision to luck and likability. I am frustrated because the fix is not complicated, but it does require discipline.

What I keep seeing in construction interviews

  • The talk is all shop talk. No plan. No lanes. No evidence. No clear expectations.
  • A strong vibe gets treated like a strong signal.
  • Someone says “they can do the job” without ever testing the three things that decide success on site.

Tell the truth. We have all nodded through these meetings. That is not hiring. That is hoping.

Two myths that quietly raise risk

  1. “You will send us good candidates who can do the job and are aligned with our culture.”
    We can attract interest and assess initial fit so you can run a sharp process. We are not a substitute for the leadership and commitment-building work of interviewing and onboarding. If that work is skipped, the hire will wobble.
  2. “Written interview feedback is bureaucratic.”
    It is discipline, like putting change orders in writing. Documentation creates clarity, accountability, and teachable patterns. It prevents selective memory and post-hoc story editing.
“What you see is all there is.”
Daniel Kahneman, Thinking, Fast and Slow

Why strong construction professionals struggle to interview without training

You know the type. The grizzled superintendent who is God's gift to the craft and cannot teach a lick of it. He can build anything and explain almost none of it, because the moves that took him twenty years to learn now feel like breathing. That same blindness sits down in the interview chair. A person who cannot break his own expertise down for an apprentice cannot reliably judge it in a stranger.

  • Curse of knowledge. Experts compress steps and skip fundamentals the role still requires.
  • Self-mirroring. “Feels like me” becomes the standard instead of “complements our team’s gaps.”
  • Unstructured talk. The hour drifts and nobody owns specific outcomes.
  • Conflated proxies. Big logos and years on paper get mistaken for capability in your environment.
  • Halo and horn effects. One memorable moment colors the entire decision.
  • No independent scoring. Group debriefs become consensus theater driven by the loudest voice.

What actually needs testing

  1. Technical expertise in your constraints. Not generic “knows construction,” but how they diagnose and sequence on your project types.
  2. Process discipline. Daily log quality, RFI cadence, change clarity, look-ahead planning.
  3. Performance under pressure. How they operate when the schedule tightens and people are upset.

Culture belongs here, but let us define it honestly. Cosmetics are the vibe when things are smooth. Real culture shows under stress. How people behave when stretched is what they truly believe.

“In complex work, checklists turn memory into discipline.”
Atul Gawande, The Checklist Manifesto

A 60-minute interview blueprint

  • 0–5: Set context. Name the three accountabilities you will test.
  • 5–25: Behavioral investigation. Two stories per accountability. What, why, how, result, and what changed after.
  • 25–45: Scenario exercise. A realistic constraint from your work. Think out loud, make trade-offs, show artifacts.
  • 45–55: Candidate questions. Prioritize job realities, success markers, and integration risks.
  • 55–60: Close with specifics. Next steps and what you will validate in references.

Require private scoring immediately after the interview. Only then compare notes.

A scorecard you can use today

Score 1 to 5 per line. Capture one verbatim quote as evidence.

Technical expertise

  • Diagnoses root causes without coaching
  • Anticipates downstream impacts across trades
  • Converts drawings and specs into field-ready plans

Process discipline

  • Daily log specificity and cadence
  • RFI, submittal, and look-ahead hygiene
  • Change order clarity and documentation

Performance under pressure

  • De-escalates conflict and keeps work moving
  • Rebuilds plan after a critical slip within 24 to 48 hours
  • Communicates up, down, and sideways with steadiness

Compatibility under stress

  • Productive fit with your PM and leadership styles
  • Accepts accountability without excuse
  • Leads with intentional, sincere, kind, competent engagement that moves the team to outcomes

A scenario prompt that reveals thinking

“You inherit a project that is six weeks behind. Two neighbors are angry about noise and parking. A key subcontractor is underperforming and the client wants a monthly photo log that has not been maintained. Walk me through your first ten days. Show how you will get to stable footing, what you will communicate to whom, and what will change by day thirty.”

Ask to see artifacts: a sample look-ahead, a daily log entry, a client update outline. Do not accept hand-waving.

Reference checks tied to what you learned

  • “Describe how they handled a late schedule and what improved within thirty days.”
  • “What patterns did you see in documentation quality and cadence?”
  • “Tell me about a time they de-escalated conflict with a trade or owner’s rep.”
  • “Where did their plan break, and how quickly did they re-plan?”
  • “Under sustained stress, what behaviors showed up repeatedly?”

A word on time

I hear “we do not have time to prep or debrief.” The rework from a bad hire is ten times worse than a one hour prep and a five minute scorecard. Candidates feel it when leaders treat hiring like a drive-by. It communicates future chaos.

Bilateral tools that change the conversation

We use a structured PXT-style conversation to help both sides anticipate what it is like to work together. It surfaces collaboration friction early, which is where culture actually lives. A client told me recently, “I cannot imagine hiring any other way now.”

“Only the paranoid survive.”
Andrew S. Grove

What I want for your team

View hiring as a critical discipline where the future of your projects hangs in the balance. Let structure and accountability do the heavy lifting so your insight actually matters. When leaders take this seriously, they become helpable, and decisions improve fast.

Questions, answered

The short version.

Why are skilled construction professionals often poor interviewers?
Because interviewing is a different craft than building; doing the work well does not equal diagnosing who can do it well here. Experts fall into predictable traps: the curse of knowledge compresses steps the role still requires, self-mirroring makes 'feels like me' the standard, unstructured talk lets the hour drift, big logos get mistaken for capability, one memorable moment colors the whole verdict, and group debriefs become consensus theater without independent scoring.
What should a construction interview test?
Three things that decide success on site: technical expertise within your constraints, meaning how the person diagnoses and sequences on your project types; process discipline, meaning daily log quality, RFI cadence, change clarity, and look-ahead planning; and performance under pressure, meaning how they operate when the schedule tightens and people are upset. Culture belongs in the list too, but define it by how people behave under stress, not the vibe when things are smooth.
How should I structure a 60-minute construction interview?
Use a blueprint: 0 to 5 minutes setting context and naming the three accountabilities you will test; 5 to 25 on behavioral investigation with two stories per accountability; 25 to 45 on a scenario exercise from your real work where the candidate thinks out loud and shows artifacts; 45 to 55 for candidate questions; and 55 to 60 to close with specifics. Then require private scoring immediately after, before anyone compares notes.
Is written interview feedback just bureaucracy?
No, it is discipline, like putting change orders in writing. Documentation creates clarity, accountability, and teachable patterns, and it prevents selective memory and post-hoc story editing. A one-hour prep and a five-minute scorecard cost far less than the rework from a bad hire.
How do I run reference checks that tell me something real?
Tie them to what you learned in the interview. Ask how the person handled a late schedule and what improved within thirty days, what patterns showed up in documentation quality and cadence, when they de-escalated conflict with a trade or owner's rep, where their plan broke and how quickly they re-planned, and what behaviors repeated under sustained stress.