Technical and professional questions (what separates the real operators)
This is where Australian interviewers decide if you’re a Construction Manager who can run a job—or someone who’s only seen the dashboard. Expect deep dives into WHS obligations, program control, commercial basics (EOTs/variations), QA/ITPs, and the software stack used by head contractors.
Q: Walk me through how you set up a project from site establishment to first pour / first major milestone.
Why they ask it: They’re testing whether you understand the startup sequence and risk controls.
Answer framework: “Mobilize–Control–Deliver” (site setup, systems, then execution).
Example answer: “I start with site establishment: amenities, access control, traffic management, environmental controls, and emergency response. Then I lock in the control systems—WHS plan, QA plan, ITPs, document control, and a baseline program with procurement lead times. Before first pour, I want permits, inspections, hold points, and pre-pour checklists aligned with the engineer and certifier. If you rush the setup, you pay for it in rework and delays.”
Common mistake: Jumping straight to construction activities without mentioning controls like ITPs, permits, and inspections.
Q: What WHS obligations do you personally carry as a site leader in Australia?
Why they ask it: They’re checking you understand duty of care and practical compliance, not just buzzwords.
Answer framework: “Duty–Systems–Evidence” (what you’re responsible for, how you run it, how you prove it).
Example answer: “I treat WHS as a daily management system: risk assessments, SWMS compliance for high-risk work, prestarts, and verification on the floor. I make sure incidents and near misses are reported and investigated properly, and that corrective actions are closed out. I’m also conscious of the broader duty under Australian WHS laws—consultation, training, and ensuring the work environment is safe so far as reasonably practicable. If it isn’t documented and verified, it didn’t happen.”
Common mistake: Saying “safety is everyone’s responsibility” and stopping there—interviewers want your mechanisms and evidence.
Q: How do you build and manage a construction program—what level of detail and what meetings drive it?
Why they ask it: They want to see if you can control critical path and interfaces.
Answer framework: “Baseline + lookahead + constraints” (master program, 2–6 week lookahead, daily coordination).
Example answer: “I keep a baseline program that’s logic-linked and procurement-aware, then I run the job off a rolling lookahead that’s detailed enough for trade sequencing and access. The program lives in weekly coordination meetings and daily floor walks—constraints get logged and assigned owners. If a task is slipping, I want to know whether it’s labor, access, design, materials, or inspections, and I want a recovery action tied to a date.”
Common mistake: Treating the program as a reporting document instead of a control tool.
Q: Which software tools have you used for site and project control (and what did you use them for)?
Why they ask it: They’re testing whether you can operate in the contractor’s ecosystem.
Answer framework: “Tool–Use case–Outcome” for 2–3 tools.
Example answer: “For programming I’ve used Primavera P6 and Microsoft Project depending on the contractor’s standard. For document control and RFIs, I’ve worked in Aconex and Procore—RFIs, submittals, drawing registers, and site instructions. For field capture, I’m comfortable with Procore or similar for defects and inspections, because it tightens closeout and reduces ‘lost’ issues.”
Common mistake: Listing tools without explaining how you used them to control time/quality, not just store documents.
Q: Explain your approach to RFIs and design coordination on a D&C project.
Why they ask it: They’re checking whether you can prevent design gaps from becoming site delays.
Answer framework: “Triage–Track–Close” (prioritize, assign, chase, verify resolution hits the floor).
Example answer: “I triage RFIs by program impact and safety/compliance risk, not by who’s shouting loudest. I keep a live register with due dates and escalation rules, and I make sure responses are buildable—details, not vague notes. Then I verify the resolution is reflected in updated drawings and communicated to the trades, otherwise you get rework disguised as ‘miscommunication.’”
Common mistake: Treating RFIs as admin work instead of a production control system.
Q: How do you manage variations and protect margin without turning every issue into a fight?
Why they ask it: They want commercial discipline with relationship maturity.
Answer framework: “Notice–Evidence–Agreement” (notify early, document cause/impact, price and agree).
Example answer: “I’m proactive with notices—if scope or conditions change, I flag it early with photos, instructions, and program impact. I separate entitlement from emotion: what changed, what it costs, what time it needs. Then I aim to agree variations progressively, not at the end, because unresolved variations poison relationships and cashflow.”
Common mistake: Waiting until the end of the job to ‘bundle’ variations—cashflow and trust suffer.
Q: Talk me through an Extension of Time (EOT) you’ve supported—what evidence did you use?
Why they ask it: They’re testing whether you understand delay analysis and contract discipline.
Answer framework: “Cause–Critical path–Proof” (event, impact on critical path, contemporaneous records).
Example answer: “We had prolonged wet weather and a late authority approval that impacted external works. I supported the EOT with BOM data, site diaries, photos, and a marked-up program showing the affected activities on the critical path. I also documented mitigation attempts—resequencing and alternative work fronts—so it wasn’t just ‘we got delayed.’ The claim was cleaner because the records were contemporaneous.”
Common mistake: Claiming time without proving critical path impact or mitigation.
Q: How do you set up QA on site—ITPs, hold points, and inspections—so it actually works?
Why they ask it: They’re checking whether you prevent defects rather than manage them later.
Answer framework: “Plan–Train–Verify” (define ITPs, brief trades, verify with evidence).
Example answer: “I start with clear ITPs tied to spec and drawings, then I brief the trades on what ‘pass’ looks like before they start. Hold points are non-negotiable—if we need engineer sign-off, we plan it into the lookahead. Verification is photos, checklists, and traceable records, because closeout in Australia can be brutal if your QA trail is weak.”
Common mistake: Treating QA as paperwork done after the fact.
Q: What do you do when a critical system fails—say Aconex/Procore is down on a day you need to issue drawings or close defects?
Why they ask it: They’re testing resilience and control under disruption.
Answer framework: “Fallback–Control–Reconcile” (temporary process, version control, then back-capture).
Example answer: “First I switch to a controlled fallback: a temporary register, PDF packs with clear revision tags, and a single point of issue so we don’t get multiple ‘latest’ drawings floating around. I brief supervisors and key trades on what’s valid for today and what’s on hold. Once the system is back, I reconcile—upload, back-capture decisions, and close the loop so the record is complete.”
Common mistake: Letting people ‘just use what they have’—that’s how rework and disputes start.
Q: How do you manage subcontractor progress claims and avoid paying for work that isn’t complete?
Why they ask it: They want to see cost control and fairness.
Answer framework: “Measure–Verify–Certify” (agreed milestones, site verification, documented sign-off).
Example answer: “I prefer milestone-based claims tied to measurable deliverables—areas complete, inspections passed, defects cleared. Before certifying, I verify on the floor with the supervisor and cross-check against ITPs and hold points. If something’s not complete, I’m transparent: I explain what’s missing and what ‘complete’ means, so it’s consistent and defensible.”
Common mistake: Approving claims based on pressure or relationships instead of measurable completion.