Data Center Administrator

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. athenahealth, Inc. as a web-based practice management and electronic health record (EHR) software product, is a large and ever-changing ecosystem. We maintain thousands of servers, petabytes of storage and the entire infrastructure that supports them. The Data Center Engineering Team (DCEng), is responsible for the entire lifecycle of the physical devices and environmental conditions in our data centers. This involves communicating with vendors and internal teams to coordinate and execute the various maintenance tasks that are required to support and grow athenahealth and the needs of the operational teams. We need talented individuals to bring their technical expertise, creative thinking and enthusiasm to help us support and grow this complex environment" That's about the role. - Responsibilities: List after "Responsibilities Include:" then bullet points. Let's list them: - Share responsibility of 24x7 support of data center specific issues with other local team members - Manage the entire lifecycle of servers, storage and network equipment within the facility. Including receiving, racking, maintenance, and recycling. - Work closely with operations teams and vendors to ensure all server, storage, and networking equipment is operating optimally - Coordinate and execute the replacement of failed components - Coordinate, communicate and supervise facility maintenance - Perform daily walkthroughs of the facility to ensure no equipment error lights or inventory discrepancies - Ensure the data center, office and storage space is spotless at all times - Ensure our cable management meets department standards and enforce environment policies - Diagnose, troubleshoot, and resolve hardware or other network and physical connectivity problems. - Act as the first responder for all technical and facility related issues within the data center - Participate in problem solving and process improvement actions related to data center operations - Work with team-members on high-level planning, design and documentation projects related to power, cooling, layer 1 networking and policies - Provide remote hands support on physical server, network and telecommunications equipment for multiple groups - Establish and maintain relationship with data center facility manager/team - Contribute to the DCEng knowledge base, documentation and culture - Experience Required: list: - Ability to lift equipment up to 50 lbs required - Experience in a production data center environment highly preferred - Understanding of data center power and cooling infrastructure components is preferred - Deep understanding of server components and repair preferred - Ability to troubleshoot Dell and HP server hardware, opening support cases with vendors as needed preferred - Basic understanding of power and cooling systems in data environments preferred - Basic understanding of the Linux command line interface preferred - About Athenahealth: repeated sections about vision, location, culture, perks, compensation. We need sections: About the role (we have), Responsibilities (we have), Requirements (we have), Qualifications (maybe same as Experience Required? Could combine but we need separate sections if content). The posting has "Experience Required:" which could be considered Requirements. Also there is "About Athenahealth" which includes Vision, Location, Culture, Perks, Compensation. We can split into sections: About the company (maybe About Athenahealth) but the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: we have. - Responsibilities: we have. - Requirements: we have (Experience Required). - Qualifications: maybe we could include "Experience in a production data center environment highly preferred" etc but that's same as Requirements. Could also include "Ability to lift equipment up to 50 lbs required" etc. Might be redundant. Perhaps we treat Requirements as the list, and Qualifications could be omitted if no distinct content. But we must not emit empty headings. So we only include sections with real content. - Skills: maybe we could extract skills like "troubleshoot Dell and HP server hardware", "Linux command line", "power and cooling", etc. But those are already in Experience Required. Could create Skills section with those. However we must not invent content; we can reuse but need to ensure we are not duplicating? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid repeating info in different sections, but we should avoid unnecessary duplication? It says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe called Requirements (or Qualifications). But we need to follow allowed headings; we can choose which to include. Since we have both Requirements and Qualifications content overlapping, we could put all under Requirements and omit Qualifications. Or we could split: Requirements = ability to lift 50 lbs; Qualifications = preferred experience etc. But that seems artificial. Better: Use Requirements for the list of required/preferred qualifications. Then we could have Skills section for specific technical skills like "troubleshoot Dell and HP server hardware", "Linux command line", "power and cooling". But those are also in the list. Might be okay to split. But we must not create sections with filler like "not specified". We have actual content for Skills: we can list specific skills: troubleshooting Dell/HP server hardware, Linux CLI, power and cooling understanding, server components repair, etc. That's substantive. Benefits: The posting mentions "Along with health & financial benefits, our athenistas are offered a variety of perks that promote employee wellbeing such as commuter support (We were named one of the 2018 Best Workplaces for Commuters!), tuition reimbursement, collaborative workspaces and dog-friendly offices - just to name a few". Also later: "Along with health and financial benefits, athenistas enjoy perks specific to each location, including commuter support, employee assistance programs, tuition assistance, employee resource groups, and collaborative workspaces — some offices even welcome dogs." Also mentions flexibility, events, etc. So we have benefits/perks content. Pay: The posting includes "Expected Compensation $53,000 - $89,000 The base salary range shown reflects the full range for this role from minimum to maximum. At athenahealth, base pay depends on multiple factors, ...". So we have Pay. Schedule: Not mentioned explicitly. No schedule info. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We could also include Qualifications if we want but we can skip. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include job title heading. Also not include Job ID etc. We need to preserve all substantive information. Let's capture all prose. About the role paragraph: we need to keep it as is, maybe split into multiple paragraphs? The instruction: use

  for prose. So we can put the whole about role in one

  or split into multiple

  for readability but not required. We'll keep as one

  . Responsibilities: list each bullet as

• . Requirements: list each bullet as
• . Skills: we need to decide what to list. Let's extract specific skills from Experience Required list: - Ability to lift equipment up to 50 lbs required (maybe more physical requirement than skill) - Experience in a production data center environment highly preferred (experience) - Understanding of data center power and cooling infrastructure components is preferred (knowledge) - Deep understanding of server components and repair preferred (knowledge) - Ability to troubleshoot Dell and HP server hardware, opening support cases with vendors as needed preferred (skill) - Basic understanding of power and cooling systems in data environments preferred (knowledge) - Basic understanding of the Linux command line interface preferred (skill) We could also include other skills from responsibilities: cable management, remote hands support, etc. But those are duties. Better to keep Skills as the technical skills: troubleshooting Dell/HP server hardware, Linux CLI, power and cooling, server components repair, etc. We'll list them. Benefits: list perks: commuter support, tuition reimbursement, collaborative workspaces, dog-friendly offices, employee assistance programs, tuition assistance, employee resource groups, flexible work arrangements, events (book clubs, external speakers, hackathons), health & financial benefits, etc. We need to preserve all substantive info; we should not omit any. Let's capture benefits/perks text: From first perks paragraph: "Along with health & financial benefits, our athenistas are offered a variety of perks that promote employee wellbeing such as commuter support (We were named one of the 2018 Best Workplaces for Commuters!), tuition reimbursement, collaborative workspaces and dog-friendly offices - just to name a few" Later: "Along with health and financial benefits, athenistas enjoy perks specific to each location, including commuter support, employee assistance programs, tuition assistance, employee resource groups, and collaborative workspaces — some offices even welcome dogs. We also encourage a better work-life balance for athenistas with our flexibility. While we know in-office collaboration is critical to our vision, we recognize that not all work needs to be done within an office environment, full-time. With consistent communication and digital collaboration tools, athenahealth enables employees to find a balance that feels fulfilling and productive for each individual situation. In addition to our traditional benefits and perks, we sponsor events throughout the year, including book clubs, external speakers, and hackathons. We provide athenistas with a company culture based on learning, the support of an engaged team, and an inclusive environment where all employees are valued." Thus benefits include: health & financial benefits, commuter support, tuition reimbursement, collaborative workspaces, dog-friendly offices, employee assistance programs, tuition assistance, employee resource groups, flexibility (remote work options), events (book clubs, external speakers, hackathons), company culture based on learning, supportive team, inclusive environment. We'll list them as bullet list. Pay: we need to include the salary range and explanation. We'll put in

  . Now ensure we don't repeat boilerplate like "About Athenahealth" repeated sections; we already used About the role. The "About Athenahealth" sections about vision, location, culture, perks, compensation we have split into Benefits and Pay. The vision statement appears also in About the role paragraph? Actually the first line repeats vision: "Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all." That's part of About the role. The later "About Athenahealth Our Vision: To create a thriving ecosystem that delivers delivers accessible, high-quality, and sustainable healthcare for all." is duplicate; we should not repeat duplicate lines. We need to preserve all substantive information but remove duplicated lines. So we should include the vision statement only once. We'll keep it in About the role paragraph (the first sentence). We'll omit the later duplicate. Also duplicate "Our Vision: To create a thriving ecosystem that delivers delivers accessible, high-quality, and sustainable healthcare for all." has a typo "delivers delivers". We'll ignore duplicate. Also duplicate "About Athenahealth" sections about culture etc we already captured in Benefits and Pay; we should not repeat them. Now we need to ensure we didn't miss any substantive info like location: "Our Location: This role is ideally located in our Ashburn, VA data center". That's substantive; we need to include location somewhere. Where to put? Could be in About the role paragraph? Not present. Could be a separate section like "Location" but not in allowed headings. Could incorporate into About the role paragraph as a sentence. Since we must preserve all substantive info, we need to add location. We can add a sentence after the about role paragraph: "This role is ideally located in our Ashburn, VA data center." We'll put that in a

  maybe as part