Sr. Engineer, Data Center

We need to output HTML fragment with sections: About the role? The posting includes a description paragraph before responsibilities. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content: The posting includes: - Intro about LinkedIn (maybe not needed? It's generic corporate fluff, but it's part of description. Might be considered boilerplate? It's not EEO but it's generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The intro about LinkedIn is not specifically listed as boilerplate, but it's generic fluff. However, we need to preserve ALL substantive information; do NOT invent or summarize away detail. The intro about LinkedIn is not directly about the role; but it's part of job description. Might be considered "About the role" content? The instruction says we can have an "About the role" heading. So we could put that intro under About the role. Then: "Job Description This role will be based in Ashburn, VA. At LinkedIn, our approach to flexible work is centered on trust and optimized for culture, connection, clarity, and the evolving needs of our business. The work location of this role is hybrid, meaning it will be performed both from home and from a LinkedIn office on select days, as determined by the business needs of the team." That's location and work arrangement. Then: "We are seeking a Data Center Engineer, Field Engineering to support owner-side infrastructure validation, commissioning and operational readiness for mission-critical data center facilities across North America. This hands-on, multidisciplinary field engineering role focuses on verifying that mechanical, electrical, cooling, controls, low-voltage, and white-space infrastructure is installed correctly, performs as designed, and is ready for safe and reliable operation. The role places particular emphasis on high-density computing environments, including liquid-cooled GPU and AI infrastructure. You will collaborate with engineering, construction, commissioning, operations, vendors, and equipment manufacturers to identify technical issues, evaluate system performance, determine root causes, validate corrective actions and drive issues through resolution. You will serve as an owner-side technical resource, bridging design intent, installed conditions, commissioning results and operational requirements. Success in this role requires engineering judgment, troubleshooting skills, attention to detail and the ability to communicate technical findings clearly to both technical and non-technical stakeholders." That's role overview. Then "Responsibilities:" followed by bullet-like sentences (each starting with a verb). We need to turn those into

  • . Then "Qualifications Basic Qualifications:" list of items (each sentence). Then "Preferred Qualifications:" list. Then "Suggested Skills:" list (comma-separated). Then "Additional Information" includes pay range and benefits mention. Then EEO statements etc which we need to remove. We need to decide sections: About the role (intro + location + role overview). Responsibilities (list). Requirements (maybe combine Basic and Preferred Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications (basic and preferred) and Skills. Could have a Qualifications section with both basic and preferred? Or separate Basic and Preferred under Qualifications? Probably better to have Qualifications heading and then list items (maybe separate basic and preferred as sublists? But we must not invent headings not in the list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Qualifications for both basic and preferred. Could also use Requirements for basic qualifications? But we have both basic and preferred; maybe we put basic under Qualifications and preferred under Skills? But Skills heading is for suggested skills. The posting has "Suggested Skills:" which is a list of skills. So we can put that under Skills heading. Thus: - About the role: includes intro paragraph about LinkedIn, location/hybrid, role overview. - Responsibilities: list of responsibilities. - Qualifications: list of basic qualifications (maybe also include preferred? but we could put preferred under Qualifications as well, but then we would duplicate? Might be okay to combine both basic and preferred under Qualifications, but we need to preserve all info. Could separate into two sublists? Not required; we can just list all qualifications (basic and preferred) as items. However, the posting distinguishes basic vs preferred; we could keep that distinction by adding a note like "Basic Qualifications:" as a inside the list? But we must not invent headings; we can include plain text before list items. Probably acceptable to have a

    with "Basic Qualifications:" then

    for those, then another

    for "Preferred Qualifications:" then

    . That's still under Qualifications heading. - Skills: list of suggested skills. - Pay: we have pay range $109,000 to $180,000. Also mention total compensation may include bonus, stock, benefits. So we can create a Pay section with that info. - Benefits: The posting mentions benefits via link but not specific benefits. It says "total compensation package may also include annual performance bonus, stock, benefits and/or other applicable incentive compensation plans." and link to benefits page. That's not specific benefits; we should not create Benefits section unless posting actually states them. It mentions benefits generically but not list. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay range, so Pay section is okay. Benefits: it mentions benefits but not specific; maybe we should not create Benefits section because no specific benefits listed. However, the phrase "benefits" is mentioned but not enumerated. Safer to omit Benefits section. - Schedule: not mentioned (no schedule details). So omit. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay. Now we need to strip boilerplate: Remove LinkedIn generic intro? It's not EEO but it's generic marketing. However, it's part of the job description; we might keep it under About the role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The generic LinkedIn intro is not those; we can keep. We also need to remove duplicated lines: there are duplicated Equal Opportunity Statement etc. We'll remove those. Also remove "Additional Information" heading? We'll incorporate pay info. Now craft HTML. We'll start with

    About the role

    then

    ... combined paragraphs. We need to ensure we preserve all substantive info: location Ashburn, VA, hybrid, role description, responsibilities list, qualifications basic and preferred, suggested skills, pay range and total comp note. Let's extract each piece. About the role content: - "LinkedIn is the world's largest professional network, built to create economic opportunity for every member of the global workforce. Our products help people make powerful connections, discover exciting opportunities, build necessary skills, and gain valuable insights every day. We're also committed to providing transformational opportunities for our own employees by investing in their growth. We aspire to create a culture that's built on trust, care, inclusion, and fun – where everyone can succeed. Join us to transform the way the world works." - "Job Description This role will be based in Ashburn, VA. At LinkedIn, our approach to flexible work is centered on trust and optimized for culture, connection, clarity, and the evolving needs of our business. The work location of this role is hybrid, meaning it will be performed both from home and from a LinkedIn office on select days, as determined by the business needs of the team." - "We are seeking a Data Center Engineer, Field Engineering to support owner-side infrastructure validation, commissioning and operational readiness for mission-critical data center facilities across North America. This hands-on, multidisciplinary field engineering role focuses on verifying that mechanical, electrical, cooling, controls, low-voltage, and white-space infrastructure is installed correctly, performs as designed, and is ready for safe and reliable operation. The role places particular emphasis on high-density computing environments, including liquid-cooled GPU and AI infrastructure. You will collaborate with engineering, construction, commissioning, operations, vendors, and equipment manufacturers to identify technical issues, evaluate system performance, determine root causes, validate corrective actions and drive issues through resolution. You will serve as an owner-side technical resource, bridging design intent, installed conditions, commissioning results and operational requirements. Success in this role requires engineering judgment, troubleshooting skills, attention to detail and the ability to communicate technical findings clearly to both technical and non-technical stakeholders." We can combine into a few paragraphs. Now Responsibilities list: each sentence after "Responsibilities:": - Perform field engineering activities across data center mechanical, electrical, cooling, controls, low-voltage and white-space infrastructure. - Review engineering drawings, specifications, equipment submittals, sequences of operation, and technical design packages. - Verify installed conditions against approved designs, technical standards, manufacturer requirements, and operational needs. - Identify installation discrepancies, integration concerns, technical risks, and potential operational impacts. - Conduct technical field inspections focused on functionality, quality, maintainability, and readiness for testing and commissioning. - Evaluate system performance and support troubleshooting and root-cause analysis for field and system-level issues. - Document field observations, deficiencies, test results, and recommended corrective actions. - Support issue resolution and verify that corrective actions satisfy design, performance, and operational requirements. - Communicate technical findings through reports, issue logs, photographs, and stakeholder updates. - Support validation and commissioning of liquid-cooling systems serving high-density compute, GPU, and AI environments. - Evaluate CDUs, coolant distribution networks, rack-level cooling, manifolds, leak detection, controls, monitoring, and associated mechanical systems. - Verify installations against approved drawings, specifications, sequences of operation, and manufacturer requirements. - Assess temperatures, pressures, flow rates, instrumentation, alarms, control responses, and overall system performance. - Troubleshoot leaks, cooling-performance deficiencies, control issues, sensor discrepancies, communication failures, and system-level anomalies. - Support root-cause analysis, corrective-action development, and resolution validation. - Collaborate with engineering, vendors, commissioning teams, and operations to confirm system performance and operational readiness. - Support post-turnover monitoring, performance optimization, and reliability improvements. We'll put each as

    • . Now Qualifications: Basic Qualifications list: - Bachelor’s degree in Mechanical Engineering, Electrical Engineering, Controls Engineering, or a related technical field, or equivalent practical experience. - Experience in field engineering, infrastructure engineering, commissioning, system validation, or data center engineering. - Experience working in data center, mission-critical, industrial, manufacturing, utility, or similarly complex infrastructure environments. - Experience with at least one major infrastructure discipline, including mechanical, electrical, cooling, controls, or low-voltage systems. - Experience performing field inspections, installation verification, functional testing, commissioning support, or operational-readiness activities. - Ability to read and interpret engineering drawings, specifications, equipment submittals, sequences of operation, single-line diagrams, piping and controls diagrams, and technical design packages. - Experience identifying and documenting field discrepancies, equipment faults, integration concerns