Mechanical Start-Up/Commissioning Specialist (Data Centers)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate (EEO, legal, etc). Must preserve all substantive info. Let's parse the posting. Content: - Intro paragraph about Jacobs mission. - "Your impact Here at Jacobs, we apply our expertise..." (some prose) - "As a Mechanical Start-Up and Commissioning Specialist, you'll join our collaborative team providing Commissioning and Start-Up services to clients in the Data Center Industry. The position provides an excellent opportunity to work for a Global Engineering Firm and support clients that operate mission-critical infrastructure." - "This position shall be responsible for the development of start-up and commissioning plans, commissioning documentation, and execution of these documents for mechanical systems, utility systems, and equipment. This role serves a diverse client base of hyperscale data centers, colocation facilities, and enterprise data center operators." - "We are looking for a passionate Mechanical Start-Up and Commissioning Specialist who is driven by collaboration, exceeding expectations, and challenging the status quo." - "You'll be accountable for providing mechanical start-up services including energization, commissioning, and visual inspection of HVAC systems, cooling infrastructure, chilled water systems, air handling units, and associated mechanical utilities to our clients." - "You will also be responsible for the following duties" then list: - Assist with project Start-Up and Commissioning Plan and execution strategies. - Assist with system Start-Up and Commissioning Plans for all mechanical systems. - Assist with generating and executing Start-Up and Commissioning documents according to industry best practices. - Assist with startup of mechanical equipment in a safe and effective manner. - Facilitate meetings for the start-up Team. - Maintain action item lists. - Maintain engineering change control logs. - Provide technical assistance and input. - Coordination of OEM Service technicians as needed. - Coordination with construction management firm as needed. - Apply engineering knowledge of, and experience with, HVAC, chilled water systems, cooling towers, pumps, air handling units, CRAC/CRAH units, instrumentation, controls, and building automation systems to support clients. - Bring your curiosity, talent for multi-tasking and collaboration, and extreme organizational skills and we'll help you grow, pursue and fulfill what drives you – so we can make big impacts on the world, together. - "Here's what you'll need" then list: - Bachelor’s degree in Mechanical Engineering or equivalent years of experience in lieu of degree - 5+ years of Start-Up and Commissioning experience in the data center industry or mission-critical facilities - Understanding of data center mechanical systems and cooling requirements. - Understanding of industry standards and best practices for mechanical commissioning - Flexibility and willingness to travel and work at various clients' locations. - "Ideally, you'll have" then list: - Proficient with Microsoft Office – Word, Excel - Ability to work well with diverse, multi-disciplined groups. - Ability to effectively communicate with management and fellow project team members - Ability to negotiate and compromise with other project team members to achieve project goals - Ability to listen and respect fellow project team member's ideas and opinions and work through conflicts or disagreements. - "Our health and welfare benefits are designed to invest in you, and in the things you care about. Your health. Your well-being. Your security. Your future. Employees have access to a 401(k) plan, as well as legally mandated benefits." - "The base salary range for this position is $102,900.00 to $141,500.00; though will be paid hourly based on hours worked. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training." - Then EEO etc (remove). - "Job posted on September 29, 2026. This position will be open for at least 3 days. Qualified applicants with criminal histories will be considered for employment" (metadata; can be short p or drop). We can include as a short p maybe. - "We value collaboration and believe that in-person interactions are crucial for both our culture and client delivery. We empower employees with our hybrid working policy, allowing them to split their work week between Jacobs offices/projects and remote locations enabling them to deliver their best work." - "Your application experience is important to us, and we’re keen to adapt to make every interaction even better. If you require further support or reasonable adjustments with regards to the recruitment process (for example, you require the application form in a different format), please contact the team via Careers Support." (application instructions; remove.) We must not include application instructions. So remove that last paragraph. We need to decide sections. We have: - About the role: could be intro describing Jacobs, mission, role overview. - Responsibilities: list of duties (the bullet list after "You will also be responsible for the following duties"). - Requirements: maybe the "Here's what you'll need" list (mandatory). - Qualifications: maybe the "Ideally, you'll have" list (preferred qualifications). Could also be Skills. - Skills: maybe the Microsoft Office proficiency etc. Could be part of Skills. - Benefits: health and welfare benefits, 401(k), legally mandated benefits. - Pay: base salary range and hourly note. - Schedule: hybrid working policy description (split work week between offices/projects and remote). That's schedule info. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good. Your impact Here at Jacobs, we apply our expertise and knowledge as we look into the future with great optimism and focus. We don't settle until we give our best and know that we're making a difference. As a Mechanical Start-Up and Commissioning Specialist, you'll join our collaborative team providing Commissioning and Start-Up services to clients in the Data Center Industry. The position provides an excellent opportunity to work for a Global Engineering Firm and support clients that operate mission-critical infrastructure. This position shall be responsible for the development of start-up and commissioning plans, commissioning documentation, and execution of these documents for mechanical systems, utility systems, and equipment. This role serves a diverse client base of hyperscale data centers, colocation facilities, and enterprise data center operators. We are looking for a passionate Mechanical Start-Up and Commissioning Specialist who is driven by collaboration, exceeding expectations, and challenging the status quo.

But note: we should avoid repeating the job title as heading, but we can mention it in prose. That's fine. But we might want to split About the role into a short paragraph summarizing Jacobs and role. Then Responsibilities:

Responsibilities

• ... each duty

We need to include all duties listed. List: - Assist with project Start-Up and Commissioning Plan and execution strategies. - Assist with system Start-Up and Commissioning Plans for all mechanical systems. - Assist with generating and executing Start-Up and Commissioning documents according to industry best practices. - Assist with startup of mechanical equipment in a safe and effective manner. - Facilitate meetings for the start-up Team. - Maintain action item lists. - Maintain engineering change control logs. - Provide technical assistance and input. - Coordination of OEM Service technicians as needed. - Coordination with construction management firm as needed. - Apply engineering knowledge of, and experience with, HVAC, chilled water systems, cooling towers, pumps, air handling units, CRAC/CRAH units, instrumentation, controls, and building automation systems to support clients. - Bring your curiosity, talent for multi-tasking and collaboration, and extreme organizational skills and we'll help you grow, pursue and fulfill what drives you – so we can make big impacts on the world, together. Note: The last bullet is more of a motivational statement; but it's part of responsibilities? It's under "You will also be responsible for the following duties" list? Actually after the list, there is a sentence: "Bring your curiosity, talent for multi-tasking and collaboration, and extreme organizational skills and we'll help you grow, pursue and fulfill what drives you – so we can make big impacts on the world, together." This seems like a closing motivational line, not a duty. Might be considered part of responsibilities? It's after the list but still part of the same paragraph. We could include it as a responsibility? It's more of a attribute. Might be better to treat as part of Skills or Qualifications. But we must preserve all substantive info; we can include it as a bullet under Responsibilities? It's not a duty but it's still content. Safer to include as a bullet under Responsibilities? Might be odd. Could include as a separate paragraph under Responsibilities? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that sentence somewhere. We could put it in a

under Responsibilities after the list, or as a final

. I'd treat it as a bullet under Responsibilities for simplicity. Now Requirements:

Requirements

• Bachelor’s degree in Mechanical Engineering or equivalent years of experience in lieu of degree
• 5+ years of Start-Up and Commissioning experience in the data center industry or mission-critical facilities
• Understanding of data center mechanical systems and cooling requirements.
• Understanding of industry standards and best practices for mechanical commissioning
• Flexibility and willingness to travel and work at various clients' locations.

Now Qualifications (or Skills): The "Ideally, you'll have" list. We could make a section

Preferred Qualifications

but the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have Qualifications and Skills separate. We need to decide what goes where. Qualifications could be the "Ideally, you'll have" list (preferred qualifications). Skills could be the Microsoft Office proficiency etc. But the "Ideally, you'll have" includes both skills and abilities. Could split: Qualifications: Bachelor's degree etc? Actually we already used Requirements for mandatory. Qualifications could be preferred qualifications (Ideally, you'll have). Skills could be technical skills like Microsoft Office proficiency, ability to work with diverse groups, communication, negotiation, listening, etc. But those are also abilities. Might be better to put all "Ideally, you'll have" under Skills, and keep Qualifications empty? But we must not create a section with filler. So we need to decide: either combine Qualifications and Skills into one section, or split them meaningfully. We have two lists: mandatory requirements (Requirements) and preferred qualifications (Ideally, you'll have). The latter includes both soft skills and technical proficiency. Could treat as Qualifications (preferred) and Skills (maybe none). But we need to avoid empty sections. We could make Qualifications = the "Ideally, you'll have" list, and Skills = maybe we could include Microsoft Office proficiency as a skill, but it's already in that list. So maybe we just have Qualifications and not Skills. But the instruction says we can have a few substantive sections over many thin ones. So we could omit Skills section if no specific skill content beyond what's already covered. However we have Microsoft Office proficiency etc. Could be considered Skills. But we could also include them under Qualifications. Better: Use Qualifications for