Critical Support Specialist, NA - Chiller Engineer, NA

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: About Vantage (company description) and Site Operations Department description, Position Overview, Essential Job Functions, Duties by Specialization (list), Job Requirements, Physical Demands And Special Requirements, Additional Details (benefits, salary range). Also mention travel 15-20% etc. We need to map to headings: About the role (maybe combine company description and position overview). Responsibilities (Essential Job Functions + Duties by Specialization). Requirements (Job Requirements). Qualifications? Might be overlapping with Requirements; but we can include Qualifications as maybe formal training/certifications. Skills maybe not explicit. Benefits (Additional Details benefits). Pay (Salary Range). Schedule (work schedule Monday-Friday day shift, travel 15-20%). Also maybe Physical Demands could be part of Requirements or separate but we don't have a heading for that; we could include under Requirements or maybe under Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. We can include Physical Demands under Requirements or maybe under Qualifications? Probably under Requirements (since it's job requirements). We'll embed physical demands in a

under Requirements. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove "Don't meet all the requirements? Please still apply..." etc. Also remove "Vantage is an Equal Opportunity Employer..." etc. Also remove "We operate with No Ego..." etc? That's cultural description maybe not boilerplate but could be considered fluff; but it's substantive? It's about culture; maybe keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The cultural statements are not boilerplate; they might be okay but could be considered fluff. However they are not duplicated. Might keep as part of About the role? But we need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep cultural statements if they are substantive. However they are not required headings; we can include them in About the role paragraph. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Vantage powers, cools, protects and connects the technology of the world’s well-known hyperscalers, cloud providers and large enterprises. Developing and operating across North America, EMEA and Asia Pacific, Vantage has evolved data center design in innovative ways to deliver dramatic gains in reliability, efficiency and sustainability in flexible environments that can scale as quickly as the market demands. The Site Operations Department is responsible for the overall health of all mechanical and electrical systems, building maintenance, and performance of all data modules in our data centers. The team is staffed 24 x 7 onsite with Critical Facility Engineers (CFEs) on each shift. This team is the face of Vantage to our customers and the first line of defense regarding the uptime of our campus as well as the performance of our customer installations. Using a Critical Maintenance Management System (CMMS) to plan and track work needed, the Site Operations department performs all preventative and corrective maintenance. Our culture expects and rewards team performance that engages directly with the customers and the facility infrastructure. This is a team that does most of the actual work versus calling upon vendors. As a result, we provide superior service that is faster and more cost effective. Position Overview: Critical Support Specialist roles are SMEs and highly-trained in specific areas within the data center electrical/mechanical space. This particular CSS is available for a Hands-on Chiller Tech-Engineer / Commercial-Industrial HVAC to be a Subject Matter Expert for our Santa-Clara, CA or Reno, NV campuses. This role will be working onsite Monday - Friday day shift. This role additionally will travel 15-20% in North America, mostly in the United States data center campuses. We are looking for a Critical Support Specialist who knows what best-in-class service looks like and can make that a reality. This role is a crucial member of our facilities team, managing some of the most efficient and cost-effective data center facilities in the industry. The successful candidate for this role will work with a team of other electrical and mechanical-focused engineers performing maintenance and repair for our data center infrastructure. We take our customer requirements for uptime seriously and keep our facilities maintained to a very high standard to ensure uninterrupted service for our customers. If you enjoy working on critical data center systems (UPSs, PDUs, Diesel Generators, ATS equipment and Building Controls), as well as industrial electrical equipment and systems that include power distribution components/wiring, electronic components, and lighting systems, know the importance of getting it right the first time and not disrupting mission critical data centers, and enjoy delighting customers with superior service, then please read on!

But we need to separate Responsibilities etc. Let's create sections:

Responsibilities

• Perform detailed, specialized maintenance, troubleshooting, and operational tasks within your area of expertise, ensuring uninterrupted data center operations.
• Independently manage complex maintenance projects and system enhancements with minimal supervision.
• Respond effectively to safety incidents and emergency situations, maintaining a secure work environment.
• Exercise discretion and judgment in adapting workflows to shifting priorities.
• Collaborate frequently with internal teams across multiple organizational levels and externally with vendors and technical partners.
• Additional duties as assigned by Management.

Duties by Specialization – HVAC/Chiller Engineer

But we only allowed headings from list; we cannot create custom heading like "Duties by Specialization – HVAC/Chiller Engineer". However we could incorporate those duties under Responsibilities as sub-items? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create additional headings. We can embed the specialization duties inside Responsibilities as a nested list or as paragraphs. Thus under Responsibilities we can have a paragraph describing HVAC specialization duties, maybe as a

inside. Let's do:

Responsibilities

Perform detailed, specialized maintenance, troubleshooting, and operational tasks within your area of expertise, ensuring uninterrupted data center operations. Independently manage complex maintenance projects and system enhancements with minimal supervision. Respond effectively to safety incidents and emergency situations, maintaining a secure work environment. Exercise discretion and judgment in adapting workflows to shifting priorities. Collaborate frequently with internal teams across multiple organizational levels and externally with vendors and technical partners. Additional duties as assigned by Management.

For the HVAC/Chiller Engineer specialization:

• Oversee comprehensive operations and detailed maintenance of critical HVAC infrastructure systems, including chilled water and condenser water systems, computer room air handlers (CRAH), computer room air conditioners (CRAC), humidity control systems, leak detection, commercial AC systems, constant and variable airflow systems, boilers, and air compressors.
• Provide technical leadership focused on optimization, innovation, and operational excellence within HVAC systems.
• Develop and implement detailed preventive and predictive maintenance strategies, integrating advanced techniques and data-driven decision-making.
• Act as an HVAC subject matter expert, leading efforts to resolve complex operational issues, overseeing major system upgrades, and consistently optimizing energy efficiency.
• Mentor junior personnel and contribute significantly to the development of industry standards, training programs, and technological advancements.
Now Requirements:

Requirements

• Minimum 8 years (10+ years preferred) of direct hands-on experience specializing in maintenance and repair within mission-critical environments, specifically in your area of expertise.
• Extensive knowledge of maintenance practices and operational standards relevant to your specialization (Low Voltage, Medium Voltage, UPS, Generators, HVAC).
• Proven ability to read and interpret technical schematics, blueprints, and operational manuals.
• Strong technical writing capabilities, with experience creating and updating method of procedures (MOPs), standard operating procedures (SOPs), and emergency operating procedures (EOPs).
• Completion of formal specialized training (e.g., UPS systems, generator maintenance, chiller systems).
• Current professional licensure or certification relevant to your technical specialization.
• Occasional travel (less than 5%) for training and professional development. This may increase as the business evolves.
• Successful completion of a background check.
• Travel expected to range from 15-20% within North America (US / Canada).

Physical demands: Ability to stand 1/3 – 2/3 of the time; walk 1/3 – 2/3 of the time; sit 1/3 – 2/3 of the time; climb and balance 1/3 – 2/3 of the time; stoop, kneel, crouch and crawl 1/3 – 2/3 of the time; reach with hands & arms 1/3 – 2/3 of the time; smell, talk & hear; use hands to type, handle & feel; reach with hands and arms; see at close and distance ranges and the ability to see color; must be comfortable working in a high stress, fast paced environment with shifting priorities; must be willing to work outside normal business hours, including weekends, late nights, holidays, and on-call support; ability to lift up to 50 pounds 1/3 of the time.

Now Benefits:

Benefits

This position is eligible for company benefits including but not limited to medical, dental, and vision coverage, life and AD&D, short and long-term disability coverage, paid time off, employee assistance, participation in a 401k program that includes company match, and many other additional voluntary benefits.

Pay:

Pay

Salary Range: $71-72/hour + annual bonus. Compensation for the role will depend on a number of factors, including your location, qualifications, skills, competencies, and experience and may fall outside of the range shown.

Schedule:

Schedule

This role will be working onsite Monday - Friday day shift. Additionally, travel 15-20% in North America, mostly in the United States data center campuses.

We should not include sections like Qualifications or Skills if no specific content. We could combine Qualifications with Requirements but we have Requirements already. We could add Qualifications heading if we have content like formal training, certifications. But we already have those under Requirements. To avoid duplication, we could omit Qualifications and Skills. Thus final HTML fragment includes headings: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check that we didn't repeat job title. Good. We removed boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions, "Don't meet all the requirements? Please still apply..." etc. Also removed cultural statements like "We operate with No Ego and No Arrogance..." etc. That is maybe considered fluff but not boilerplate