Jobs · Information Technology · Tennessee

Service Engineer � Data Center / Server Hardware

Netpace Inc · Memphis, TN · 3 wk ago
On-siteInformation TechnologyContract
We need to output HTML fragment with sections: About the role? The posting includes "Job Summary" and "Role Responsibilities". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We need to extract content. We have: - Job Summary: "Role Responsibilities Client Corporation is seeking an experienced On-Site Service Engineer (OSE) to provide hands-on support for enterprise data center servers and hardware environments, including next-generation AI infrastructure. This is a hands-on server hardware and break/fix role. The successful candidate will have direct experience diagnosing, repairing, replacing, and maintaining enterprise server hardware in a data center, field service, or customer-facing environment. Prior AI experience is not required. Strong experience with enterprise servers and data center hardware is the priority." That's basically description. Could be "About the role" or "Job Summary". Use heading "About the role". Provide paragraph. - Responsibilities: The "What You'll Do" list. That's a list of duties. Use

Responsibilities

then
  • each bullet. - Requirements: "What You Bring Required" list. Use

    Requirements

    then list. - Preferred Qualifications: Use

    Qualifications

    maybe "Preferred Qualifications". Could also be "Qualifications". We'll use heading "Qualifications". Provide list. - Skills: Not explicitly separate; but we could combine with Requirements? The instruction: Use headings for sections like Skills if present. There's no explicit Skills section separate; but we could include "Skills" heading if we have skill list. However we have many skill-like items in Requirements and Preferred Qualifications. Might be better to not create a Skills section if not distinct. The instruction: Prefer a few substantive sections over many thin ones. So we can combine skills into Requirements/Qualifications. - Benefits, Pay, Schedule: The posting includes Work hours: 8-5 Mon-Fri, occasionally need to support different shift hours and on call. On Call: Yes Travel: No Contract to Hire: Possible Duration: 6 months with possible extensions. Also "Work hours: 8-5 Mon-Fri, occasionally need to support different shift hours and on call." That's schedule info. Also "Duration: 6 months with possible extensions" maybe not schedule but contract length. Benefits not mentioned. Pay not mentioned. So we should include Schedule section if there is real specific content. We have work hours and on-call. So we can create

    Schedule

    with paragraph describing work hours, on-call, occasional shift, etc. Also maybe include duration? Could be part of Schedule or maybe a separate "Contract" but not required. We'll put duration in Schedule paragraph. - Benefits: none, so omit. - Pay: none, omit. - Also note "Contract to Hire: Possible" could be included in Schedule or maybe a separate section but not required. We'll include in Schedule paragraph. We must not include boilerplate like "Please apply if you are comfortable doing W2 Title:" etc. That's metadata; we can fold minor metadata into a short

    or drop it. The first line: "Please apply if you are comfortable doing W2 Title: On-Site Service Engineer AI Data Center Location: Memphis Tennessee 38118 Duration: 6 months with possible extensions Work hours: 8-5 Mon-Fri, occasionally need to support different shift hours and on call. On Call: Yes Travel: No Contract to Hire: Possible Job Summary". Actually that line includes location, duration, work hours, etc. We already captured schedule info. Location we could include in a short paragraph maybe under About the role? But location is minor metadata; we can fold into a short

    maybe after About the role. However instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." Location is minor metadata; we can include a short paragraph after About the role maybe. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep location, duration, work hours, on-call, travel, contract-to-hire possible. We'll include those in Schedule section or a separate "Details" but we only have allowed headings list. Could add a paragraph after About the role that includes location and contract type. But we must not create new headings not in list. So we can just add a

    after About the role containing location and contract-to-hire possible. That's allowed as prose. Let's structure:

    About the role

    On-Site Service Engineer AI Data Center position in Memphis, Tennessee 38118. Contract to hire possible.

    Then responsibilities, requirements, qualifications, schedule. Schedule section: include work hours, on-call, occasional shift, duration 6 months with possible extensions, travel none. We need to ensure we don't repeat content. Let's extract details: Work hours: 8-5 Mon-Fri, occasionally need to support different shift hours and on call. On Call: Yes Travel: No Contract to Hire: Possible Duration: 6 months with possible extensions We'll put in Schedule:

    Standard work hours are 8 AM–5 PM Monday‑Friday, with occasional shift work and on‑call responsibilities. Travel is not required. The initial contract is 6 months, with possible extensions, and contract‑to‑hire is possible.

    Now responsibilities list: from "What You'll Do". We'll create bullet points. Requirements list: from "What You Bring Required". We'll bullet. Preferred Qualifications list: from "Preferred Qualifications". We'll bullet. Check for any duplicate content: Ensure we don't repeat same bullet across sections. Let's extract bullets: What You'll Do: - Provide on-site technical support for Dell PowerEdge and other enterprise server hardware - Diagnose and resolve server hardware failures and system issues to minimize customer downtime - Perform hands-on hardware installation, removal, replacement, and repair, including: - Memory/DIMMs - CPUs/processors - Power supplies - Fans and cooling components - Hard drives/SSDs - RAID/HBA components - NICs and other PCIe components - GPUs and accelerator hardware - Motherboards/system boards and other server components - Perform rack-and-stack, server installation, cabling, component swaps, and hardware configuration - Troubleshoot issues involving server hardware, BIOS/firmware, operating systems, and hardware diagnostics - Perform firmware and BIOS updates and utilize server management tools such as Dell iDRAC or comparable platforms - Execute both reactive break/fix and preventive maintenance following established procedures - Troubleshoot and isolate hardware failures using documented diagnostic procedures and technical resources - Work directly with customers and internal technical teams during service events to communicate status, troubleshoot issues, and drive resolution - Accurately document service activities, hardware replacements, troubleshooting steps, and resolution details - Escalate complex technical issues when appropriate - Participate in on-call rotations and provide extended coverage as required We need to flatten nested list? The instruction: Use
    • for any list of duties/requirements/benefits. So we can have top-level
        with
      • items; for sub-items we could either embed another
          inside
        • or just include them as part of the li text. Probably easiest to keep top-level bullets and include sub-items as part of the li text separated by commas or semicolons. But we could also nest. The instruction didn't forbid nesting. We'll keep simple top-level bullets; for the long list we can break into separate li for each component group. Let's create separate li for each major duty: - Provide on-site technical support for Dell PowerEdge and other enterprise server hardware - Diagnose and resolve server hardware failures and system issues to minimize customer downtime - Perform hands-on hardware installation, removal, replacement, and repair of components such as memory/DIMMs, CPUs/processors, power supplies, fans and cooling components, hard drives/SSDs, RAID/HBA components, NICs and other PCIe components, GPUs and accelerator hardware, motherboards/system boards and other server components - Perform rack-and-stack, server installation, cabling, component swaps, and hardware configuration - Troubleshoot issues involving server hardware, BIOS/firmware, operating systems, and hardware diagnostics - Perform firmware and BIOS updates and utilize server management tools such as Dell iDRAC or comparable platforms - Execute both reactive break/fix and preventive maintenance following established procedures - Troubleshoot and isolate hardware failures using documented diagnostic procedures and technical resources - Work directly with customers and internal technical teams during service events to communicate status, troubleshoot issues, and drive resolution - Accurately document service activities, hardware replacements, troubleshooting steps, and resolution details - Escalate complex technical issues when appropriate - Participate in on-call rotations and provide extended coverage as required That covers. Now Requirements list: - 3+ years of hands-on experience supporting enterprise servers, data center hardware, or similar infrastructure - Direct, hands-on experience physically working on server hardware installing, removing, diagnosing, repairing, or replacing server components - Experience troubleshooting and replacing components such as memory, CPUs, power supplies, storage, RAID/HBA, NICs, fans/cooling systems, PCIe components, or GPUs - Experience working with rack-mounted enterprise servers in a data center, field service, or customer environment - Strong understanding of server hardware architecture and troubleshooting methodology - Experience with hardware diagnostics, BIOS/firmware, and server management tools - Familiarity with Linux or similar operating systems - Strong troubleshooting and problem-solving skills with the ability to independently diagnose hardware issues - Comfortable working independently in a customer-facing environment - Ability to clearly communicate technical issues and resolutions to customers and internal teams - Ability to lift up to 50 lbs., travel to customer sites, and support flexible/on-call schedules Note: "travel to customer sites" but posting says Travel: No? Actually earlier Travel: No. But requirement says ability to travel to customer sites. Might be contradictory but we keep as given. Now Preferred Qualifications list: - Experience supporting Dell PowerEdge servers - Dell or other enterprise hardware certifications - Experience with iDRAC, iLO, or comparable server management platforms - Experience supporting GPU/AI server infrastructure - Experience with data center operations, rack/stack, structured cabling, or server deployment - Associate's or Bachelor's degree in IT, Computer Science, or a related field Now schedule section: we already have. Now About the role paragraph: we need to include the job summary content. Let's craft:

          Client Corporation is seeking an experienced On‑Site Service Engineer (OSE) to provide hands‑on support for enterprise data center servers and hardware environments, including next‑generation AI infrastructure. This is a hands‑on server hardware and break/fix role requiring direct experience diagnosing, repairing, replacing, and maintaining enterprise server hardware in a data center, field service, or customer‑facing environment. Prior AI experience is not required; strong enterprise server and data center hardware experience is the priority.

          Add location and contract-to-hire possible maybe as separate short paragraph after About the role:

          Position located in Memphis, Tennessee 38118. Contract‑to‑hire possible.

          But we already have location and contract in schedule? We'll keep schedule separate for hours etc. We'll add a short paragraph after About the role for location and contract type. Now ensure we don't repeat info: schedule paragraph includes work hours, on-call, travel none, duration 6 months possible extensions. We'll not repeat location there. Now produce HTML fragment:

          About the role

          Client Corporation is seeking an experienced On‑Site Service Engineer (OSE) to provide hands‑on support for enterprise data center servers and hardware environments, including next‑generation AI infrastructure.

Similar jobs