Interviewing a site supervisor: questions that reveal real competence

Most builders hire a site supervisor the way they buy a ute: on the reference, the look of the last job and a feeling about the person. The trouble is that a supervisor’s value shows up on the day something goes wrong. A résumé rarely tells you how someone will behave late on a wet afternoon, when the crane is held up, the frame inspection has not happened and the client is on the phone.

This article gives you scenario questions for a site supervisor interview, with the answer signals that show real competence and the warning signs that a candidate has not run a site properly. It is aimed at supervisors specifically. General hiring, retention and pay questions are a different job, and the links later in the article cover those separately.

Ask each question as a scenario rather than a question about strengths. Ask the candidate to walk you through what they would do, step by step, and listen for what they check before they act. Good supervisors ask questions back. Weak ones jump straight to a fix.

Confirm the licence and the supervision before the first question

Before the interview, check the licence or certificate that the role requires on the official register. The NSW Government guidance on general building work licensing sets out which licences apply to which work. A licence that covers one type of work does not automatically cover the rest of the job, and a photocopy in a candidate’s folder tells you what they wanted you to see, not what is current.

A supervisor who holds a builder licence also carries an annual CPD obligation of their own, and the guide to how NSW builder CPD works explains what that involves. Ask how the candidate keeps their CPD records. A supervisor who is organised about their own licence obligations is more likely to be organised about the site.

Sequencing and the hold point question

The first scenario tests whether the candidate understands that some work cannot proceed until a check has been made. Put it to them plainly: the concrete pump is booked for the morning, the formwork inspection is still outstanding, and the engineer has raised a question about the reinforcing. Ask them to walk you through the next hour and what they tell the client.

A strong answer stops the pour before anything else. The candidate checks the inspection status, calls the engineer or the certifier, reschedules the pump with the supplier in writing, and tells the client what is happening and why. They think about the knock-on effects on the trades booked behind the pour. The weak answer is some version of “we’d get it poured and sort the paperwork after”. That answer is the reason some slabs are later broken out.

Listen for whether the candidate treats the hold point as a fact of the job or as an obstacle to the program. The supervisor you want sees the inspection as the thing that protects the builder, the owner and the people who will live with the work for decades.

Follow up by asking what they would have done if the engineer could not be reached that day. The answer tests whether the candidate knows who has authority to approve a change and who must be contacted, which matters more on a job with several consultants than on a simple house.

Defects, tolerances and the things nobody wants to say

The second scenario is about bad news from the trades. After the wall sheeting goes up, a plasterer tells the supervisor that a stud line is out of plumb and that a window appears to sit off its setout. Ask what happens next.

A sound supervisor stops the trade from working over the fault, measures rather than eyeballs it, and tells the builder. They then work out whether the problem lies in the framing, the window or the setout, because the fix is different in each case. They record the finding with photographs and a note of the measurements. The weak answer is “it’ll plaster out”. A plasterer who says that is describing a defect that will surface at handover, and a supervisor who accepts it has agreed to carry the cost.

Ask the candidate about a defect they reported on a previous job that nobody else wanted to raise. A supervisor who has never had to say something unwelcome to a subcontractor or a client has usually not been tested.

Follow-up questions do most of the work. Once the candidate has given a first answer, ask what they would tell the plasterer if the window had already been fixed, and what they would tell the client if the fault had been missed until handover. Those answers show whether the candidate treats a defect as a problem to be recorded or as an embarrassment to be managed quietly.

Subcontractors, inductions and site safety

The third scenario tests control of the site. A labour-hire worker arrives at the gate without an induction, and the excavator is already running on the other side of the fence. Ask what the candidate does in the first few minutes.

The right answer is that the machine is stopped, or the operator is told to stop, before anything else. The worker is inducted before they are given access, and their competence for the plant or the task is checked and recorded. The supervisor then speaks to the labour-hire company about why the worker arrived unprepared. The weak answer is “they seem fine, let them get on with it”. That answer is the start of most of the serious incidents that end up in an investigation.

A supervisor should also know where the reporting line is for a serious incident, and what must be preserved on site afterwards. Ask the candidate to describe, in general terms, what they would do after an incident with an injury. Their answer will show how seriously they take the obligation to report and to keep the site as it was until the inspectors have been.

Variations, client requests and the paper trail

The fourth scenario is about scope. The client wants the kitchen window moved after the frame is up. The client says it is a small thing and asks the supervisor to just do it. Ask what the candidate says.

A sound answer is a polite refusal to start until the change is written up. The supervisor prepares the variation with its price and its effect on the program, gets the client’s approval in writing, and then instructs the trade. They also think about the things a small change can disturb: the framing, the services, the lintel and the waterproofing. The weak answer is “no worries, we’ll sort the price at the end”. That is how a variation becomes a dispute, and how a builder ends up doing unpaid work on a job that was already tight.

Ask the candidate how they would tell the client that the change will cost time as well as money. A supervisor who can hold that conversation without apologising for the builder’s position is worth more than one who agrees to everything to keep the peace.

Money, retention and a subcontractor who is not being paid

The fifth scenario tests whether the candidate understands the money side of a job. A carpenter rings to say he has not been paid for some weeks, and he is threatening to leave the site. Ask what the candidate checks first.

A strong answer goes to the record. The supervisor looks at the payment claims, what has been certified and what has been held back, and what the contract says about the process for releasing money. A supervisor who understands retention knows that money held back from payments is governed by the contract and by the security of payment rules, and that the release of that money follows a defined path. They keep the crew informed without making promises the builder has not authorised. The weak answer is “I’d tell him to hang on and sort it out at the end of the week”, because it has no basis in the paperwork and it invites the subcontractor to stop work.

A supervisor who handles money well is usually one who keeps a clear record of who is owed what, and who never lets a verbal understanding stand in for a claim that has been lodged.

Follow up with a question about cash flow on the site. Ask how they would know, before the end of the month, that a subcontractor’s claim was going to be late, and who they would tell. A supervisor who watches the money as well as the work is a supervisor who protects the builder’s margin.

Records, diaries and the evidence a good supervisor keeps

The sixth scenario is the simplest and often the most revealing. Ask the candidate to show you the daily diary or the site notes from their last job, and to tell you what they would change about it. Ask to see photographs as well, if they have any.

A good supervisor produces a diary that records the weather, visitors, deliveries, the inspections that took place, the instructions given and the hold points released. Their photographs are dated and show the work before it is covered. They can talk candidly about a mistake that is recorded in the diary, because the diary is how the mistake was fixed. The weak answer is “I keep it in my head”, or a diary with nothing in it for a fortnight of work. A supervisor’s diary is often the only contemporaneous record of a site in a dispute, and a candidate who does not keep one will leave the builder with nothing to defend the job with.

Once the hire is made, the way you review how the supervisor performs is a separate question, and the article on performance reviews for site staff covers that properly.

Red flags that show up in the answers

Some warning signs appear in almost every weak interview, whatever the scenario. Use these flags to decide what to probe further, not as a verdict on a single answer. A nervous candidate can still be a careful one, and a polished answer can hide a gap that only the diary will reveal. Watch for these:

• The candidate blames the trades, the client or the previous builder for every problem and cannot describe a fault they caused.
• They treat the program as a target to be hit at any cost rather than a commitment to be managed with the client.
• They speak with confidence about regulatory detail they cannot source, and cannot say where they would check it.
• They have never reported a near miss, which usually means they did not record one.
• They answer every scenario with a fix and never with a question about what has already been checked.

Worked example: a builder in the Hunter region

A builder in the Hunter region is hiring a supervisor for a run of townhouses. Two candidates interview well. The first has a strong résumé, speaks fast about the program and has managed larger jobs. The second is quieter, brings a folder of diaries and dated photographs from a previous project, and asks two questions about the inspection regime before answering anything.

The builder puts the concrete pump scenario to both. The first candidate says the pour would go ahead and the paperwork would be sorted afterwards, because the program cannot slip. The second candidate says the pour stops, the engineer is called, the pump is rebooked in writing, and the client is told before the crew is sent home. The builder then asks each to show a diary. The first has nothing for the previous month. The second produces a page for every working day.

The builder hires the second candidate and records the answers against the signals on file. A few months later, a trade on a neighbouring townhouse covers a set of footings before the inspection, and the builder’s own site is not affected by the same habit because the supervisor has made the hold point part of the daily routine. The decision was defensible because the reasons were written down on the day it was made.

Pay for the role should be set against the classification the work falls under, and the article on how building award classifications work sets out how those levels are read.

How to run the interview and keep a record of it

The structure matters as much as the questions. A consistent process lets you compare candidates fairly and lets you explain the decision later. Work through the steps in the order shown, and keep the same scenarios for each candidate so the answers can be compared.

Write the notes the same day. A short record of each answer, marked against the signals, is worth more than a clear memory a month later. If you do hire on the strength of an interview, the notes become part of the file that shows the decision was made on the evidence and not on a feeling about the person.

Questions builders ask

• Hiring
• Staff
• Supervision

Published 7 October 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.