Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
I assess MEP conflicts by how candidates reach a safe, approved fix - not how fast they suggest a reroute. When a duct and cable tray block equipment access, I look for checks of drawings and field conditions, trade input, and a hold on affected work when safety or approval is unresolved.
My interview checks for key skills for data center construction managers, specifically whether candidates can:
I score 8 areas on a 1–5 scale, using the same prompts for each candidate. This structured approach is part of my broader strategy to hire data center construction project managers efficiently. A high total cannot cancel out unsafe judgment. My hiring decision rests on <u>what candidates would check, document, and verify</u> - not how confident they sound.
Data Center PM Interviews: MEP Conflict Decision Workflow
Ask candidates which trades the change affects before they name attendees. Look for mechanical and electrical foremen, detailers, the VDC coordinator, and the superintendent. The goal isn’t consensus. It’s getting enough input to choose a route crews can build.
Bring in other trades only when the change affects their work. Include commissioning personnel if access or testing could change.
Ask candidates what trades need to confirm before recommending a route: prefabrication status, released materials, replacement lead times, lifting and joining access, temporary supports, crew productivity, and downstream tie-ins.
A model revision is not the same as a buildable field change. Compare every option against code, owner criteria, system performance, and maintenance access - not convenience.
Use this matrix to guide the candidate’s comparison. Each option depends on verified drawings, specs, equipment requirements, and field conditions. VDC or commissioning review does not count as approval.
Use the comparison to test whether the candidate can tell the difference between a route crews can build and one that simply looks convenient. Confirm the project’s approval requirements for each option.
Require a short coordination record covering the conflict location, drawing or model revision, affected packages, options, assumptions, missing information, and required approvals.
Assign one accountable owner and a deadline to each open action. Tie deadlines to fabrication release, rough-in, inspection, or testing.
Check whether candidates put unrelated questions in separate issue records instead of letting them stall the routing decision. Keep version history so teams don’t reopen settled items or work from old information.
Once the options are logged, move to approval authority and field release: test who owns the decision and who must approve the change.
After the team compares routing options, test whether the candidate knows who can approve the change - and who can only recommend it.
Agreement on a solution is not permission to change the design. Ask who recommends the change, approves it, controls field release, and verifies the result. Trades recommend changes. The engineer of record approves design intent, while the delegated designer approves delegated scope. The PM manages implementation and verification. Commissioning reviews testing or performance impacts but does not replace design approval.[3][4]
Next, ask who can approve added cost or time. Technical approval is not commercial approval. Changes to price, schedule, scope, warranty, or milestones must follow the contract’s formal change process.[6][7]
A candidate who cannot separate these approvals does not yet understand how field changes move from review to release.
Judge observable actions, not confidence or familiarity with job titles.
Ask candidates to describe the field release package. It should include the approved clarification or RFI response, revised coordination drawings or BIM content, the applicable formal change directive, and the distribution record. The release should identify the area, revision, effective date, responsible trade, and inspection or testing hold points. RFI responses that affect cost or time must enter the formal change process; meeting minutes alone are not authorization.[8][9]
Distribute the revision through controlled document channels and supersede old revisions. Record whether fabricated material will be reused, reworked, or scrapped. Then test whether the candidate identifies who verifies the installation against the approved revision and updates commissioning records.[3][4][5] Use that answer to move into the impact check on schedule, sequence, access, and commissioning.
Once the change is approved, test whether the candidate can predict its field impact. Ask them to trace the change through fabrication, delivery, installation, inspection, and start-up. Look for specific affected activities, dependencies, trades, and completion dates - not vague promises to recover lost time. Cost estimates should include engineering, replacement materials, labor, remobilization, relocation, temporary protection, overtime, and delayed testing.[10][2]
Next, check the work sequence. Which trade installs first? Can prefabricated assemblies be reused? How will crews keep safe access and temporary power, cooling, or both? The candidate should explain trade congestion, supervision needs, inspection availability, and whether work elsewhere can continue without causing rework. Strong answers weigh risk, sequence, and turnover rather than focusing only on the technical fix. This preparation mirrors how construction teams prepare for DOE data center projects by aligning technical requirements with community and energy constraints. Also ask what could block testing or turnover.
Ask the candidate to check maintenance access against manufacturer requirements and design criteria. The review should cover valve and damper access, electrical working clearances, filter and coil removal paths, test ports, drains, controls panels, and cable pathways. Clash-free does not mean maintainable. ASHRAE guidance covers access for service, repair, removal, and replacement - not just installation.[1]
Have the candidate review system interfaces, too, rather than stopping at the spatial clash. Ask which testing prerequisite the change could block: pressure testing, flushing, controls-point verification, sensor calibration, startup, or functional performance testing. They should trace power, cooling, BAS, alarms, and failure-mode interfaces into integrated systems testing. Bring commissioning into the process before final installation decisions, and involve operations in functional and integrated testing.[2]
Check who verifies the work and what evidence proves acceptance. Ask the candidate to name the verifier and specify measurable evidence: field dimensions, support checks, equipment tags, flow direction, signoffs, and test results. Installed is not accepted. For changed interfaces, require updates only to the affected commissioning plans, inspection checkpoints, test scripts, equipment records, as-builts, and turnover documents.[11]
If testing fails, the candidate should identify who owns the correction, who witnesses the retest, and what evidence proves acceptance. A test notice is not acceptance.[2]
After the candidate walks through the conflict, score the judgment behind their response. This makes the coordination scenario a repeatable test of how they make decisions.
Give every candidate the same core scenario. Score eight areas: document verification and field-release documentation, MEP interfaces, trade consultation, decision ownership, escalation, schedule and cost, installation feasibility and commissioning, and closeout.
Use a 1–5 scale: 1 = missing or unsafe reasoning, 3 = workable with prompts, and 5 = complete without help. Record the actions that support each rating.[12]
Ask the same short prompts in the same order:
Also ask about schedule, cost, fabrication, and work sequence. Allow clarifying questions, but give every candidate the same level of coaching.[12]
Watch for blame shifting, unilateral reroutes, bypassed review, and delayed commissioning. A high total must not hide unsafe judgment. Before interviews begin, set critical thresholds, including minimum scores for decision ownership and the combined installation feasibility and commissioning area.
Have interviewers score independently, then use their notes to resolve differences. Tie the hiring recommendation to the PM duties, and use the scorecard to compare candidates on evidence, not confidence.
Separate decision-making authority from technical knowledge. MEP leads and engineers own design intent, technical specifications, and system performance. A project manager (PM) shows judgment by coordinating trades, resolving conflicts where systems meet, managing procurement dependencies, and making sure systems are ready for commissioning.
Ask candidates to walk through a conflict they handled: What risk did they spot? Who had authority to approve changes? How did they manage schedule or cost impacts without compromising safety or quality?
Ask candidates to walk through one piece of equipment from submittals and factory testing to shipping, installation, startup, and functional testing. What made it ready for testing - not just delivered? Have them explain which readiness prerequisites they personally checked before release.
Then ask about a failed test. Have them walk through the investigation, corrective actions, formal retesting, and final acceptance process. Who witnessed the retest, and what evidence confirmed the fix?
Focus on participation and supervised learning, not solving problems alone. Assess whether candidates can spot an MEP clash, identify the key stakeholders, and follow escalation procedures.
Ask how they reviewed BIM models or submittals, helped communicate the conflict, and understood its effect on installation schedules. Look for technical curiosity and a clear understanding of their authority: junior PMs should route field conflicts through change control, not approve design changes on their own.
