4 — Technical and Professional Questions (the separators)
This is where US General Contractor interviews get real. They’ll test whether you understand contracts, cost control, and jobsite systems—not just “construction knowledge.” Expect follow-ups. If you say “we used Procore,” they’ll ask what workflows you owned.
Q: How do you build and manage a baseline schedule—what’s your process and what tools do you use?
Why they ask it: They want proof you can run critical path and not treat the schedule like a poster.
Answer framework: “Inputs → logic → ownership → updates.” Explain how you build logic ties, assign owners, and update with field reality.
Example answer: “I start with contract milestones and long-lead procurement, then build the logic around trade sequence and inspections. I’ve used Primavera P6 and Microsoft Project depending on the company, but the key is the logic and the weekly update discipline. I run pull-planning sessions with the super and key subs, then translate that into a CPM schedule with clear constraints. Weekly, we update percent complete, adjust logic only with documented reasons, and publish a two-week look-ahead that matches the CPM.”
Common mistake: Naming software without explaining logic ties, constraints, or update cadence.
Q: Explain your buyout strategy. How do you avoid scope gaps and bid shopping accusations?
Why they ask it: Buyout is where margin is made—or lost—and where ethics and documentation matter.
Answer framework: “Scope leveling → clarifications → award rationale.” Show a clean, auditable process.
Example answer: “I level bids against a scope sheet and force written inclusions/exclusions—especially for MEP, fire protection, and finishes. I run scope reviews with each bidder, document clarifications, and confirm alternates and unit rates. Award decisions are based on scope completeness, schedule, safety record, and past performance—not just low number. That protects us from gaps and keeps us out of bid-shopping gray areas.”
Common mistake: Bragging about squeezing subs without mentioning scope sheets and documentation.
Q: Walk me through your change order process from identification to billing.
Why they ask it: They’re testing whether you can protect the company contractually and keep cash flowing.
Answer framework: “Notice → pricing → approval → tracking.” Tie it to contract requirements and logs.
Example answer: “First, I confirm whether it’s owner-driven, design-driven, or unforeseen condition and send timely notice per the contract. I get ROM pricing quickly, then formal pricing with backup—labor, material, equipment, markups—aligned to the schedule impact. I track it in a change order log and push for written authorization before releasing work, unless it’s a safety or stop-work situation. Finally, I make sure it’s billed correctly—often via AIA G702/G703 on commercial jobs—and reconciled against the budget.”
Common mistake: Doing the work first and trying to ‘paper it’ later.
Q: How do you handle RFIs and submittals so they don’t become schedule grenades?
Why they ask it: RFIs/submittals are the quiet killers of fast-track projects.
Answer framework: “Triage → deadlines → escalation.” Explain prioritization and escalation paths.
Example answer: “I triage RFIs by schedule impact and field need—anything affecting rough-in, embeds, or long-leads is top priority. In Procore, I assign due dates that match the look-ahead, not arbitrary two-week windows, and I escalate with a weekly design coordination call if responses slip. For submittals, I build a submittal register early and tie key approvals to procurement dates. The goal is predictable flow, not a giant backlog.”
Common mistake: Treating RFIs as admin work instead of schedule control.
Q: What’s your approach to AIA billing and pay applications?
Why they ask it: They’re testing whether you understand cashflow mechanics and lien risk.
Answer framework: “Front-end setup → monthly discipline → backup.” Explain SOV setup, percent complete, and documentation.
Example answer: “I set up a clean Schedule of Values that matches cost codes and the contract—no ‘miscellaneous’ buckets that cause fights later. Each month, we validate percent complete with the super and subs, collect conditional lien waivers, and attach backup for stored materials when allowed. I’m careful with retainage rules and make sure change orders are reflected correctly so we’re not underbilling or creating disputes.”
Common mistake: Guessing percent complete without field verification.
Q: How do you run safety as the controlling contractor on site?
Why they ask it: In the US, OSHA exposure and EMR matter, and they want to see leadership—not slogans.
Answer framework: “Plan → enforce → document.” Mention pre-task planning, orientations, audits, and stop-work authority.
Example answer: “I treat safety like production: planned and measured. We do site-specific orientations, daily pre-task plans, and weekly toolbox talks tied to current hazards. I run regular audits with documented corrections, and I empower supers to stop work immediately for fall protection, trenching, or energized work issues. If we have an incident, we do a root-cause review and adjust the plan—not just blame a worker.”
Common mistake: Saying “safety is #1” without naming concrete controls.
Q: What OSHA standards come up most on your projects, and how do you stay compliant?
Why they ask it: They want to know if you understand common citations and can manage risk.
Answer framework: “Top hazards → controls → verification.” Pick relevant standards (fall protection, scaffolds, trenching, silica).
Example answer: “The big ones I see are fall protection (29 CFR 1926 Subpart M), scaffolding, trenching/excavation, and silica exposure controls. We verify competent persons for excavation and scaffolds, require documented inspections, and enforce tie-off and guardrails with zero exceptions. I also coordinate with subs on JHAs and make sure we’re aligned with the site-specific safety plan. Compliance is a system, not a pep talk.”
Common mistake: Vague answers that don’t reference real hazards or controls.
Q: How do you manage long-lead procurement and substitutions when lead times blow up?
Why they ask it: Lead times are still a major US risk, and they want to see proactive procurement.
Answer framework: “Identify → lock → track → pivot.” Show how you track and how you get approvals for alternates.
Example answer: “I identify long-leads during precon—gear, RTUs, curtainwall, elevators—and I lock submittal dates and release dates into the baseline schedule. I track procurement weekly with a log that includes fabrication and shipping milestones. If lead times change, I bring options fast: approved equals, phased releases, or design adjustments, and I document schedule impacts for potential time extensions. The key is not being surprised at week 12.”
Common mistake: Waiting for the sub to complain before you act.
Q: What’s your method for cost forecasting—how do you know a job is going off the rails early?
Why they ask it: They want a GC who can forecast, not just report history.
Answer framework: “Budget → commitments → actuals → EAC.” Explain how you use cost codes and trend logs.
Example answer: “I track budget vs. commitments vs. actuals by cost code and maintain a trend log for emerging risks—scope gaps, design creep, productivity issues. Each month I update EAC based on real production rates and remaining scope, not hope. If a cost code starts trending negative, I identify the driver and propose a corrective action—scope clarification, change order pursuit, resequence, or subcontractor performance plan.”
Common mistake: Only looking at invoices after the money is already spent.
Q: If Procore (or your project management system) goes down during a critical week, how do you keep the job moving and protect documentation?
Why they ask it: They’re testing operational resilience and whether you rely on one tool as a crutch.
Answer framework: “Fallback workflow.” Identify what must continue (RFIs, submittals, daily reports, safety) and how you capture it.
Example answer: “If Procore is down, we switch to a predefined fallback: RFIs and submittals via email with a strict naming convention, daily reports captured on a shared template, and photos stored in a dated folder with location tags. I assign one person to back-enter everything once the system is up so the record stays complete. For anything contractual—like change notice—I make sure it’s still issued in writing within the required timeframes.”
Common mistake: Saying ‘we’d just wait’—that’s how you lose claims and control.
Q: Tell me about a time you dealt with an AHJ inspection failure. What did you do next?
Why they ask it: They want to see how you handle compliance, rework, and stakeholder communication.
Answer framework: STAR + “containment.” Contain the issue, fix root cause, prevent recurrence.
Example answer: “We failed a firestopping inspection above ceiling because documentation and labeling didn’t match what was installed. I stopped ceiling close-in in the affected zone, brought the firestop sub and inspector into a walk, and created a punch list by grid line. We corrected and re-inspected within 48 hours, then implemented a hold-point checklist and photo documentation before any future close-in. I also updated the owner on schedule impact the same day with a recovery plan.”
Common mistake: Blaming the inspector instead of tightening your process.