Building Engineer, Data Centers (Days)

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not put Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting. Key parts: - Intro: "JLL empowers you to shape a brighter way..." This is about company, maybe "About the role"? Actually "About the role" could be a short description of the role. The posting includes: "Building Engineer, Data Centers What this job involves - The Data Center Operations Engineer is responsible for delivery of best practice systems and problem resolution on all data center electrical and mechanical infrastructure (UPS, MV electrical systems, generators, cooling systems etc.)" Thus we can have an "About the role" section with that description. Then "What is your day to day? Your day-to-day tasks will include - ..." That's responsibilities. Then "Requirements Desired experience and technical skills - ..." That's requirements. Then "Preferred Corrigo experienceUniversal EPA 608 certificationTrained in NFPA70E" That's maybe qualifications or skills. Then "This position does not provide visa sponsorship. Candidates must be authorized to work in the United States without sponsorship. Location: On-site -Chandler, AZ" This is maybe location and work authorization; could be part of Requirements or maybe a separate "Qualifications"? But we can include location in a short paragraph maybe under "About the role"? However instructions: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and work auth in a paragraph maybe under "About the role" or a separate short paragraph not as heading. Then "If this job description resonates with you, we encourage you to apply..." That's application instruction, should be removed. Then "Personalized Benefits That Support Personal Well-being And Growth JLL recognizes the impact that the workplace can have on your wellness, so we offer a supportive culture and comprehensive benefits package that prioritizes mental, physical and emotional health. Some of these benefits may include: 401(k) plan with matching company contributionsComprehensive Medical, Dental & Vision CarePaid parental leave at 100% of salaryPaid Time Off and Company HolidaysEarly access to earned wages through Daily Pay". That's benefits. Then AI stuff: "At JLL, we harness the power of artificial intelligence (AI) to efficiently accelerate meaningful connections between candidates and opportunities..." That's maybe not needed? It's about recruitment process; could be considered boilerplate? It's not standard EEO but maybe still generic. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI part is not exactly those categories but could be considered generic recruiting fluff. I'd lean to remove it as it's not substantive job content. However we need to preserve ALL substantive information; does that include AI description? It's not about the job itself, it's about the hiring process. Likely considered boilerplate. We'll remove. Then "JLL Privacy Notice ..." That's legal boilerplate, remove. Then "Jones Lang LaSalle ("JLL") is an Equal Opportunity Employer..." That's EEO boilerplate, remove. Then "Pursuant to the Arizona Civil Rights Act..." etc. That's legal, remove. Then "Accepting applications on an ongoing basis until candidate identified." That's application instruction, remove. Thus final sections: About the role, Responsibilities, Requirements, Qualifications/Skills maybe combined, Benefits. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Pay or Schedule info. The posting mentions "Must be able to work different schedules. Must be able to work Holidays. Must be able to respond to site emergencies." That's schedule info. So we can include a Schedule section with that content. Pay: no mention of salary, so we should NOT create Pay section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We need to ensure we don't create empty sections. Now extract content for each. About the role: Could combine the introductory company blurb and the specific role description. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include a short paragraph about the role and maybe company overview. But we should preserve substantive information. The company overview is somewhat generic but maybe considered part of "About the role". However it's somewhat fluff but still part of posting. I'd include it as a paragraph. Thus About the role:

JLL empowers you to shape a brighter way. Our people at JLL are shaping the future of real estate for a better world by combining world class services, advisory and technology for our clients. We are committed to hiring the best, most talented people and empowering them to thrive, grow meaningful careers and to find a place where they belong. Whether you've got deep experience in commercial real estate, skilled trades or technology, or you're looking to apply your relevant experience to a new industry, join our team as we help shape a brighter way forward. Building Engineer, Data Centers - The Data Center Operations Engineer is responsible for delivery of best practice systems and problem resolution on all data center electrical and mechanical infrastructure (UPS, MV electrical systems, generators, cooling systems etc.).

But we might want to separate the company blurb from role specifics. However it's okay. Responsibilities: The day-to-day tasks list. We need to extract the bullet list after "What is your day to day? Your day-to-day tasks will include -". The text after that is a long sentence with many items separated by semicolons? Let's parse: "Responsible for maintaining, monitoring, and performing preventive maintenance and continuous operation of all building systems to maintain 100% Up-time including: fire/life safety, mechanical systems such as (HVAC, chillers, crac, crah, plumbing, controls), electrical including emergency backup systems such as (lighting, UPS, ATS, STS, PDU, generators, primary switchgear, power distribution, transformers), and hot water systems. Monitors operation, adjusts, and maintains refrigeration, chilled water, and air conditioning equipment; boilers, and ventilating and water heaters; pumps, valves, piping, and filters; other mechanical and electrical equipment. Must record readings and make and adjust where necessary to ensure proper operation of equipment.Requires the ability to analyze the operation of various systems, determine the cause of any problems/malfunctions and take corrective action as required. Comply with departmental policy for the safe storage, usage, and disposal of hazardous materials. Maintains a clean and safe workplace.Learn and understand the data center site in-order to manage incidents and events that put the critical systems at risk.Work order management, including CMMS, Vendor Management, and Customer Facing Tickets.Understanding and complying with emergency escalation procedures.Perform additional job duties as required." We need to turn this into

• items. We can split by sentences or logical items. Potential items: - Responsible for maintaining, monitoring, and performing preventive maintenance and continuous operation of all building systems to maintain 100% Up-time including: fire/life safety, mechanical systems such as (HVAC, chillers, crac, crah, plumbing, controls), electrical including emergency backup systems such as (lighting, UPS, ATS, STS, PDU, generators, primary switchgear, power distribution, transformers), and hot water systems. - Monitors operation, adjusts, and maintains refrigeration, chilled water, and air conditioning equipment; boilers, and ventilating and water heaters; pumps, valves, piping, and filters; other mechanical and electrical equipment. - Must record readings and make and adjust where necessary to ensure proper operation of equipment. - Requires the ability to analyze the operation of various systems, determine the cause of any problems/malfunctions and take corrective action as required. - Comply with departmental policy for the safe storage, usage, and disposal of hazardous materials. - Maintains a clean and safe workplace. - Learn and understand the data center site in order to manage incidents and events that put the critical systems at risk. - Work order management, including CMMS, Vendor Management, and Customer Facing Tickets. - Understanding and complying with emergency escalation procedures. - Perform additional job duties as required. We'll output each as
• . Now Requirements: The section "Requirements Desired experience and technical skills -". Then list: - Ability to traverse large, campus-like settings. - Lifting a minimum of 50 lbs. - Climbing stairs and navigating rooftops to access equipment. - Using ladders up to 30 ft and working from heights. - Ability to Climb a ladder with a 300-lb weight limit. - Must be able to work different schedules. - Must be able to work Holidays. - Must be able to respond to site emergencies. - 2+ years experience working in a data center/critical facility. - Experience with building systems, including: UPS systems, emergency generators, and switchgears. - Demonstrated verbal/written communication skills. - Working knowledge of computer applications including MS Office (Word, Excel, Outlook), Google Suite and CMMS. We'll put these as
  • . Now Qualifications: maybe we have "Preferred Corrigo experienceUniversal EPA 608 certificationTrained in NFPA70E". That's a bit jumbled: "Preferred Corrigo experienceUniversal EPA 608 certificationTrained in NFPA70E". Likely meaning: Preferred: Corrigo experience, Universal EPA 608 certification, Trained in NFPA70E. We'll split. Thus Qualifications section could contain these preferred qualifications. Skills: maybe we could separate technical skills from requirements? But we already have many skills in requirements. Could create Skills section for things like "Working knowledge of computer applications including MS Office (Word, Excel, Outlook), Google Suite and CMMS." But that's already in requirements. However we could move some to Skills. But we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We can keep them in Requirements and not create Skills if it would duplicate. Better to have Requirements cover experience and technical skills, and Skills maybe for soft skills like communication. But we already have communication in requirements. Could still create Skills for "Demonstrated verbal/written communication skills." and "Working knowledge of computer applications..." but that would duplicate. Safer to not create Skills section if it would be thin or duplicate. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills section and keep those items under Requirements or Qualifications. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Now Benefits: list: - 401(k) plan with matching company contributions - Comprehensive Medical, Dental & Vision Care - Paid parental leave at 100% of salary - Paid Time Off and Company Holidays - Early access to earned wages through Daily Pay We'll output as
    • . Schedule: from requirements we have "Must be able to work different schedules. Must be able to work Holidays. Must be able to respond to site emergencies." Also maybe "Must be able to work different schedules." Already captured. We'll create Schedule section with those items. We should not duplicate the schedule items also in Requirements; but we need to preserve all info. If we move schedule items to Schedule section, we should remove them from Requirements to avoid duplication. However the instruction says preserve ALL substantive information; we can keep them in both places? That would be duplication but still preserving. However better to avoid duplication but still preserve by moving them to Schedule and removing from