Data Center Engineer
for sections: 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. Include a section only when posting has real, specific content for it—never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key info:
Location: Sparks, NV (Onsite)
Schedule: 4x10 Hour Shifts
Pay: Up to $45/hour
Then description: "Build the Future of High-Performance Infrastructure ..."
Then "Available Shifts (4x10 Schedule)" with times.
Then "Key Responsibilities" list.
Then "Required Qualifications" list.
Then "Preferred Qualifications" list.
Then "Why Join Us?" bullet list.
Then "Important Information" about onsite, commute, schedule.
Then later: "#MPipe26 Job Type & Location This is a Contract position based out of Sparks, NV. Pay And Benefits The pay range for this position is $45.00 - $45.00/hr. Individual compensation offered ..."
Then benefits list.
Then "Workplace Type This is a fully onsite position in Sparks,NV."
Then "Application Deadline This position is anticipated to close on Sep 18, 2026."
Then about TEKsystems etc (boilerplate). We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the TEKsystems description, equal opportunity statements, etc. Also drop "Application Deadline"? The instruction says remove application instructions. Application deadline maybe considered application instruction? Probably yes, remove. Also drop "Job Type & Location" maybe not needed as we have location and schedule already. But we need to preserve substantive info: location, schedule, pay, responsibilities, required qualifications, preferred qualifications, why join us (benefits of joining), benefits (medical etc). Also maybe "Contract position" is job type; could be included in a short paragraph.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
We have:
- About the role: we have description paragraph: "Build the Future of High-Performance Infrastructure We are seeking experienced Data Center Engineers..." That's about the role. So we can put that in
About the role
with .
- Responsibilities: we have "Key Responsibilities" list. So
Responsibilities
with - .
- Requirements: Could be "Required Qualifications". That's requirements. So
Requirements
with - .
- Qualifications: Could be "Preferred Qualifications". That's qualifications (preferred). So
Qualifications
with - .
- Skills: Could be derived from required/preferred but maybe we can combine? The instruction says prefer few substantive sections over many thin ones. Could we merge Requirements and Qualifications into one? But they ask to use headings for those specific names if we have content. We have both required and preferred; we could make Requirements for required, Qualifications for preferred. That's two sections.
- Skills: maybe we can extract skills like Linux, troubleshooting, etc. But we already have them in required/preferred. Could we create a Skills section? Might be thin. Better to omit Skills if not distinct.
- Benefits: we have benefits list (medical, dental, vision, etc). So
Benefits
with - .
- Pay: we have pay range: Up to $45/hour, also $45.00 - $45.00/hr (fixed). So we can put Pay section with
stating pay.
- Schedule: we have schedule: 4x10 Hour Shifts, with details: Sunday - Wednesday 7:00 AM - 6:00 PM, 9:00 AM - 8:00 PM? Actually they list two time ranges? The posting shows:
Available Shifts (4x10 Schedule)
Sunday - Wednesday 7:00 AM - 6:00 PM
9:00 AM - 8:00 PM
Wednesday - Saturday 7:00 AM - 6:00 PM
9:00 AM - 8:00 PM
Probably meaning two shift options: either 7am-6pm or 9am-8pm, both 4x10. We'll capture that.
Thus Schedule section with
describing.
We must not include filler like "commensurate with experience". Not present.
We must not repeat job title as heading. Not.
We must not put Job ID/requisition numbers as headings. There's "#MPipe26". We'll ignore.
We must remove boilerplate: TEKsystems description, EEO statements, etc.
We must not include application instructions: like "Apply today", "Application Deadline". Remove.
We must preserve all substantive information.
Thus final HTML fragment:
About the role
Build the Future of High-Performance Infrastructure We are seeking experienced Data Center Engineers to join a cutting-edge operations team supporting advanced computing infrastructure. This is an excellent opportunity for individuals with strong data center, hardware, Linux, and troubleshooting experience who enjoy working in fast-paced, highly technical environments. As a Data Center Engineer, you will work alongside engineering, operations, and infrastructure teams to deploy, maintain, troubleshoot, and optimize large-scale compute systems. You will play a key role in ensuring system performance, reliability, and operational excellence.
Responsibilities
- Perform rack-and-stack deployments, hardware installations, and infrastructure builds.
- Execute structured cabling and connectivity validation for data center environments.
- Troubleshoot hardware, infrastructure, Linux, and system performance issues.
- Support engineering teams with testing, validation, deployment, and operational initiatives.
- Monitor system health and assist with maintaining high availability across critical infrastructure.
- Participate in hardware break/fix, component replacement, upgrades, and recovery efforts.
- Create and maintain Standard Operating Procedures (SOPs) and operational documentation.
- Collect and analyze system metrics to identify opportunities for performance improvement.
- Drive efficiency initiatives that improve uptime, throughput, testing accuracy, and overall operational performance.
- Collaborate closely with cross-functional technical teams to support next-generation technologies and deployments.
Requirements
- Experience working in a data center, laboratory, or large-scale technical infrastructure environment.
- Hands-on experience with: rack and stack deployments, structured cabling, hardware installation and troubleshooting, data center maintenance, infrastructure support.
- Working knowledge of Linux and command-line troubleshooting.
- Experience testing, validating, and deploying hardware platforms.
- Strong problem-solving and analytical skills.
- Excellent written and verbal communication abilities.
- Ability to work effectively in a collaborative, team-oriented environment.
Qualifications
- Experience with DCIM platforms such as Nautobot or similar tools.
- Scripting or automation experience with Shell, Python, Ansible, or related technologies.
- Knowledge of networking concepts and protocols including: TCP/IP, DNS, NFS, SSL.
- Experience supporting servers, GPUs, PCBs, or high-performance computing environments.
- Previous experience in mission-critical infrastructure environments.
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
Pay
Up to $45/hour (pay range $45.00 - $45.00/hr).
Schedule
4x10 hour shifts. Available shift patterns: Sunday–Wednesday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM; Wednesday–Saturday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM.
We need to ensure we didn't include any filler like "commensurate with experience". Not present.
Check for duplication: We included location? Not needed as heading but we could include location in About the role paragraph? Already we have location in description? Not explicitly. The location is given at top: "Location: Sparks, NV (Onsite)". We could include that in About the role paragraph or maybe a separate short paragraph. But we have no heading for location; we could embed it in About the role. Let's add location info there.
Update About the role paragraph to include location: "Located in Sparks, NV (onsite)." Also mention schedule? Already schedule separate.
Thus About the role paragraph: "Build the Future of High-Performance Infrastructure We are seeking experienced Data Center Engineers to join a cutting-edge operations team supporting advanced computing infrastructure. This is an excellent opportunity for individuals with strong data center, hardware, Linux, and troubleshooting experience who enjoy working in fast-paced, highly technical environments. As a Data Center Engineer, you will work alongside engineering, operations, and infrastructure teams to deploy, maintain, troubleshoot, and optimize large-scale compute systems. You will play a key role in ensuring system performance, reliability, and operational excellence. Located in Sparks, NV (onsite)."
Now check for any leftover boilerplate: We removed TEKsystems description, EEO, etc. Also removed "Important Information" about commute and schedule? We included schedule; commute mention maybe not needed. Could add a sentence about commute in About the role or Schedule? The posting says: "Candidates must be able to reliably commute to the site and work one of the designated 4x10 schedules." That's substantive. We could add to Schedule paragraph: "Candidates must be able to reliably commute to the site and work one of the designated 4x10 schedules." Let's add.
Thus Schedule paragraph: "4x10 hour shifts. Available shift patterns: Sunday–Wednesday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM; Wednesday–Saturday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM. Candidates must be able to reliably commute to the site and work one of the designated 4x10 schedules."
Now check for any other substantive info: "Contract position" maybe we could include in About the role or a short note. Could add to About the role: "This is a contract position." Let's add.
Thus About the role paragraph: add "This is a contract position." after location maybe.
Now final HTML.
Check that we didn't include any heading with empty content. All sections have content.
Now output only HTML
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Include a section only when posting has real, specific content for it—never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key info: Location: Sparks, NV (Onsite) Schedule: 4x10 Hour Shifts Pay: Up to $45/hour Then description: "Build the Future of High-Performance Infrastructure ..." Then "Available Shifts (4x10 Schedule)" with times. Then "Key Responsibilities" list. Then "Required Qualifications" list. Then "Preferred Qualifications" list. Then "Why Join Us?" bullet list. Then "Important Information" about onsite, commute, schedule. Then later: "#MPipe26 Job Type & Location This is a Contract position based out of Sparks, NV. Pay And Benefits The pay range for this position is $45.00 - $45.00/hr. Individual compensation offered ..." Then benefits list. Then "Workplace Type This is a fully onsite position in Sparks,NV." Then "Application Deadline This position is anticipated to close on Sep 18, 2026." Then about TEKsystems etc (boilerplate). We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the TEKsystems description, equal opportunity statements, etc. Also drop "Application Deadline"? The instruction says remove application instructions. Application deadline maybe considered application instruction? Probably yes, remove. Also drop "Job Type & Location" maybe not needed as we have location and schedule already. But we need to preserve substantive info: location, schedule, pay, responsibilities, required qualifications, preferred qualifications, why join us (benefits of joining), benefits (medical etc). Also maybe "Contract position" is job type; could be included in a short paragraph. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: we have description paragraph: "Build the Future of High-Performance Infrastructure We are seeking experienced Data Center Engineers..." That's about the role. So we can put that in
About the role
with. - Responsibilities: we have "Key Responsibilities" list. So
Responsibilities
with- .
- Requirements: Could be "Required Qualifications". That's requirements. So
Requirements
with- .
- Qualifications: Could be "Preferred Qualifications". That's qualifications (preferred). So
Qualifications
with- .
- Skills: Could be derived from required/preferred but maybe we can combine? The instruction says prefer few substantive sections over many thin ones. Could we merge Requirements and Qualifications into one? But they ask to use headings for those specific names if we have content. We have both required and preferred; we could make Requirements for required, Qualifications for preferred. That's two sections.
- Skills: maybe we can extract skills like Linux, troubleshooting, etc. But we already have them in required/preferred. Could we create a Skills section? Might be thin. Better to omit Skills if not distinct.
- Benefits: we have benefits list (medical, dental, vision, etc). So
Benefits
with- .
- Pay: we have pay range: Up to $45/hour, also $45.00 - $45.00/hr (fixed). So we can put Pay section with
stating pay. - Schedule: we have schedule: 4x10 Hour Shifts, with details: Sunday - Wednesday 7:00 AM - 6:00 PM, 9:00 AM - 8:00 PM? Actually they list two time ranges? The posting shows: Available Shifts (4x10 Schedule) Sunday - Wednesday 7:00 AM - 6:00 PM 9:00 AM - 8:00 PM Wednesday - Saturday 7:00 AM - 6:00 PM 9:00 AM - 8:00 PM Probably meaning two shift options: either 7am-6pm or 9am-8pm, both 4x10. We'll capture that. Thus Schedule section with
describing. We must not include filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not. We must not put Job ID/requisition numbers as headings. There's "#MPipe26". We'll ignore. We must remove boilerplate: TEKsystems description, EEO statements, etc. We must not include application instructions: like "Apply today", "Application Deadline". Remove. We must preserve all substantive information. Thus final HTML fragment:
About the role
Build the Future of High-Performance Infrastructure We are seeking experienced Data Center Engineers to join a cutting-edge operations team supporting advanced computing infrastructure. This is an excellent opportunity for individuals with strong data center, hardware, Linux, and troubleshooting experience who enjoy working in fast-paced, highly technical environments. As a Data Center Engineer, you will work alongside engineering, operations, and infrastructure teams to deploy, maintain, troubleshoot, and optimize large-scale compute systems. You will play a key role in ensuring system performance, reliability, and operational excellence.
Responsibilities
- Perform rack-and-stack deployments, hardware installations, and infrastructure builds.
- Execute structured cabling and connectivity validation for data center environments.
- Troubleshoot hardware, infrastructure, Linux, and system performance issues.
- Support engineering teams with testing, validation, deployment, and operational initiatives.
- Monitor system health and assist with maintaining high availability across critical infrastructure.
- Participate in hardware break/fix, component replacement, upgrades, and recovery efforts.
- Create and maintain Standard Operating Procedures (SOPs) and operational documentation.
- Collect and analyze system metrics to identify opportunities for performance improvement.
- Drive efficiency initiatives that improve uptime, throughput, testing accuracy, and overall operational performance.
- Collaborate closely with cross-functional technical teams to support next-generation technologies and deployments.
Requirements
- Experience working in a data center, laboratory, or large-scale technical infrastructure environment.
- Hands-on experience with: rack and stack deployments, structured cabling, hardware installation and troubleshooting, data center maintenance, infrastructure support.
- Working knowledge of Linux and command-line troubleshooting.
- Experience testing, validating, and deploying hardware platforms.
- Strong problem-solving and analytical skills.
- Excellent written and verbal communication abilities.
- Ability to work effectively in a collaborative, team-oriented environment.
Qualifications
- Experience with DCIM platforms such as Nautobot or similar tools.
- Scripting or automation experience with Shell, Python, Ansible, or related technologies.
- Knowledge of networking concepts and protocols including: TCP/IP, DNS, NFS, SSL.
- Experience supporting servers, GPUs, PCBs, or high-performance computing environments.
- Previous experience in mission-critical infrastructure environments.
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
Pay
Up to $45/hour (pay range $45.00 - $45.00/hr).
Schedule
4x10 hour shifts. Available shift patterns: Sunday–Wednesday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM; Wednesday–Saturday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM.
We need to ensure we didn't include any filler like "commensurate with experience". Not present. Check for duplication: We included location? Not needed as heading but we could include location in About the role paragraph? Already we have location in description? Not explicitly. The location is given at top: "Location: Sparks, NV (Onsite)". We could include that in About the role paragraph or maybe a separate short paragraph. But we have no heading for location; we could embed it in About the role. Let's add location info there. Update About the role paragraph to include location: "Located in Sparks, NV (onsite)." Also mention schedule? Already schedule separate. Thus About the role paragraph: "Build the Future of High-Performance Infrastructure We are seeking experienced Data Center Engineers to join a cutting-edge operations team supporting advanced computing infrastructure. This is an excellent opportunity for individuals with strong data center, hardware, Linux, and troubleshooting experience who enjoy working in fast-paced, highly technical environments. As a Data Center Engineer, you will work alongside engineering, operations, and infrastructure teams to deploy, maintain, troubleshoot, and optimize large-scale compute systems. You will play a key role in ensuring system performance, reliability, and operational excellence. Located in Sparks, NV (onsite)." Now check for any leftover boilerplate: We removed TEKsystems description, EEO, etc. Also removed "Important Information" about commute and schedule? We included schedule; commute mention maybe not needed. Could add a sentence about commute in About the role or Schedule? The posting says: "Candidates must be able to reliably commute to the site and work one of the designated 4x10 schedules." That's substantive. We could add to Schedule paragraph: "Candidates must be able to reliably commute to the site and work one of the designated 4x10 schedules." Let's add. Thus Schedule paragraph: "4x10 hour shifts. Available shift patterns: Sunday–Wednesday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM; Wednesday–Saturday 7:00 AM–6:00 PM or 9:00 AM–8:00 PM. Candidates must be able to reliably commute to the site and work one of the designated 4x10 schedules." Now check for any other substantive info: "Contract position" maybe we could include in About the role or a short note. Could add to About the role: "This is a contract position." Let's add. Thus About the role paragraph: add "This is a contract position." after location maybe. Now final HTML. Check that we didn't include any heading with empty content. All sections have content. Now output only HTML
- .
- Pay: we have pay range: Up to $45/hour, also $45.00 - $45.00/hr (fixed). So we can put Pay section with
- .
- Skills: Could be derived from required/preferred but maybe we can combine? The instruction says prefer few substantive sections over many thin ones. Could we merge Requirements and Qualifications into one? But they ask to use headings for those specific names if we have content. We have both required and preferred; we could make Requirements for required, Qualifications for preferred. That's two sections.
- Skills: maybe we can extract skills like Linux, troubleshooting, etc. But we already have them in required/preferred. Could we create a Skills section? Might be thin. Better to omit Skills if not distinct.
- Benefits: we have benefits list (medical, dental, vision, etc). So
- .
- Qualifications: Could be "Preferred Qualifications". That's qualifications (preferred). So