Skip to content

Learn · Guide · Interview prep

QA/QC interview questions: what they actually check

Every theme below is the same question in disguise: will you protect the quality record under schedule pressure, without becoming the site's enemy? These are the recurring shapes on data center projects, each with the example stem, what the interviewer is checking, and the answer that ends the conversation.

Written by the DCP team · Reviewed by a commissioning lead with 12 years on live sites · LAST REVIEWED:

The method that works across all of them: practice aloud, not in your head. Answer the stem, score yourself 0 to 4, and rebuild the answer in your own words until the structure arrives without effort. The role behind these questions is mapped on the QA/QC quality engineer path.

What happens at a hold point?

The theme that opens most QA/QC screens, because it separates people who have held the gate from people who have read about it. Work stops at a hold point and stays stopped until the named party inspects and signs; proceeding without release is a breach of the ITP, not a scheduling choice.

Walk me through what happens at a hold point.

What they check  Whether you know the work STOPS until sign-off, who signs the release, and what notice period the inspecting party is owed before the point is reached.

Red flag  Treating a hold point as a formality that paperwork catches up with later.

Go deeper on this theme: ITPs and hold, witness and review points, explained.

What happens when work does not match the drawing?

The non-conformance theme, and the strongest single predictor in the set. A finding routes into the NCR process: record it, contain it, and let the engineered disposition decide the fix. The instinct being tested is documentation-first, not repair-first.

You find work that does not match the drawing. What happens next?

What they check  The four dispositions, escalation without drama, and whether the record is opened before anyone touches the work.

Red flag  “I would just get it fixed.” Bypassing the record is the failure, however good the fix.

Go deeper on this theme: The NCR lifecycle and its four dispositions.

The full worked depth on these judgment calls, with model answers and drills, lives in the QA/QC Quality Engineer Prep Pack ($89).

How do you inspect without becoming the site's enemy?

The relationship theme. Schedule pressure arrives through people, usually a foreman with a pour window closing. The job is firmness with respect: the inspection stands, the escalation path is named, and no tolerance gets negotiated at the workface.

A foreman pushes back that your inspection is slowing the pour.

What they check  Firmness plus respect, a clean escalation path, and zero freelancing on tolerances under pressure.

Red flag  Either caving to keep the peace or grandstanding to win the exchange. Both lose the site.

Which documents do you check before inspecting?

The paper-trail theme. An inspection is only as good as the revision it inspects against: the approved-for-construction drawing at current revision, the approved submittals, the ITP itself, and the calibration certificates of the instruments you will use.

Which documents do you check before inspecting?

What they check  Current-revision awareness, submittals and approved drawings, and calibration certificates, in that instinctive order.

Red flag  Inspecting from memory of how it is usually built.

How does an item get off a punch list?

The closure theme. Items leave a punch list through evidence, not through assurances: the fix is made, re-inspected against the original criterion, and signed off through the same chain that raised it.

How does an item get OFF your punch list?

What they check  Closure evidence, re-inspection, and the sign-off chain arriving in your answer as one sequence.

Go deeper on this theme: How a data center punch list actually works.

What makes an inspection record defensible a year later?

The audit theme. A defensible record answers who inspected what, when, against which revision, with which calibrated instrument, and shows it: photos attached, readings recorded, instrument IDs traceable. A year later, the record is the inspection.

What makes an inspection record defensible a year later?

What they check  Traceability (who, what, when, revision), photographs, and calibrated instrument IDs.

Red flag  Vague notes that require the author present to mean anything.

What do you do when asked to sign off work you did not witness?

The boundary theme, and the one answer worth rehearsing word for word. Do not sign for work you did not witness, whoever asks. The strong answer refuses procedurally, escalates through the named route, and offers the path that keeps work moving: re-test or re-witness under your eyes.

You are asked to sign off work you did not witness.

What they check  Refusal quality: the do-not answer delivered without drama, the escalation named, and a constructive path (re-test, re-witness) offered in the same breath.

Scope note: generalized education only. Not a quality procedure, an inspection authorization, or a replacement for your project's ITP and specifications. Do not release hold points, sign records, or accept work outside your project's authorized process, whatever an interview answer or an article says.

Interview prep

Hear how the format works before the screen

Start with 25 free role-tagged questions with model answers, and see the answer structure these themes reward.