Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
For a data center VDC career, I’d focus on Revit, Navisworks, MEP coordination, and field experience - not job titles alone. For pay context, two cited Jacobs coordinator postings advertise $61,700–$90,000 in annual base salary as of November 2, 2026. That’s one employer’s range, not a national benchmark.
Here’s what I’d check when planning your next move:
My rule: <u>compare the work you’ll own and the complete offer</u> - then ask for clear decision limits, field access, and promotion criteria before accepting.
Data Center VDC Workflow: Design to Turnover
The difference between entry-level production support and senior coordination ownership comes down to what you check, decide, and deliver.
During preconstruction, combine architectural, structural, and MEP models, including fire protection, into a combined model. Check versions and coordinates before running clash tests. Audit for errors, broken links, incorrect worksets, unconnected systems, and the required level of detail. Follow the BIM Execution Plan (BEP) for model uses, exchanges, responsibilities, and quality control.
During construction, separate hard clashes from clearance, duplicate, and constructability issues. Clash counts aren't the priority. Safety, code compliance, access, sequence, lead time, rework, and the critical path come first. Track each issue's location, trade owner, due date, priority, status, and proof of closure.
If a resolution needs design approval, support the RFI with model views and field constraints. Then link the response to the updated model. Use a two-week look-ahead to align model releases with work from fabrication through commissioning. Close issues only after checking the revised model and relevant field conditions.
At turnover, check record geometry against installed conditions. Verify equipment tags, asset data, and operation-and-maintenance information. Support commissioning by documenting system boundaries, test dependencies, and outstanding deficiencies. Use COBie when the owner requires it, and deliver records the facilities team can use.
This work calls for disciplined use of Revit, Navisworks, and field-tracking workflows - not just familiarity with the software.
In Autodesk Revit, practice MEP systems, families and parameters, worksharing, linked models, schedules, and model audits. In Navisworks Manage, build search or selection sets, configure hard and clearance tests, update models, and verify issue closure. Use AutoCAD for 2D details and spreadsheets to track issues.
Pair those software skills with knowledge of switchgear, generators, UPS systems, busway, cable trays, cooling and piping, containment, and fire protection.
Check space for installation and maintenance - not geometry alone. Account for insulation allowances, valve access, replacement paths, and installation tolerances. Marked-up views, meeting notes, and RFI narratives should clearly tell installers what needs action.
Compare decision ownership and deliverables, not titles. People can enter VDC through construction management, engineering, architecture, BIM production, specialty trades, fabrication, or field experience. Degrees, Autodesk certifications, and safety credentials depend on the role; they aren't universal prerequisites. Use sanitized work samples to show your responsibilities, coordination decisions, and verified outcomes.
As the role progresses, the focus shifts from production support to coordination ownership and team leadership.
Once you can handle coordination tasks reliably, move toward owning specific systems and handoffs. Ask to take ownership of an electrical room, overhead utility corridor, or prefabrication package. Get exposure to fabrication, installation, and commissioning, too. Understanding how work passes between these stages is central to data center construction.
Build your promotion case around repeatable delivery: fewer repeat clashes, faster issue closure, fewer rejected releases, and field-verified resolutions. Track your results separately from the team’s output. Finding more clashes alone doesn’t show that you’re ready for a senior role.
At this level, the focus shifts from coordinating models to running the coordination process. A manager keeps project coordination dependable through staffing, review gates, and risk reporting.
A director takes that work across projects or buildings: setting shared standards, assigning people, and approving technology spending. Both roles must connect decisions to cost, schedule, quality, and safety - and recognize that coordination is only one input.
One reported 150-MW data center project used shared model reviews to align superintendents, trade contractors, designers, and the owner’s facilities team.[1]
Before accepting a role, confirm which systems you’ll own, which decisions you can make, and what earns advancement. For technical growth, look for difficult MEP work and field exposure. For management growth, seek responsibility for staffing, standards, and multiple buildings. Ask for a defined next assignment - not just a promise of “growth.”
Those paths also affect pay, which the next section covers.
Research current as of November 2, 2026. Advertised ranges are not guaranteed offers. The two verified Jacobs coordinator postings below offer clues about pay, not market benchmarks.
Compare responsibilities before titles. A contractor VDC engineer may handle field coordination, subcontractor models, clash resolution, and installation sequencing. A specialty trade role may focus on electrical, mechanical, or prefabrication models. Engineering roles may center on design documentation and constructability, while owner-side positions may cover standards, model governance, asset data, and turnover.
Pay depends on scope, authority, location, travel, clearance, and schedule risk.
Verified ranges aren't available for every market, so the table includes only the cited postings. These coordinator roles don't establish pay benchmarks for senior managers or directors. Compare each range with the systems, coordination decisions, and turnover duties you'd own.
Base salary is only part of the offer. Travel, hours, and bonuses can change what that pay means in practice.
A target bonus isn't guaranteed, and equity depends on vesting and liquidity. Compare health coverage, retirement contributions, and paid leave separately. Even offers with similar salaries can look different once you account for hours and travel.
Hypothetical offers - not employer quotes or market benchmarks Offer Base pay Variable pay and benefits Travel and hours Practical interpretation A: Local contractor VDC engineer $105,000 10% target bonus, standard benefits, 401(k) match Mostly local; 45–50 hours weekly Lower base may provide better stability and fewer personal travel costs B: Travel-intensive VDC role $125,000 5% target bonus, company-paid lodging and per diem 60-hour weeks, frequent travel Higher base may be offset by long hours and disruption C: Owner-side BIM/VDC role $115,000 15% target bonus, stronger benefits, possible equity Mostly local; occasional site travel Lower advertised upside may come with better predictability and benefits
Hypothetical offers - not employer quotes or market benchmarks
Ask for written terms covering overtime, travel time, lodging, per diem, home-leave trips, relocation payback, and bonus eligibility. Per diem and reimbursements are not salary, and their tax treatment varies by arrangement.
The two Jacobs postings form a small, single-employer sample - not a national VDC salary benchmark.[4][5] Treat job-board ranges as signals. Check the posting date, employer, location, base range, bonus language, and travel expectations. Also confirm whether the employer supplied the range or the job board estimated it.
Check government reporting periods, too. The supplied BLS figures report May 2025 median salaries of $114,990 for construction managers and $171,270 for architectural and engineering managers. These are broader occupations, not direct VDC salary benchmarks.[3][2]
For negotiations, use the written responsibilities and complete offer rather than the title alone. Compare the pay with the scope you'd actually own.
Choose roles that build coordination judgment, field exposure, and decision authority - not just modeling output. Balance those growth opportunities against the full compensation package, and use the same lens when presenting your work and comparing offers.
Create two or three anonymized case studies that show model setup, clash prioritization, issue tracking, and verified closure. For each, describe the project type, trades involved, software, coordination objective, and your contribution. Include evidence of critical-power, cooling, redundancy, or commissioning work.
Show the work through a discipline or workset setup, clash-priority matrix, issue log, marked-up coordination view, or field-ready installation package.
Use approved, anonymized material or clearly labeled practice projects. Remove client names, facility locations, security-sensitive layouts, equipment capacities, proprietary details, and unpublished design information. Back up outcomes with permitted issue records, approved details, or field-verification notes. Don’t claim avoided delays or savings without documentation.
Look for job descriptions that spell out a path to more responsibility. Check the project phase, MEP complexity, modeling versus coordination ownership, required software, field access, travel, mentorship, and promotion criteria.
Ask who approves your decisions and what should change at 12, 24, and 36 months. More ownership and field access, supported by clear promotion criteria, can strengthen your case for higher compensation.
Trade hires should close skill gaps in model federation, clash testing, and issue tracking. Commercial-construction hires should add knowledge of critical power, cooling, redundancy, and commissioning. Use those qualifications and added responsibilities to negotiate better offers. Require employers to define decision authority and measurable advancement criteria before you accept.
Draw on your experience in healthcare, pharmaceutical, or semiconductor projects. Focus on complex MEP coordination, high-density builds, and tight schedules. Use the STAR method (Situation, Task, Action, Result) to turn that experience into resume achievements that explain what you did and the results you delivered.
Build your skills in Revit, Navisworks, and Autodesk Construction Cloud, and pursue relevant certifications. In your current role, take ownership of BIM Execution Plans, perform clash detection, and lead multidisciplinary coordination meetings. These responsibilities help show you're ready for data center work.
You’re ready when you move from supporting models to owning project-wide delivery. That means independently leading multi-trade coordination, managing model governance, and turning complex data into clear field instructions. It also means resolving high-stakes MEP conflicts, setting priorities, and mentoring coordinators.
Back up that readiness with verified field-issue closure, successful prefabrication integration, and schedule adherence. You should also be able to explain system constraints and manage risk across entire data halls.
Compare total annual value - not just base pay. Get written confirmation of expected hours, paid travel time, and overtime eligibility.
Separate recurring cash compensation from one-time or variable payments, such as per diem, relocation payments, or milestone bonuses. For travel assignments or extended site deployments, subtract any living expenses your employer won’t reimburse. Confirm whether salary rates are based on the project site or your home office.
