Engineer, Data Center
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Benefits only if posting states them.
We need to parse the posting.
Content:
- Intro about LinkedIn (company description) maybe not needed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include the company description? It's part of job posting but not a section heading. Could be placed as a
before sections? The instruction says output only HTML fragment; we can include paragraphs as needed. There's no rule against including intro text. We'll include it as a
maybe.
- Job Description: "This role will be based in Hillsboro, OR. 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 on-site, meaning it will be performed in the specified office on a full-time basis due to the business needs of the team. As an onsite Data Center Engineer, you will be responsible for hardware deployments and acting as a point of escalation for our contracted employees responsible for addressing server break fix tickets. You will also assist Senior Data Center Engineers with the deployment of network, storage, and server nodes within your region."
That's prose.
- Then list: "We are looking for candidates with server and network hardware installation experience, network cabling experience, server break fix experience, experience troubleshooting Linux Kickstart issues, and Linux/Unix troubleshooting skills."
That's a list of requirements; could be
.
- Then "Responsibilities:" heading in source; we need to output Responsibilities
and then list items.
Responsibilities bullet points:
- Operate, monitor, and maintain the liquid-cooling infrastructure supporting LinkedIn's GPU and machine learning fleet, including Coolant Distribution Units (CDUs), secondary/technology cooling loops, manifolds, quick-disconnects, and rear-door heat exchangers.
- Monitor loop health — supply/return temperature (ΔT), differential pressure (ΔP), flow rate, and fluid conductivity — and act on alarms before they impact GPU availability.
- Perform and coordinate coolant sampling, water chemistry and fluid quality testing, filter changes, and fluid top-offs in accordance with OEM and LinkedIn standards.
- On a daily basis, review LinkedIn's DCIM Incident Dashboard and act on any fatal or warning incidents, escalating to your regional Site Supervisor or Senior Critical Infrastructure Engineer as necessary.
- Triage warning notifications to determine how they should be acted upon or suppressed.
- Monitor environmentals for all data center suites and ensure they remain within ASHRAE standards as defined in our leases with providers.
- Utilize internal tools (DCIM) and external tools (provider portals, BMS) to monitor power load, capacity, and environmental data across all data center suites.
- Review all MOPs, SOPs, and maintenance advisories provided by the facility operator; flag gaps, sequencing risk, or deviations from LinkedIn standards before work begins.
- Ensure major maintenance activities are captured in LinkedIn's internal change management process with appropriate risk classification, notification, and rollback plans.
- Maintain the regional Critical Infrastructure maintenance calendar and keep stakeholders informed of upcoming high-risk activities.
- Coordinate and schedule supplier/vendor onsite activities, including access, escort, and safety briefings.
- Exercise stop-work authority — recognize when vendor work is unsafe, out of sequence, or out of compliance, and halt the work to address concerns.
- In collaboration with the provider's site engineering team, support annual and quarterly preventive maintenance on all critical infrastructure, verifying that LinkedIn standards and industry best practices are followed.
- Support server, storage, and network deployments within your region — racking, cabling, initial configuration, and quality control of vendor-completed installs against LinkedIn cabling and labeling standards.
- Perform and support component-level hardware break-fix (DIMMs, CPUs, fans, power supplies, HDD/SSD/NVMe, risers) and serve as an escalation point for managed-services technicians.
- Troubleshoot physical-layer network issues across copper and fiber, including optics, console connectivity, and link and path validation.
That's a list.
- Then "Qualifications" heading in source; we need Qualifications
maybe split into Basic Qualifications and Preferred Qualifications? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a single Qualifications section with sublists? Could also have Requirements separate? The posting has "Basic Qualifications:" and "Preferred Qualifications:" and "Suggested Skills:" maybe we treat Skills as separate section.
We need to decide sections: About the role (maybe intro), Responsibilities, Requirements (maybe basic qualifications?), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule.
But we must only include sections when posting has real specific content. Let's see:
- About the role: we have introductory paragraph about role location, onsite, etc. That could be "About the role". We'll include that.
- Responsibilities: we have list.
- Requirements: we have "We are looking for candidates with ..." plus maybe Basic Qualifications list. Could combine.
- Qualifications: we have Basic Qualifications and Preferred Qualifications details.
- Skills: we have "Suggested Skills:" list.
- Benefits: posting mentions "Additional Information LinkedIn is committed to fair and equitable compensation practices. The pay range for this role is $90,000 to $148,000. Actual compensation packages are based on several factors... The total compensation package for this position may also include annual performance bonus, stock, benefits and/or other applicable incentive compensation plans. For more information, visit https://careers.linkedin.com/benefits."
Thus there is mention of benefits generally but not specific benefits list. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist (annual performance bonus, stock, benefits). However it's vague; but it does mention benefits. Should we include a Benefits section? It says "The total compensation package for this position may also include annual performance bonus, stock, benefits and/or other applicable incentive compensation plans." That's a statement about benefits existing but not enumerated. Might be considered substantive? It's not a list but it's a statement. The rule: "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')". The benefits statement is not filler; it's specific that there may be annual performance bonus, stock, benefits. So we could include a Benefits section with that statement as a
. However we also have Pay range specified, so we should include Pay section.
- Schedule: posting mentions work location on-site, full-time basis. That is schedule info: full-time, on-site. So we can include Schedule section with that.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to avoid duplication. Ensure we preserve all substantive information.
Let's extract content:
About the role: The paragraph: "This role will be based in Hillsboro, OR. 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 on-site, meaning it will be performed in the specified office on a full-time basis due to the business needs of the team. As an onsite Data Center Engineer, you will be responsible for hardware deployments and acting as a point of escalation for our contracted employees responsible for addressing server break fix tickets. You will also assist Senior Data Center Engineers with the deployment of network, storage, and server nodes within your region."
We'll put that as
.
Responsibilities: list as above.
Requirements: The line "We are looking for candidates with server and network hardware installation experience, network cabling experience, server break fix experience, experience troubleshooting Linux Kickstart issues, and Linux/Unix troubleshooting skills." plus maybe Basic Qualifications items? Actually Basic Qualifications are under Qualifications heading. But we can treat Requirements as the "We are looking for candidates..." list. We'll also include Basic Qualifications as part of Qualifications section.
Qualifications: Basic Qualifications list:
- Bachelor's Degree or equivalent industry experience.
- Relevant trade or technical certification (electrical, mechanical/HVAC, facilities, or military technical training) will also be considered.
- 2+ years in a data center operations, critical facilities, or comparable infrastructure role.
- Hands-on server hardware break-fix at the component level — DIMMs, CPUs, fans, power supplies, HDD/SSD/NVMe, risers, and cabling.
- Server and network deployment experience — racking, cabling, and initial configuration, including structured cabling and labeling standards and QC of vendor-completed installs.
- Physical-layer network troubleshooting across copper and fiber — optics and transceivers, console connectivity, link and path validation.
- Linux troubleshooting at the OS level (boot/POST, log review, basic system diagnosis).
- Experience with imaging or provisioning workflows such as kickstart, autobuild, or PXE.
- Out-of-band management experience — IPMI/BMC, iDRAC, iLO, or equivalent.
- Experience with data center critical infrastructure — UPS, generator, switchgear, PDUs and busway, and chiller plant — and an understanding of redundancy topology (N+1, 2N).
Preferred Qualifications list:
- Direct liquid-cooling experience — CDUs (Vertiv, Motivair, CoolIT, Boyd, nVent), rear-door heat exchangers, manifolds, quick-disconnects, and drip/leak detection.
- Adjacent closed-loop experience also applies: chilled-water HVAC, industrial process cooling, semiconductor fab facilities, power generation, or marine/Navy engineering.
- GPU and ML hardware exposure — NVIDIA HGX/DGX platforms, high-density rack deployments, and OEM break-fix coordination.
- Water chemistry and fluid quality management — conductivity, corrosion inhibitor and biocide treatment, PG25 vs. treated water, filtration micron ratings, and sampling cadence.
- MOP and SOP review experience — evaluating maintenance procedures before execution.
- Vendor or data center provider coordination, including escorting, scheduling, and holding third parties to standard.
Suggested Skills list:
- Experience with incident dashboards, DCIM, BMS, or provider portals, including the judgment to determine what to act on, escalate, or suppress.
- Ticket-driven operational discipline — owning a queue against SLA expectations and coordinating resolution across teams and vendors.
- Change management discipline in a live production environment, plus operational safety fundamentals (lockout/tagout, arc flash awareness, PPE, OSHA and state regulations).
- Ability to read schematics, P&IDs, and technical diagrams to determine the proper sequence of operations for maintenance activities.
We could put Suggested Skills under Skills section.
Benefits: The statement: "LinkedIn is committed to fair and equitable compensation practices. The pay range for this role is $90,000 to $148,000. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to skill set, depth of experience, certifications, and specific work location. This may be different in other locations due to differences in
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Benefits only if posting states them. We need to parse the posting. Content: - Intro about LinkedIn (company description) maybe not needed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Should we include the company description? It's part of job posting but not a section heading. Could be placed as a
before sections? The instruction says output only HTML fragment; we can include paragraphs as needed. There's no rule against including intro text. We'll include it as a
maybe. - Job Description: "This role will be based in Hillsboro, OR. 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 on-site, meaning it will be performed in the specified office on a full-time basis due to the business needs of the team. As an onsite Data Center Engineer, you will be responsible for hardware deployments and acting as a point of escalation for our contracted employees responsible for addressing server break fix tickets. You will also assist Senior Data Center Engineers with the deployment of network, storage, and server nodes within your region." That's prose. - Then list: "We are looking for candidates with server and network hardware installation experience, network cabling experience, server break fix experience, experience troubleshooting Linux Kickstart issues, and Linux/Unix troubleshooting skills." That's a list of requirements; could be
- .
- Then "Responsibilities:" heading in source; we need to output
Responsibilities
and then list items. Responsibilities bullet points: - Operate, monitor, and maintain the liquid-cooling infrastructure supporting LinkedIn's GPU and machine learning fleet, including Coolant Distribution Units (CDUs), secondary/technology cooling loops, manifolds, quick-disconnects, and rear-door heat exchangers. - Monitor loop health — supply/return temperature (ΔT), differential pressure (ΔP), flow rate, and fluid conductivity — and act on alarms before they impact GPU availability. - Perform and coordinate coolant sampling, water chemistry and fluid quality testing, filter changes, and fluid top-offs in accordance with OEM and LinkedIn standards. - On a daily basis, review LinkedIn's DCIM Incident Dashboard and act on any fatal or warning incidents, escalating to your regional Site Supervisor or Senior Critical Infrastructure Engineer as necessary. - Triage warning notifications to determine how they should be acted upon or suppressed. - Monitor environmentals for all data center suites and ensure they remain within ASHRAE standards as defined in our leases with providers. - Utilize internal tools (DCIM) and external tools (provider portals, BMS) to monitor power load, capacity, and environmental data across all data center suites. - Review all MOPs, SOPs, and maintenance advisories provided by the facility operator; flag gaps, sequencing risk, or deviations from LinkedIn standards before work begins. - Ensure major maintenance activities are captured in LinkedIn's internal change management process with appropriate risk classification, notification, and rollback plans. - Maintain the regional Critical Infrastructure maintenance calendar and keep stakeholders informed of upcoming high-risk activities. - Coordinate and schedule supplier/vendor onsite activities, including access, escort, and safety briefings. - Exercise stop-work authority — recognize when vendor work is unsafe, out of sequence, or out of compliance, and halt the work to address concerns. - In collaboration with the provider's site engineering team, support annual and quarterly preventive maintenance on all critical infrastructure, verifying that LinkedIn standards and industry best practices are followed. - Support server, storage, and network deployments within your region — racking, cabling, initial configuration, and quality control of vendor-completed installs against LinkedIn cabling and labeling standards. - Perform and support component-level hardware break-fix (DIMMs, CPUs, fans, power supplies, HDD/SSD/NVMe, risers) and serve as an escalation point for managed-services technicians. - Troubleshoot physical-layer network issues across copper and fiber, including optics, console connectivity, and link and path validation. That's a list. - Then "Qualifications" heading in source; we needQualifications
maybe split into Basic Qualifications and Preferred Qualifications? The instruction: Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a single Qualifications section with sublists? Could also have Requirements separate? The posting has "Basic Qualifications:" and "Preferred Qualifications:" and "Suggested Skills:" maybe we treat Skills as separate section. We need to decide sections: About the role (maybe intro), Responsibilities, Requirements (maybe basic qualifications?), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. Let's see: - About the role: we have introductory paragraph about role location, onsite, etc. That could be "About the role". We'll include that. - Responsibilities: we have list. - Requirements: we have "We are looking for candidates with ..." plus maybe Basic Qualifications list. Could combine. - Qualifications: we have Basic Qualifications and Preferred Qualifications details. - Skills: we have "Suggested Skills:" list. - Benefits: posting mentions "Additional Information LinkedIn is committed to fair and equitable compensation practices. The pay range for this role is $90,000 to $148,000. Actual compensation packages are based on several factors... The total compensation package for this position may also include annual performance bonus, stock, benefits and/or other applicable incentive compensation plans. For more information, visit https://careers.linkedin.com/benefits." Thus there is mention of benefits generally but not specific benefits list. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist (annual performance bonus, stock, benefits). However it's vague; but it does mention benefits. Should we include a Benefits section? It says "The total compensation package for this position may also include annual performance bonus, stock, benefits and/or other applicable incentive compensation plans." That's a statement about benefits existing but not enumerated. Might be considered substantive? It's not a list but it's a statement. The rule: "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')". The benefits statement is not filler; it's specific that there may be annual performance bonus, stock, benefits. So we could include a Benefits section with that statement as a
. However we also have Pay range specified, so we should include Pay section. - Schedule: posting mentions work location on-site, full-time basis. That is schedule info: full-time, on-site. So we can include Schedule section with that. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to avoid duplication. Ensure we preserve all substantive information. Let's extract content: About the role: The paragraph: "This role will be based in Hillsboro, OR. 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 on-site, meaning it will be performed in the specified office on a full-time basis due to the business needs of the team. As an onsite Data Center Engineer, you will be responsible for hardware deployments and acting as a point of escalation for our contracted employees responsible for addressing server break fix tickets. You will also assist Senior Data Center Engineers with the deployment of network, storage, and server nodes within your region." We'll put that as
. Responsibilities: list as above. Requirements: The line "We are looking for candidates with server and network hardware installation experience, network cabling experience, server break fix experience, experience troubleshooting Linux Kickstart issues, and Linux/Unix troubleshooting skills." plus maybe Basic Qualifications items? Actually Basic Qualifications are under Qualifications heading. But we can treat Requirements as the "We are looking for candidates..." list. We'll also include Basic Qualifications as part of Qualifications section. Qualifications: Basic Qualifications list: - Bachelor's Degree or equivalent industry experience. - Relevant trade or technical certification (electrical, mechanical/HVAC, facilities, or military technical training) will also be considered. - 2+ years in a data center operations, critical facilities, or comparable infrastructure role. - Hands-on server hardware break-fix at the component level — DIMMs, CPUs, fans, power supplies, HDD/SSD/NVMe, risers, and cabling. - Server and network deployment experience — racking, cabling, and initial configuration, including structured cabling and labeling standards and QC of vendor-completed installs. - Physical-layer network troubleshooting across copper and fiber — optics and transceivers, console connectivity, link and path validation. - Linux troubleshooting at the OS level (boot/POST, log review, basic system diagnosis). - Experience with imaging or provisioning workflows such as kickstart, autobuild, or PXE. - Out-of-band management experience — IPMI/BMC, iDRAC, iLO, or equivalent. - Experience with data center critical infrastructure — UPS, generator, switchgear, PDUs and busway, and chiller plant — and an understanding of redundancy topology (N+1, 2N). Preferred Qualifications list: - Direct liquid-cooling experience — CDUs (Vertiv, Motivair, CoolIT, Boyd, nVent), rear-door heat exchangers, manifolds, quick-disconnects, and drip/leak detection. - Adjacent closed-loop experience also applies: chilled-water HVAC, industrial process cooling, semiconductor fab facilities, power generation, or marine/Navy engineering. - GPU and ML hardware exposure — NVIDIA HGX/DGX platforms, high-density rack deployments, and OEM break-fix coordination. - Water chemistry and fluid quality management — conductivity, corrosion inhibitor and biocide treatment, PG25 vs. treated water, filtration micron ratings, and sampling cadence. - MOP and SOP review experience — evaluating maintenance procedures before execution. - Vendor or data center provider coordination, including escorting, scheduling, and holding third parties to standard. Suggested Skills list: - Experience with incident dashboards, DCIM, BMS, or provider portals, including the judgment to determine what to act on, escalate, or suppress. - Ticket-driven operational discipline — owning a queue against SLA expectations and coordinating resolution across teams and vendors. - Change management discipline in a live production environment, plus operational safety fundamentals (lockout/tagout, arc flash awareness, PPE, OSHA and state regulations). - Ability to read schematics, P&IDs, and technical diagrams to determine the proper sequence of operations for maintenance activities. We could put Suggested Skills under Skills section. Benefits: The statement: "LinkedIn is committed to fair and equitable compensation practices. The pay range for this role is $90,000 to $148,000. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to skill set, depth of experience, certifications, and specific work location. This may be different in other locations due to differences in