Senior Data Center Operations Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the "Notice to Job Seekers Regarding Impersonation and Fraudulent Job Offers" etc. Also remove "Our Commitment to Diversity & Inclusion" maybe considered EEO boilerplate; should remove. Also remove "Milestone also makes reasonable accommodations..." etc. Also remove the "Our recruitment team is looking forward to meeting you." That's maybe okay? It's not boilerplate but could be considered fluff; but we should preserve substantive information. It's not essential but maybe okay to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement is EEO boilerplate, so remove. The fraud notice is also boilerplate/scam-warning, remove. Also remove "Our Commitment to Diversity & Inclusion" and following paragraphs. Also remove "Our recruitment team is looking forward to meeting you." That's not boilerplate but maybe considered fluff; but it's not required. Safer to remove as it's not substantive.
We need to preserve all substantive information: Company Overview, Job Overview (maybe combine into About the role?), Key Responsibilities (list), Required Skills (list), Required Experience (list), Preferred Certifications (list), Physical Requirements (list), Compensation (Pay). Also maybe "Job Overview" could be considered About the role. We'll create sections: About the role (maybe combine Company Overview and Job Overview? Actually Company Overview is about the company, not role. Could be separate section "About the company"? Not in allowed headings list: they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company. But we could put Company Overview under About the role? Might be okay. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings only if content exists. We have content for About the role (job overview). We have Responsibilities (Key Responsibilities). We have Requirements (maybe Required Experience + Required Skills? Could split into Requirements and Qualifications? But we have Required Skills and Required Experience. Could combine into Requirements. Qualifications maybe for Preferred Certifications? Could treat as Qualifications. Skills we have Required Skills; but we already used Skills heading maybe for skills list. However they said prefer a few substantive sections over many thin ones. So we could have: About the role (job overview), Responsibilities (Key Responsibilities), Requirements (combine Required Skills + Required Experience), Qualifications (Preferred Certifications), Pay (Compensation), Physical Requirements (maybe could be under Requirements? But it's separate; we could include as a subsection under Requirements? But they said use headings only for those categories; Physical Requirements not listed. Could we omit? It's substantive. Could we include under Requirements? Might be okay to include as a list under Requirements. But better to create a section maybe "Physical Requirements" but not in allowed list; but they gave examples, not exhaustive? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can use other headings if needed. Safer to include Physical Requirements as its own heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Physical Requirements.
Now we need to extract content.
Company Overview: paragraph about Milestone Technologies. We'll include that in About the role? Actually About the role should describe the role, not company. But we could include company overview as part of About the role? Might be weird. Better to have About the role contain Job Overview description. And maybe we can have a separate section "About the company" but not in list; but we can still use heading. However they said prefer few sections; adding another section may be okay. But we can incorporate company overview into About the role as a brief intro? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't forbid adding other headings. So we can add About the company if we want. But to keep few sections, maybe we merge company overview into About the role as a preamble? Might be acceptable.
Let's craft About the role: combine company overview and job overview? Might be too long but okay.
Better: About the role: Job Overview paragraph (the description of role). Then we can have a separate section "About the company" but not needed. I'll include company overview as a paragraph under About the role? Might be confusing.
Given the instruction to preserve ALL substantive information, we need to keep company overview somewhere. If we omit it, we lose info. So we need a section for it. Could use "About the company" heading. Not in examples but allowed. Let's do that.
Thus sections: About the company, About the role, Responsibilities, Requirements, Qualifications, Pay, Physical Requirements.
Now extract each.
About the company: The paragraph(s) under "Company Overview Milestone Technologies is a global IT managed services firm..." up to "...revolutionizing the way IT is deployed." That's the company overview.
About the role: The "Job Overview Senior Data Center Operations Engineer Job Overview" repeated? Actually there is "Job Overview Senior Data Center Operations Engineer Job Overview". Then description: "The Senior Data Center Operations Engineer plays a critical, hands-on role..." up to "...This role offers continuity across both deployment and operational phases and provides exposure to large-scale, modern infrastructure environments, with a clear path for progression into advanced technical or engineering roles." We'll capture that.
Responsibilities: The bullet list under "Key ResponsibilitiesAdvanced Hardware Troubleshooting & Repair ..." etc. It's a list with headings inside? Actually they have headings like "Advanced Hardware Troubleshooting & Repair", then bullet points. We need to output - for any list of duties/requirements/benefits. So we should flatten? Probably each bullet point as
- . The headings could be omitted or turned into
- with bold? But we must preserve all substantive information; we could keep the heading as part of the
- text. Eg: "
- Advanced Hardware Troubleshooting & Repair: Diagnose and resolve ..." but we cannot add unless it's in original? Not necessary. We'll just list each bullet as
- with the text.
Let's extract bullet points:
Under Advanced Hardware Troubleshooting & Repair:
- Diagnose and resolve complex hardware failures across server platforms (motherboards, CPUs, memory, storage)
- Perform component-level repairs and replacements on servers and data center hardware
- Execute break/fix processes with a focus on minimizing downtime and meeting SLAs
- Conduct root cause analysis (RCA) of hardware failures and implement preventative improvements
- Identify recurring failure trends and contribute to tooling, automation, and process enhancements
Linux Systems & Platform Support:
- Utilize Linux command-line tools for system monitoring, diagnostics, and troubleshooting
- Support provisioning and deployment of servers across Linux distributions (RHEL, Ubuntu, etc.)
- Troubleshoot boot-level and OS-level issues in production environments
- Collaborate with engineering teams to resolve complex hardware/software interaction issues
Data Center Operations:
- Support hardware installation, structured cabling, and infrastructure validation
- Maintain accurate inventory of spare parts, assets, and retired equipment
- Document repairs, changes, and configurations in ITSM/DCIM systems
- Ensure adherence to safety, security, and operational protocols
- Serve as a primary escalation point for complex infrastructure issues
- Participate in on-call rotation supporting 24x7 operations
Collaboration & Mentorship:
- Provide guidance and mentorship to technicians on hardware troubleshooting and best practices
- Collaborate with network, storage, and infrastructure teams to resolve cross-functional issues
- Contribute to knowledge sharing, documentation, and operational excellence initiatives
- Support continuous improvement efforts across processes, tooling, and operational workflows
Now Required Skills: list:
- Strong English communication skills (written and verbal) are required for coordination with cross-functional teams
- Expert-level knowledge of server hardware architecture and component-level troubleshooting
- Strong proficiency with Linux systems and command-line diagnostics
- Solid understanding of networking fundamentals and infrastructure components
- Experience working within structured operational environments (SOPs, SLAs, ticketing systems)
- Familiarity with ITSM/DCIM tools (ServiceNow, Jira, or similar)
- Experience with structured cabling and fiber optic connectivity
- Strong analytical and problem-solving skills with attention to detail
- Ability to operate effectively in high-pressure, high-availability environments
- Strong organizational and documentation skills
Required Experience:
- 5+ years of experience in data center operations or similar infrastructure environments
- Significant hands-on experience with server hardware troubleshooting and repair
- Minimum of 2 years of experience working with Linux operating systems in production environments
- Experience supporting enterprise server platforms and infrastructure environments
- Demonstrated experience performing root cause analysis and resolving complex hardware issues
- Experience working within ticketing systems and operational workflows
- Exposure to data center build-outs, deployments, or infrastructure upgrades (preferred)
Preferred Certifications:
- CompTIA A+, Server+, or Linux+LPI certification or equivalent
- Vendor-specific hardware certifications
Physical Requirements:
- Ability to lift and move equipment up to 50 lbs
- Ability to work in a temperature-controlled environment with moderate noise levels
- Ability to perform physical tasks such as standing, walking, bending, and kneeling for extended periods
Compensation:
- Estimated Pay Range: $46.17 - $68.00 USD
- Exact compensation and offers of employment are dependent on circumstances of each case and will be determined based on job-related knowledge, skills, experience, licenses or certifications, and location.
We should not include the sentence "Exact compensation..." if it's just boilerplate? It's substantive. Keep.
Now we need to output HTML fragment with
headings and
for prose,
- for lists.
We need to decide which content is prose vs list.
About the company: prose paragraph(s). We'll put in
.
About the role: prose paragraph(s). We'll put in
.
Responsibilities: list =>
- each bullet.
Requirements: we could combine Required Skills and Required Experience into one list? But they are different categories. Could split into two sublists under Requirements heading? But we need to preserve structure. Could make
with all items; but might lose distinction. Better to have two subheadings? Not allowed? Could use inside? Not specified. Simpler: make one list under Requirements containing both skills and experience items. That's okay.
Qualifications: list of Preferred Certifications.
Pay: could be prose (
) containing the two sentences.
Physical Requirements: list.
Now ensure we don't include any boilerplate like "Our Commitment to Diversity & Inclusion", fraud notice, etc.
Now produce HTML.
Let's craft.
About the company paragraph: combine the company overview text.
We need to ensure we don't include duplicated lines. The company overview appears once.
Let's copy:
"Milestone Technologies is a global IT managed services firm that partners with organizations to scale their technology, infrastructure and services to drive specific business outcomes such as digital transformation, innovation, and operational agility. Milestone
for prose. We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the "Notice to Job Seekers Regarding Impersonation and Fraudulent Job Offers" etc. Also remove "Our Commitment to Diversity & Inclusion" maybe considered EEO boilerplate; should remove. Also remove "Milestone also makes reasonable accommodations..." etc. Also remove the "Our recruitment team is looking forward to meeting you." That's maybe okay? It's not boilerplate but could be considered fluff; but we should preserve substantive information. It's not essential but maybe okay to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement is EEO boilerplate, so remove. The fraud notice is also boilerplate/scam-warning, remove. Also remove "Our Commitment to Diversity & Inclusion" and following paragraphs. Also remove "Our recruitment team is looking forward to meeting you." That's not boilerplate but maybe considered fluff; but it's not required. Safer to remove as it's not substantive. We need to preserve all substantive information: Company Overview, Job Overview (maybe combine into About the role?), Key Responsibilities (list), Required Skills (list), Required Experience (list), Preferred Certifications (list), Physical Requirements (list), Compensation (Pay). Also maybe "Job Overview" could be considered About the role. We'll create sections: About the role (maybe combine Company Overview and Job Overview? Actually Company Overview is about the company, not role. Could be separate section "About the company"? Not in allowed headings list: they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the company. But we could put Company Overview under About the role? Might be okay. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings only if content exists. We have content for About the role (job overview). We have Responsibilities (Key Responsibilities). We have Requirements (maybe Required Experience + Required Skills? Could split into Requirements and Qualifications? But we have Required Skills and Required Experience. Could combine into Requirements. Qualifications maybe for Preferred Certifications? Could treat as Qualifications. Skills we have Required Skills; but we already used Skills heading maybe for skills list. However they said prefer a few substantive sections over many thin ones. So we could have: About the role (job overview), Responsibilities (Key Responsibilities), Requirements (combine Required Skills + Required Experience), Qualifications (Preferred Certifications), Pay (Compensation), Physical Requirements (maybe could be under Requirements? But it's separate; we could include as a subsection under Requirements? But they said use headings only for those categories; Physical Requirements not listed. Could we omit? It's substantive. Could we include under Requirements? Might be okay to include as a list under Requirements. But better to create a section maybe "Physical Requirements" but not in allowed list; but they gave examples, not exhaustive? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can use other headings if needed. Safer to include Physical Requirements as its own heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Physical Requirements.
Now we need to extract content.
Company Overview: paragraph about Milestone Technologies. We'll include that in About the role? Actually About the role should describe the role, not company. But we could include company overview as part of About the role? Might be weird. Better to have About the role contain Job Overview description. And maybe we can have a separate section "About the company" but not in list; but we can still use heading. However they said prefer few sections; adding another section may be okay. But we can incorporate company overview into About the role as a brief intro? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't forbid adding other headings. So we can add About the company if we want. But to keep few sections, maybe we merge company overview into About the role as a preamble? Might be acceptable.
Let's craft About the role: combine company overview and job overview? Might be too long but okay.
Better: About the role: Job Overview paragraph (the description of role). Then we can have a separate section "About the company" but not needed. I'll include company overview as a paragraph under About the role? Might be confusing.
Given the instruction to preserve ALL substantive information, we need to keep company overview somewhere. If we omit it, we lose info. So we need a section for it. Could use "About the company" heading. Not in examples but allowed. Let's do that.
Thus sections: About the company, About the role, Responsibilities, Requirements, Qualifications, Pay, Physical Requirements.
Now extract each.
About the company: The paragraph(s) under "Company Overview Milestone Technologies is a global IT managed services firm..." up to "...revolutionizing the way IT is deployed." That's the company overview.
About the role: The "Job Overview Senior Data Center Operations Engineer Job Overview" repeated? Actually there is "Job Overview Senior Data Center Operations Engineer Job Overview". Then description: "The Senior Data Center Operations Engineer plays a critical, hands-on role..." up to "...This role offers continuity across both deployment and operational phases and provides exposure to large-scale, modern infrastructure environments, with a clear path for progression into advanced technical or engineering roles." We'll capture that.
Responsibilities: The bullet list under "Key ResponsibilitiesAdvanced Hardware Troubleshooting & Repair ..." etc. It's a list with headings inside? Actually they have headings like "Advanced Hardware Troubleshooting & Repair", then bullet points. We need to output - for any list of duties/requirements/benefits. So we should flatten? Probably each bullet point as
- . The headings could be omitted or turned into
- with bold? But we must preserve all substantive information; we could keep the heading as part of the
- text. Eg: "
- Advanced Hardware Troubleshooting & Repair: Diagnose and resolve ..." but we cannot add unless it's in original? Not necessary. We'll just list each bullet as
- with the text.
Let's extract bullet points:
Under Advanced Hardware Troubleshooting & Repair:
- Diagnose and resolve complex hardware failures across server platforms (motherboards, CPUs, memory, storage)
- Perform component-level repairs and replacements on servers and data center hardware
- Execute break/fix processes with a focus on minimizing downtime and meeting SLAs
- Conduct root cause analysis (RCA) of hardware failures and implement preventative improvements
- Identify recurring failure trends and contribute to tooling, automation, and process enhancements
Linux Systems & Platform Support:
- Utilize Linux command-line tools for system monitoring, diagnostics, and troubleshooting
- Support provisioning and deployment of servers across Linux distributions (RHEL, Ubuntu, etc.)
- Troubleshoot boot-level and OS-level issues in production environments
- Collaborate with engineering teams to resolve complex hardware/software interaction issues
Data Center Operations:
- Support hardware installation, structured cabling, and infrastructure validation
- Maintain accurate inventory of spare parts, assets, and retired equipment
- Document repairs, changes, and configurations in ITSM/DCIM systems
- Ensure adherence to safety, security, and operational protocols
- Serve as a primary escalation point for complex infrastructure issues
- Participate in on-call rotation supporting 24x7 operations
Collaboration & Mentorship:
- Provide guidance and mentorship to technicians on hardware troubleshooting and best practices
- Collaborate with network, storage, and infrastructure teams to resolve cross-functional issues
- Contribute to knowledge sharing, documentation, and operational excellence initiatives
- Support continuous improvement efforts across processes, tooling, and operational workflows
Now Required Skills: list:
- Strong English communication skills (written and verbal) are required for coordination with cross-functional teams
- Expert-level knowledge of server hardware architecture and component-level troubleshooting
- Strong proficiency with Linux systems and command-line diagnostics
- Solid understanding of networking fundamentals and infrastructure components
- Experience working within structured operational environments (SOPs, SLAs, ticketing systems)
- Familiarity with ITSM/DCIM tools (ServiceNow, Jira, or similar)
- Experience with structured cabling and fiber optic connectivity
- Strong analytical and problem-solving skills with attention to detail
- Ability to operate effectively in high-pressure, high-availability environments
- Strong organizational and documentation skills
Required Experience:
- 5+ years of experience in data center operations or similar infrastructure environments
- Significant hands-on experience with server hardware troubleshooting and repair
- Minimum of 2 years of experience working with Linux operating systems in production environments
- Experience supporting enterprise server platforms and infrastructure environments
- Demonstrated experience performing root cause analysis and resolving complex hardware issues
- Experience working within ticketing systems and operational workflows
- Exposure to data center build-outs, deployments, or infrastructure upgrades (preferred)
Preferred Certifications:
- CompTIA A+, Server+, or Linux+LPI certification or equivalent
- Vendor-specific hardware certifications
Physical Requirements:
- Ability to lift and move equipment up to 50 lbs
- Ability to work in a temperature-controlled environment with moderate noise levels
- Ability to perform physical tasks such as standing, walking, bending, and kneeling for extended periods
Compensation:
- Estimated Pay Range: $46.17 - $68.00 USD
- Exact compensation and offers of employment are dependent on circumstances of each case and will be determined based on job-related knowledge, skills, experience, licenses or certifications, and location.
We should not include the sentence "Exact compensation..." if it's just boilerplate? It's substantive. Keep.
Now we need to output HTML fragment with
headings and
for prose,
- for lists.
We need to decide which content is prose vs list.
About the company: prose paragraph(s). We'll put in
.
About the role: prose paragraph(s). We'll put in
.
Responsibilities: list =>
- each bullet.
Requirements: we could combine Required Skills and Required Experience into one list? But they are different categories. Could split into two sublists under Requirements heading? But we need to preserve structure. Could make
with all items; but might lose distinction. Better to have two subheadings? Not allowed? Could use inside? Not specified. Simpler: make one list under Requirements containing both skills and experience items. That's okay.
Qualifications: list of Preferred Certifications.
Pay: could be prose (
) containing the two sentences.
Physical Requirements: list.
Now ensure we don't include any boilerplate like "Our Commitment to Diversity & Inclusion", fraud notice, etc.
Now produce HTML.
Let's craft.
About the company paragraph: combine the company overview text.
We need to ensure we don't include duplicated lines. The company overview appears once.
Let's copy:
"Milestone Technologies is a global IT managed services firm that partners with organizations to scale their technology, infrastructure and services to drive specific business outcomes such as digital transformation, innovation, and operational agility. Milestone
- for any list of duties/requirements/benefits. So we should flatten? Probably each bullet point as
- . The headings could be omitted or turned into
- with bold? But we must preserve all substantive information; we could keep the heading as part of the
- text. Eg: "
- Advanced Hardware Troubleshooting & Repair: Diagnose and resolve ..." but we cannot add unless it's in original? Not necessary. We'll just list each bullet as
- with the text. Let's extract bullet points: Under Advanced Hardware Troubleshooting & Repair: - Diagnose and resolve complex hardware failures across server platforms (motherboards, CPUs, memory, storage) - Perform component-level repairs and replacements on servers and data center hardware - Execute break/fix processes with a focus on minimizing downtime and meeting SLAs - Conduct root cause analysis (RCA) of hardware failures and implement preventative improvements - Identify recurring failure trends and contribute to tooling, automation, and process enhancements Linux Systems & Platform Support: - Utilize Linux command-line tools for system monitoring, diagnostics, and troubleshooting - Support provisioning and deployment of servers across Linux distributions (RHEL, Ubuntu, etc.) - Troubleshoot boot-level and OS-level issues in production environments - Collaborate with engineering teams to resolve complex hardware/software interaction issues Data Center Operations: - Support hardware installation, structured cabling, and infrastructure validation - Maintain accurate inventory of spare parts, assets, and retired equipment - Document repairs, changes, and configurations in ITSM/DCIM systems - Ensure adherence to safety, security, and operational protocols - Serve as a primary escalation point for complex infrastructure issues - Participate in on-call rotation supporting 24x7 operations Collaboration & Mentorship: - Provide guidance and mentorship to technicians on hardware troubleshooting and best practices - Collaborate with network, storage, and infrastructure teams to resolve cross-functional issues - Contribute to knowledge sharing, documentation, and operational excellence initiatives - Support continuous improvement efforts across processes, tooling, and operational workflows Now Required Skills: list: - Strong English communication skills (written and verbal) are required for coordination with cross-functional teams - Expert-level knowledge of server hardware architecture and component-level troubleshooting - Strong proficiency with Linux systems and command-line diagnostics - Solid understanding of networking fundamentals and infrastructure components - Experience working within structured operational environments (SOPs, SLAs, ticketing systems) - Familiarity with ITSM/DCIM tools (ServiceNow, Jira, or similar) - Experience with structured cabling and fiber optic connectivity - Strong analytical and problem-solving skills with attention to detail - Ability to operate effectively in high-pressure, high-availability environments - Strong organizational and documentation skills Required Experience: - 5+ years of experience in data center operations or similar infrastructure environments - Significant hands-on experience with server hardware troubleshooting and repair - Minimum of 2 years of experience working with Linux operating systems in production environments - Experience supporting enterprise server platforms and infrastructure environments - Demonstrated experience performing root cause analysis and resolving complex hardware issues - Experience working within ticketing systems and operational workflows - Exposure to data center build-outs, deployments, or infrastructure upgrades (preferred) Preferred Certifications: - CompTIA A+, Server+, or Linux+LPI certification or equivalent - Vendor-specific hardware certifications Physical Requirements: - Ability to lift and move equipment up to 50 lbs - Ability to work in a temperature-controlled environment with moderate noise levels - Ability to perform physical tasks such as standing, walking, bending, and kneeling for extended periods Compensation: - Estimated Pay Range: $46.17 - $68.00 USD - Exact compensation and offers of employment are dependent on circumstances of each case and will be determined based on job-related knowledge, skills, experience, licenses or certifications, and location. We should not include the sentence "Exact compensation..." if it's just boilerplate? It's substantive. Keep. Now we need to output HTML fragment with
headings and
for prose,
- for lists.
We need to decide which content is prose vs list.
About the company: prose paragraph(s). We'll put in
. About the role: prose paragraph(s). We'll put in
. Responsibilities: list =>
- each bullet.
Requirements: we could combine Required Skills and Required Experience into one list? But they are different categories. Could split into two sublists under Requirements heading? But we need to preserve structure. Could make
- with all items; but might lose distinction. Better to have two subheadings? Not allowed? Could use
inside? Not specified. Simpler: make one list under Requirements containing both skills and experience items. That's okay. Qualifications: list of Preferred Certifications. Pay: could be prose (
) containing the two sentences. Physical Requirements: list. Now ensure we don't include any boilerplate like "Our Commitment to Diversity & Inclusion", fraud notice, etc. Now produce HTML. Let's craft. About the company paragraph: combine the company overview text. We need to ensure we don't include duplicated lines. The company overview appears once. Let's copy: "Milestone Technologies is a global IT managed services firm that partners with organizations to scale their technology, infrastructure and services to drive specific business outcomes such as digital transformation, innovation, and operational agility. Milestone
- each bullet.
Requirements: we could combine Required Skills and Required Experience into one list? But they are different categories. Could split into two sublists under Requirements heading? But we need to preserve structure. Could make
- with the text. Let's extract bullet points: Under Advanced Hardware Troubleshooting & Repair: - Diagnose and resolve complex hardware failures across server platforms (motherboards, CPUs, memory, storage) - Perform component-level repairs and replacements on servers and data center hardware - Execute break/fix processes with a focus on minimizing downtime and meeting SLAs - Conduct root cause analysis (RCA) of hardware failures and implement preventative improvements - Identify recurring failure trends and contribute to tooling, automation, and process enhancements Linux Systems & Platform Support: - Utilize Linux command-line tools for system monitoring, diagnostics, and troubleshooting - Support provisioning and deployment of servers across Linux distributions (RHEL, Ubuntu, etc.) - Troubleshoot boot-level and OS-level issues in production environments - Collaborate with engineering teams to resolve complex hardware/software interaction issues Data Center Operations: - Support hardware installation, structured cabling, and infrastructure validation - Maintain accurate inventory of spare parts, assets, and retired equipment - Document repairs, changes, and configurations in ITSM/DCIM systems - Ensure adherence to safety, security, and operational protocols - Serve as a primary escalation point for complex infrastructure issues - Participate in on-call rotation supporting 24x7 operations Collaboration & Mentorship: - Provide guidance and mentorship to technicians on hardware troubleshooting and best practices - Collaborate with network, storage, and infrastructure teams to resolve cross-functional issues - Contribute to knowledge sharing, documentation, and operational excellence initiatives - Support continuous improvement efforts across processes, tooling, and operational workflows Now Required Skills: list: - Strong English communication skills (written and verbal) are required for coordination with cross-functional teams - Expert-level knowledge of server hardware architecture and component-level troubleshooting - Strong proficiency with Linux systems and command-line diagnostics - Solid understanding of networking fundamentals and infrastructure components - Experience working within structured operational environments (SOPs, SLAs, ticketing systems) - Familiarity with ITSM/DCIM tools (ServiceNow, Jira, or similar) - Experience with structured cabling and fiber optic connectivity - Strong analytical and problem-solving skills with attention to detail - Ability to operate effectively in high-pressure, high-availability environments - Strong organizational and documentation skills Required Experience: - 5+ years of experience in data center operations or similar infrastructure environments - Significant hands-on experience with server hardware troubleshooting and repair - Minimum of 2 years of experience working with Linux operating systems in production environments - Experience supporting enterprise server platforms and infrastructure environments - Demonstrated experience performing root cause analysis and resolving complex hardware issues - Experience working within ticketing systems and operational workflows - Exposure to data center build-outs, deployments, or infrastructure upgrades (preferred) Preferred Certifications: - CompTIA A+, Server+, or Linux+LPI certification or equivalent - Vendor-specific hardware certifications Physical Requirements: - Ability to lift and move equipment up to 50 lbs - Ability to work in a temperature-controlled environment with moderate noise levels - Ability to perform physical tasks such as standing, walking, bending, and kneeling for extended periods Compensation: - Estimated Pay Range: $46.17 - $68.00 USD - Exact compensation and offers of employment are dependent on circumstances of each case and will be determined based on job-related knowledge, skills, experience, licenses or certifications, and location. We should not include the sentence "Exact compensation..." if it's just boilerplate? It's substantive. Keep. Now we need to output HTML fragment with