3) Technical and professional questions (NZ-specific, site-real)
This is where a Site Superintendent who’s “been around sites” gets separated from someone who can actually run one. Expect them to probe your systems: programme, QA, H&S, and documentation. NZ employers also care about how you work with consultants and councils, because compliance issues can wreck timelines.
Q: How do you build and run a 2–6 week lookahead so it actually drives production?
Why they ask it: Lookaheads are how you prevent chaos; they want to see constraint management.
Answer framework: Last Planner-style loop — Plan, Make Ready, Commit, Learn.
Example answer: “I start from the master programme, then break it into a rolling lookahead with trade-by-trade handoffs. The key is ‘make ready’: I track constraints like design info, inspections, access, materials, and permits. Each week we confirm what’s truly ready, not what we wish was ready, and we lock commitments with foremen. Then I review what slipped and why—weather, labour, late RFI—and adjust the next cycle so the plan gets smarter.”
Common mistake: Treating the lookahead as a spreadsheet that doesn’t change site behavior.
Q: What’s your approach to QA on site—ITPs, hold points, and dealing with NCRs?
Why they ask it: Rework kills margin and time; they want a superintendent who prevents defects.
Answer framework: “Prevent–Detect–Correct” with examples.
Example answer: “I prevent defects by making the ITP visible and tying it to the lookahead—crews know what inspections are coming before they start. I detect issues early with walkdowns and staged sign-offs at hold points, especially for waterproofing, fire stopping, and services penetrations. If we get an NCR, I treat it as a system failure: isolate the area, agree a corrective action, and then change the process so it doesn’t repeat—often that’s better supervision, clearer details, or a mock-up.”
Common mistake: Saying ‘QA is the QA manager’s job.’
Q: How do you manage inspections and sign-offs under the New Zealand Building Code and council processes?
Why they ask it: Missed inspections can cause expensive opening-up and delays.
Answer framework: “Map–Book–Prove” — map required inspections, book early, prove compliance with records.
Example answer: “Early in a job I map out the inspection points that matter—council inspections, producer statements, and critical trade sign-offs—then I align them to the programme so we’re not scrambling. I book inspections with lead time and keep a buffer for re-inspection risk. And I prove compliance with clean records: photos, checklists, as-builts, and signed PS where applicable, so handover isn’t a paperwork panic.”
Common mistake: Talking about ‘getting council in when needed’ without a planned inspection schedule.
Q: What H&S systems have you used in NZ—SiteSafe, pre-quals, SWMS/SSSP—and how do you enforce them with subcontractors?
Why they ask it: They want to know you can run NZ-standard contractor management and not just talk safety.
Answer framework: “Set the gate, then police the gate” — pre-qual, induction, verification, consequences.
Example answer: “I’ve worked with SiteSafe-style inductions and contractor pre-qualification where competency and documentation are checked before boots hit site. On site, enforcement is verification: I spot-check SWMS/SSSP against what’s actually happening, and I make supervisors own their controls. If a crew can’t demonstrate the plan, they stop and reset—no exceptions. The key is consistency: the same rule applies whether it’s a small subbie or a major package.”
Common mistake: Listing certificates but not explaining how you enforce controls day-to-day.
Q: Which site software have you used for RFIs, drawings, and field reporting—Procore, Aconex, Autodesk Build—and what does “good” look like in your setup?
Why they ask it: NZ projects increasingly rely on digital workflows; they want someone who won’t create admin chaos.
Answer framework: “Workflow + discipline” — define how info moves and how you keep it clean.
Example answer: “I’ve used Procore and Autodesk Build for RFIs, inspections, and daily logs. ‘Good’ for me means one source of truth: current drawings are controlled, RFIs have clear owners and due dates, and inspections are tied to locations so we can trace issues fast. I keep field reporting simple—photos with context, short notes, and consistent tags—so the PM and QS can use it for progress claims and variations.”
Common mistake: Saying you’ve ‘used Procore’ but not knowing how to structure RFIs, drawing sets, or inspection templates.
Q: If the project management system goes down (no Procore/Aconex access) for 24 hours, how do you keep the site moving without losing control?
Why they ask it: They’re testing operational resilience and document control under pressure.
Answer framework: “Fallback pack” — freeze, verify, run manual controls, reconcile.
Example answer: “First I’d freeze any work that depends on new or uncertain information—no one builds off an unverified detail. Then I’d switch to a fallback pack: last issued drawings printed or saved offline, a manual RFI/decision log, and paper inspection checklists for critical hold points. We’d keep production going on confirmed work fronts only. Once systems are back, I reconcile: upload photos, back-enter inspections, and confirm any decisions in writing so we don’t lose traceability.”
Common mistake: ‘We’d just keep working’—that’s how you build the wrong thing.
Q: How do you plan and control temporary works and site logistics (cranes, hoists, laydown, traffic management) on tight NZ sites?
Why they ask it: Logistics is often the real critical path in NZ urban builds.
Answer framework: “Model–Brief–Enforce” — plan it visually, brief it daily, enforce it physically.
Example answer: “I treat logistics like a design package. I map crane picks, delivery routes, laydown limits, and exclusion zones, then I brief it with foremen and the traffic controller so everyone understands the rules. On tight sites, enforcement is physical: barriers, signage, booking systems for deliveries, and a clear rule that unbooked trucks don’t enter. That’s how you avoid gridlock and near-misses.”
Common mistake: Leaving logistics to ‘common sense’ and reacting when the street is blocked.
Q: Talk me through how you manage concrete pours—pre-pour checks, testing, and finishing—so you don’t get defects or delays.
Why they ask it: Concrete is high-risk for quality, safety, and programme.
Answer framework: Pre–During–Post control points.
Example answer: “Pre-pour I confirm formwork sign-off, embed set-out, access/egress, and a clear pour sequence with the pump line and exclusion zones. During the pour I watch slump and placement, ensure test cylinders are taken as required, and keep finishing resources matched to the pour rate. Post-pour I lock curing protection and record results—photos, test IDs, and any issues—so we can trace it later if there’s a dispute.”
Common mistake: Only talking about ‘getting the truck booked’ and ignoring QA/testing and curing.
Q: How do you handle variations and site instructions so the project doesn’t bleed margin?
Why they ask it: Superintendents often create or prevent variation claims through documentation.
Answer framework: “Notice–Evidence–Cost–Approval” loop.
Example answer: “When something changes, I issue notice early—what changed, where, and why it impacts time/cost. I capture evidence immediately: photos, marked-up drawings, labour and plant records. Then I align with the PM/QS on the commercial path—quote, dayworks, or agreed rates—before the work disappears behind linings. The goal is no surprises at the end.”
Common mistake: Doing the work first and trying to ‘sort the paperwork later.’
Q: What’s your approach to commissioning and handover—especially services coordination and closeout documents?
Why they ask it: Many NZ projects lose weeks at the end because commissioning wasn’t planned.
Answer framework: “Start with the end” — commissioning plan, progressive completion, staged sign-offs.
Example answer: “I start commissioning planning early—who owns what, what pre-commissioning checks are needed, and what access is required. I push progressive completion: close ceilings only when inspections and photos are done, and I track O&M manuals, warranties, and as-builts as we go. At the end, handover is a controlled sprint, not a panic.”
Common mistake: Treating commissioning as something you do in the last two weeks.