Critical Facilities Engineer for Colocation Data Centers

What does this hire really come down to?

A critical facilities engineer at a colocation provider supports a live site that serves many customers. They write and review procedures, plan maintenance, manage capacity and projects and sometimes carry out switching under lockout. Customer service levels shape every decision, and a single mistake can reach several companies at once.

The engineer is the person who must say a request is unsafe, even when the customer is large. The first tradeoff is customer sensitivity. Work that is routine in a single-tenant site may need notice and approval in a colocation building. Ask how the candidate handled a maintenance window that affected customers and who they told. An engineer who has only worked in an enterprise site may find the notice process slow.

The second tradeoff is the sales interface. Colocation engineers are asked for technical answers about power, cooling and space by people who are selling. Ask how they handled a request they could not support. An engineer who says yes to everything creates risk, and one who says no to everything loses business. The third is capacity tracking. Selling space and power is the business, so the engineer must know what is truly available. Ask how they tracked headroom and how they dealt with a customer who exceeded their allotment.

What do we check before you see anyone?

Ask how they planned a window and notified customers. Detail on approvals matters. Ask how they tracked power and cooling per customer and what decisions the data drove. Ask what procedures they wrote and how technicians responded. Ask what switching they performed and under what authorization.

• Customer-aware changes: ask how they planned a window and notified customers. Detail on approvals matters.
• Capacity tracking: ask how they tracked power and cooling per customer and what decisions the data drove.
• Procedure authorship: ask what procedures they wrote and how technicians responded.
• Switching authorization: ask what switching they performed and under what authorization.
• Sales interface: ask how they handled a technical request they could not support.
• Incident handling: ask about a customer-affecting event and how they communicated.
• Project involvement: ask which expansions or upgrades they supported and what they owned. Colocation sites change often.
• Vendor management: ask how they managed maintenance vendors on a live site and what they did when work ran late.

Where do we find these candidates?

Colocation CFEs come from other colocation operators, enterprise sites, hospital facilities and critical engineering consultancies. Some began as technicians and finished a degree. Others are engineers who want a busier, more commercial site. A few came from utility or manufacturing environments and moved into data centers for the shift pattern.

• Colocation CFEs come from other colocation operators, enterprise sites, hospital facilities and critical engineering consultancies. Some began as technicians and finished a degree. Others are engineers who want a busier, more commercial site. A few came from utility or manufacturing environments and moved into data centers for the shift pattern.
• They move for growth into management, for better hours or for a site with fewer legacy problems. Some are tired of single-tenant isolation and want variety. Others leave because customer pressure is not managed by their employer.
• Describe the customer base, the notification policy and who has the final word between sales and operations.
• Experienced candidates compare colocation operators on how they treat engineers in front of customers. If your management backs engineers when they push back, say so with an example. If sales pressure is heavy, say that too, so the person who accepts is not surprised.

Which hiring mistakes should you avoid?

Do not hire a single-tenant engineer and discover they resist customer notice rules. A routine change can become an incident. Do not let sales commit capacity the engineer has not confirmed. A missing source of truth becomes an argument. Do not ignore on-call expectations until the first night event.

• Hiring a single-tenant engineer and discovering they resist customer notice rules. A routine change can become an incident.
• Letting sales commit capacity the engineer has not confirmed. A missing source of truth becomes an argument.
• Ignoring on-call expectations until the first night event. Night events test the pattern.

Your search in 3 steps

1. Understand the customers

   We ask about customer profile, service levels and notice rules. That tells us how sensitive the engineer must be. We also ask how sales and operations divide authority over customer commitments.

2. Probe habits

   We ask candidates about windows, capacity and sales requests and report what they said. We pay attention to how they describe pushing back on a request.

3. Set terms

   We help you describe shifts, on-call and growth so the offer is clear. We also help you describe how engineers advance toward manager roles.

Explore the relevant desks

• Critical Facilities Engineer (CFE)
• Colocation and multi-tenant operators (retail and interconnection)

Start your search

Related hiring resources

• Critical Facilities Engineer (CFE) recruiting
• Colocation and multi-tenant operators (retail and interconnection)
• Hiring guide: Critical Facilities Operations
• Every Critical Facilities Operations title
• How long a search takes
• Interview questions for Critical Facilities Engineer (CFE)
• MOPs, SOPs and EOPs: what candidates should have written or followed
• Switching authority and the qualified person, in hiring terms
• Shift rotations in critical operations and how they change the search