What Construction Site Manager Interviews Actually Test

Who actually interviews you

For most site manager roles, the person leading the interview is whoever you'd report to on the job — usually a contracts manager, sometimes a project director on a larger scheme. HR or a recruiter might run a first-stage screening call to check your CSCS card level, SMSTS or SSSTS certificate, right-to-work status and salary expectations, but they are rarely the ones deciding whether you get the job. That decision sits with someone who has run sites themselves and will be checking whether your answers hold up against their own experience of a live build.

On larger contractors (main contractor or Tier 1 work), you may also meet a pre-construction or planning lead, particularly if the role involves handover from design into build. Some firms add a second interview that's actually a site visit — you walk a live or recently completed job with the panel and talk through what you notice. That stage is not a formality. It's where a lot of hiring decisions actually get made, because it's hard to fake site sense when you're standing in front of an unpropped opening or a scaffold tag that's out of date.

The technical part: what gets put in front of you

Many interviews for this role include some form of practical or technical assessment, not just conversation. What that looks like varies by employer size and sector (residential, commercial fit-out, groundworks, infrastructure), but common formats include:

• A set of drawings or a programme extract. You might be asked to look at an Asta Powerproject or Microsoft Project printout and identify the critical path, or spot a sequencing error — say, second fix starting before first fix M&E is signed off.
• A RAMS document to review. You're handed a subcontractor's risk assessment and method statement and asked what's missing or wrong. This is a direct test of whether you actually read RAMS properly rather than rubber-stamping them.
• A defects or snagging scenario. You might be shown a snagging list or asked how you'd structure one ahead of practical completion, including how you'd track it against the defects liability period.
• A site walk. If it's stage two, expect to be asked to point out hazards, check permit-to-work compliance, or comment on housekeeping and material storage as you go.

If there's no technical stage at all, treat that as information — it usually means the employer is hiring on relationships and references rather than testing competence directly, which is worth knowing either way.

The questions that are actually testing you

A lot of what sounds like small talk in these interviews is not. Here's what specific questions are really probing, and what a shallow answer to each one sounds like.

"Tell me about a time you stopped work for a safety reason." This is testing whether you have actually exercised authority under CDM 2015, not whether you know the phrase "safety first." A real answer names what stopped the work — an unsafe scaffold tag, a subcontractor working at height without edge protection, a permit that hadn't been signed — and what happened after: who you told, whether it went into the site diary, whether it triggered a RIDDOR consideration, and how work resumed. A shallow answer is "I always put safety first and would never let unsafe work continue," with no specific incident, no document trail, no named outcome.

"A subcontractor's RAMS doesn't match what they're doing on site. What do you do?" This tests document control and whether you actually cross-check RAMS against site reality rather than filing them. A competent answer talks about stopping the specific operation, reviewing the RAMS with the subcontractor's supervisor, and either amending the document or issuing a formal instruction before work continues — and says something about who signs it off. A shallow answer skips straight to "I'd have a conversation with them" with no mention of the paperwork or the stop.

"You're two weeks behind on the programme because of a design query. How do you recover it?" This is testing programme literacy — do you actually understand float, critical path and resequencing, or do you just know the word "programme"? A real answer talks about which trades can run in parallel, whether the delay affects the critical path or sits in float, whether it's grounds for an extension of time under the contract (JCT or NEC, depending on the job), and how you'd communicate that to the client or contracts manager. A shallow answer is "I'd push the team to work harder and catch up," with no mention of sequencing, contract mechanism or who else needs to know.

"How do you handle a variation that hasn't been priced yet?" This tests whether you understand your own authority and the commercial side of the job, or whether you treat commercial matters as someone else's problem entirely. A competent site manager knows roughly where the line sits between instructing minor changes to keep the job moving and escalating anything with cost or time implications to the quantity surveyor before work starts. A shallow answer either claims full authority they don't have, or says "that's not my area" — both signal the same gap.

"Walk me through how you run a subcontractor package from start to finish." This one is deliberately open because it lets a weak candidate talk in generalities. A strong answer names the actual mechanics: pre-start meeting, checking the subcontractor's own RAMS and insurances, induction, toolbox talks, progress tracking against the programme, quality checks before sign-off, and snagging before they leave site. If the answer is "I make sure they know what they're doing and check in regularly," that's the shallow version — it could describe almost any supervisory job, and the interviewer knows it.

What a shallow answer sounds like in general

Across all of these, the tell is the same: language that would survive being said by someone who has never actually run a site. "I'm a strong communicator," "I always put safety first," "I keep the team motivated" — none of these are wrong, but none of them are specific to this job either. A real site manager's answer has a document in it (RAMS, permit, programme, snagging list, site diary), a named party (subcontractor, QS, building control, NHBC inspector), and a mechanism (stop work, escalate, resequence, instruct). If your answer doesn't touch at least one of those three things, it's probably too shallow for the person asking.

The reverse is also worth knowing: interviewers on this side of the table are often not great at asking clean questions. You may get a rambling scenario or a question that's really three questions stacked together. It's fine to ask them to clarify which part they want you to address, or to say "can I answer that in terms of a specific job I ran?" before launching into detail. That's not evasive — it shows you think in terms of real projects rather than talking points.

What to do before you go in

Pull the RAMS, programme and snagging documents from your last two jobs and re-read them the night before, specifically so the vocabulary and the sequence of events are fresh, not reconstructed on the spot. If the advert names a specific contract form (JCT, NEC), a specific accreditation (SMSTS, NEBOSH, CSCS black card), or a specific sector (groundworks, fit-out, infrastructure), have one real example ready that uses that exact vocabulary — not a generic story adapted to fit. If you're not sure what a specific advert is actually asking for versus what it's padding with boilerplate, jobmarket.pro reads the advert in full and tells you where your experience matches and where it doesn't, before you apply.