Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
I judge senior electrical estimating skills by cost decisions - not software names. My starting point: five linked work samples that show how you checked quantities, reviewed an estimate, compared bids, priced a change, and explained a cost forecast.
For data center work, I look for clear records of:
I score technical completeness at 30%, traceability at 25%, commercial reasoning at 25%, and communication at 20%. My goal is simple: <u>check whether you can explain and support the numbers</u>, from the first takeoff through field costs.
Senior Electrical Estimator: Five Work Samples That Prove Skill
Check whether the candidate can turn measured quantities into an estimate others can review. Ask them to connect quantities to assemblies, pricing, and a reviewed estimate. Have them name the exact software version they used, their responsibilities, their deliverables, and their review process. Each output should trace back to drawings, specifications, and estimate lines.
Features and integrations vary by edition, version, licensing, and configuration. Use this comparison to assess relevant experience - not to rank platforms.
Ask candidates to open one feeder assembly and explain its conductors, raceway, fittings, supports, terminations, and testing. Then have them trace each item to pricing and labor. They should identify material pricing sources and dates, labor bases, and any manual pricing or labor overrides. They should also explain how they reconciled exported or linked quantities with the estimate.
The test isn't just whether they can use the software. Its output must hold up to quantity checks and estimate review.
Validate quantities before pricing them. Confirm the drawing number, issue date, revision, and scale, and check enlarged details separately. Reconcile equipment counts with schedules and one-lines. Then check routing lengths, rises and drops, assembly contents, and model quantities against specifications and installation methods.
Keep routing lengths in feet and inches, and leave equipment ratings and units unchanged from the source document. When sources conflict, investigate - don't average them. Record every correction, its reason, the affected estimate line, and the reviewer.
In Excel, keep inputs, calculations, assumptions, and outputs separate. Connect assembly IDs to pricing and labor through controlled lookups. Use variance checks to flag differences among takeoff totals, estimate totals, and subcontractor bids. Protect formulas, summarize costs by system or area with pivot tables, and reconcile worksheet totals with the estimating export.
Keep supplier quote numbers, source dates, validity periods, and labor bases traceable. Test scenarios for quantity changes, overtime, escalation, and installation methods. Ask candidates to explain each correction's cost impact and source check - not just how they navigate the spreadsheet. Require that same traceability in estimate review, bid comparison, and change pricing.
Once takeoff is complete, the estimate must stand up to review, bid leveling, and change pricing. Each workflow calls for a different decision - not just a different spreadsheet tab. Keep quantities traceable across all three.
Use the variance log to label each discrepancy as an error, assumption gap, or legitimate design change. Check all major electrical systems against the design and commissioning requirements. Review labor units, crew assumptions, productivity, pricing, subcontractor coverage, supervision, indirect costs, and markups. For each finding, record the cost impact, resolution, and reviewer.
Include a dated basis-of-estimate log with the reviewed estimate and recommendation. Record the estimate version, pricing date, document revisions, labor and equipment rates, productivity assumptions, pricing sources, quotations, escalation, and schedule.
List exclusions, clarifications, allowances, owner-furnished equipment, assumed quantities, and open design questions. Explicitly state whether the estimate includes generator startup, UPS battery testing, integrated systems testing, utility coordination, temporary power, and controls programming. Link each major amount to its support: a takeoff, quotation, labor calculation, or written assumption. Match review depth and contingency to design maturity.[1]
After reviewing scope, put all bids on the same assumptions before comparing prices.
Use an Excel scope matrix to separate compliant scope, exclusions, qualifications, alternates, allowances, and unpriced requirements. Put labor, material, equipment, freight, testing, startup, warranty, and schedule on the same basis. Keep evaluator adjustments separate from supplier commitments: an evaluated total is not the supplier’s quote. Show every adjustment and request written clarification when possible.
To level bids, add the costs of omitted testing, commissioning, startup, warranty, and freight, along with schedule risk, to each quote. Keep qualifications visible and flag any lead-time risk that hasn't been quantified. State the recommendation, the assumptions behind it, and the clarifications needed before award.
After award, use the contract baseline - not the latest drawing - as the pricing reference.
Build the change cost breakdown from the executed contract scope, approved estimate, latest accepted schedule, contract rates, allowances, and applicable markup rules. Show original, added, deleted, and revised quantities. Break out labor, material, equipment, supervision, subcontractor costs, testing, commissioning, escalation, and schedule effects.
Keep the governing directive, relevant revised documents, quantity calculations, labor records, quotations, schedule analysis, and markup calculation with the change record.
AACE's change-management framework runs from identification and notification through review, formal submission, approval or rejection, and execution.[2] Track priced, submitted, approved, and directed to proceed as separate statuses. A pricing recommendation does not authorize work. For directed work, document limits, notice requirements, labor tracking, and reservation of rights.
After estimating and change control, use cost reporting to check whether the forecast still holds. The report tests estimating assumptions - not just monthly spending. Include the approved budget, current forecast, commitments, actuals to date, approved and pending changes, remaining contingency, cost to complete, and forecast at completion.
State the reporting date. Keep approved changes separate from pending exposure, either excluding pending exposure or carrying it as a separate allowance. For each cost code, report dollar variances alongside the cause, corrective action, responsible owner, and expected financial effect. Track labor productivity, material pricing, and contingency use separately rather than combining them into one net variance.
Forecast at completion equals actual costs to date plus cost to complete. Build the cost to complete from remaining quantities, unpaid commitments, productivity, pricing, schedule conditions, and known risks - not a blanket percentage.
Reconcile procurement commitments, accounting actuals and accruals, the change log, and document revisions using the same cost codes and cutoff date. Where integrations exist, check for duplicate commitments, incorrect mappings, and missing accruals. Don’t double-count purchase orders when part of the work has already been incurred.
Keep a project record that includes the data center construction type, U.S. location, dates, delivery method, total project value, and electrical-scope value. State whether each value reflects the bid, award, forecast, or final amount.
Use the revision history to show your judgment. Describe one major revision where software data conflicted with drawings, specifications, vendor information, or field conditions. Explain what you verified, what you changed, who approved the decision, and how it changed the forecast.
Include the electrical complexity, estimate stage, software and version, and outputs delivered. Label your role on each sample as prepared, reviewed, approved, or assisted. Redact confidential information, separate your contribution from the team’s results, and preserve a revision history that shows your reasoning.
Use the same record to judge whether the work can be defended - not how polished it looks. Request five linked samples: marked-up drawings, an estimate, a bid tabulation, a change proposal, and a variance report. Accept redacted project work or a labeled hypothetical. Don’t require proprietary drawings or sensitive rates. For smaller teams, use one integrated exercise with the same drawing revision, cost codes, and reporting date.
Score estimating judgment - not software familiarity - with these weights: technical completeness at 30%, traceability at 25%, commercial reasoning at 25%, and communication at 20%. Score each criterion from 1 to 5. Unsupported work earns 1, usable work needing normal review earns 3, and independently defensible work earns 5.
Ask candidates to explain their biggest assumption, an error they caught, unresolved exposure, and the action they recommended. Require evidence for each score, and apply the same criteria across candidates to distinguish software familiarity from the ability to defend an electrical cost forecast.
Whether reviewing estimates, leveling bids, pricing changes, or reporting, software only matters if the output holds up. Knowing the software doesn’t prove senior-level skill. The estimator must be able to validate quantities, document assumptions, level bids, price changes, and defend the forecast.
The strongest evidence connects screen output to project records to field results. When records are available, compare estimated labor units and gear buyout costs with actuals. Explain the estimate-to-actual variance and what you changed in later estimates.
For senior estimating roles, score every candidate against the same work-sample criteria - not software keywords. Check references for estimate-to-actual performance, not just bid wins. Hire reasoning that stands up to review, not familiarity with an interface.
Build an anonymized portfolio that shows budget or buyout variances, value-engineering savings, and how you reconciled incomplete design documents. Include screenshots of bid-leveling sheets, risk registers, and estimate-to-actual variance logs. Remove client names, proprietary rates, and security-sensitive details.
In interviews, walk through the scope you owned, the decisions you made, and their cost or schedule impacts. Use those examples to show how you spotted constructability risks and resolved scope gaps.
Review subcontractor bids for missing scope or design gaps, then adjust them to create an apples-to-apples baseline. When design documents are incomplete, use historical cost data and professional judgment to put a dollar amount on uncertainty.
Track risks in a formal risk register. Set contingencies based on design maturity, schedule pressure, and procurement risk. Document your assumptions clearly so you can explain and defend your contingency approach during executive reviews.
Use expert judgment and system-level benchmarks, such as cost per MW or per square foot, to build bid-ready estimates from single-line diagrams, narratives, or basis-of-design documents.
As designs change, document assumptions and flag constructability risks early. Quantify uncertainty with allowances tied to design maturity and procurement risk. Explain contingencies, lead-time escalation, and equipment buyout strategies so the estimate stands up to review, supports an audit, and meets project margin targets and owner requirements.
