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 commissioning career path.
Can you explain the commissioning levels in your own words?
The opening theme on most commissioning screens. The ladder runs factory, delivered, installed, component, systems, integrated, and the logic is the point: each level proves what the next one assumes, which is why the order cannot be shuffled to suit a schedule.
Explain L1 to L5 to a new tech.
What they check Sequence logic (factory to delivered to installed to component to systems to integrated) and why the order matters, in your words rather than the framework's.
Red flag Reciting the level labels without the why.
Go deeper on this theme: Commissioning levels, explained in plain language: L0 to L6.
What do you do when the script says a step you believe is wrong?
The discipline theme, and the sharpest filter in the set. The answer is stop, then red-line the script through the issues process. Do not improvise on energized systems, however confident the fix feels: the script is the agreed truth, and changing it has a route.
The test script says a step you believe is wrong.
What they check Stop first, correct through the red-line and issues process, and never adapt live on energized plant.
Red flag “I would adapt it.” Improvisation reads as competence to the candidate and as risk to the panel.
The full worked depth, from single-line reading to test-script anatomy and a rehearsal with model answers, lives in the Design & Commissioning Prep Pack ($149).
What do you record during a functional test?
The evidence theme. A witnessed test produces expected versus actual readings, timestamps, the IDs of the calibrated instruments used, and who witnessed each step. If the record cannot reconstruct the test without you in the room, it is not a record.
What do you record during a functional test?
What they check Expected versus actual, timestamps, instrument IDs, and who witnessed.
Red flag Pass or fail with no readings behind it.
What happens when a test fails with the schedule tight?
The judgment theme, usually staged at 2 am for a reason. The failing result gets logged as it happened, the issue enters the list, and the retest path is agreed through the process. Schedule pressure changes none of that; it only raises the temptation.
A pump fails its performance curve at 2 am with the schedule tight.
What they check Log it honestly, raise the issue, agree the retest path, and refuse the quiet pencil-whip without theatre.
Red flag Negotiating the result instead of recording it.
Why does the pull-the-plug test come last?
The systems-thinking theme. The integrated systems test proves what no component test can: that the site's systems respond to a real loss of power together, dependencies and all. It comes last because every level below it must already be true for the result to mean anything.
Why does the pull-the-plug test come last?
What they check Dependency-chain understanding, and what the integrated test proves that component tests cannot.
What makes a turnover package usable for operations?
The handover theme. Operations inherits the plant through the package: as-builts that match what was actually installed, an honest open-items list rather than a clean-looking one, and O&M documentation linked so the first shift can find what the plant needs.
What makes a turnover package usable for operations?
What they check As-built accuracy, open-items honesty, and O&M linkage.
Go deeper on this theme: Documentation and handover, explained.
Who signs the witness point when the vendor is testing?
The independence theme. The vendor technician runs the test; the witness signature belongs to an independent party, and that line holds politely however experienced the vendor is. Witnessing your own work is not witnessing.
The vendor tech wants to sign their own witness point.
What they check Independence of the witness, and holding the line without making an enemy of the vendor.
Scope note: generalized education only. Not a commissioning procedure, a test authorization, or a replacement for your project's scripts and engineering governance. Do not run tests, sign witness points, or modify scripts outside your project's authorized process, whatever an interview answer or an article says.