Sustaining Systems Engineer

We need to output HTML fragment with sections: About the role, Responsibilities (What You’ll Do), Requirements/Qualifications (What You Bring), Benefits (What We Offer). Possibly also About ZT Systems? The instruction: use

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

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

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

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We have content: About The Role (intro paragraph). What You’ll Do (list of duties). What You Bring (list of qualifications). About ZT Systems (company description). What We Offer (benefits). Also there is a line about "Compensation & Financial Security" etc. That's benefits details. So we need sections: About the role (maybe "About the role" heading). Responsibilities (What You’ll Do). Requirements (What You Bring). Benefits (What We Offer). Possibly also "About ZT Systems" could be part of About the role? But we can include a section "About the company" but not in the list of allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't include About the company. However we could incorporate that into About the role or maybe omit? The instruction: "include a section ONLY when the posting has real, specific content for it". The posting has "About ZT Systems" content. It's substantive. But the allowed headings list doesn't have a generic "About the company". Could we use "About the role" for that? No, that's about the role. Could we use "Requirements" or "Qualifications"? Not appropriate. Could we create a custom heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive. So we can use other headings if needed, but better to stick to those. However "About ZT Systems" could be considered part of "About the role"? Not really. But we could include it as a paragraph under "About the role" heading, maybe combine. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings. So we can add a heading like "About ZT Systems". That seems reasonable. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for section headings. Use

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

    for prose. We need to preserve all substantive information. Let's extract. About The Role paragraph: "The Sustaining Systems Engineer will be responsible for assessing ECO’s, change requests, debug, and coordination and creation of validation plans to support mass production server platforms. In addition, the Systems Engineer will play a critical role in documenting key learnings and proposing/designing new and complex system requirements for future programs as improved methodologies and system designs evolve on next generation server products." That's prose. What You’ll Do (list): - Determine system specifications, I/O processes, and working parameters for hardware/software compatibility. - Coordinate the validation/debug/design of subsystems and the integration of the total system. - Maintain updated overall server and system product configurations as they evolve during the sustenance phase through EoL. - Work as part of a cross-functional team to define/create validation and debug methodologies for customer change requests, alternative source part validation, 2nd source qualifications, updated FW/BMC/UEFI, etc. - Optimize system performance and resolve performance problems post launch. - Ensure and maintain the manufacturability, reliability, and serviceability of designs. What You Bring (list): - Bachelor’s degree in Electrical Engineer or Computer Science and 6+ years of server design experience (alternatively a MS and 4+ years) - Strong understanding of x-86 system architecture - Robust technical knowledge and expertise in Platform execution - Understanding of System-level server platforms and how each component interacts with the system - Board level development skills - Good understanding of hardware and system software interactions, and ability to apply this knowledge to resolve technical issues - Proactively oriented to seize opportunities and identify potential problems - Ability to use time, energy, and resources in an effective manner to achieve set goals - Ability to identify the elements of a situation/ability to visualize, articulate, and solve problems - Collaborative, flexible, and adaptable About ZT Systems paragraph(s): "At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT Systems and help us build technology infrastructure that connects the world." What We Offer (benefits) includes several sub-sections: Compensation & Financial Security, Health & Wellness, Time Away & Work-Life Balance, Growth & Purpose. Also note: "These benefits are available to eligible employees and are designed to grow with you as your career evolves. Full benefits and eligibility varies by work location. Learn more about our benefits here." We need to preserve all substantive information. So we need to list benefits as a list? The instruction: Use

    • for any list of duties/requirements/benefits. So we should convert the benefits into a list. However there are subheadings; we could keep them as headings inside the benefits section? But we only allow

      for section headings. Could we have nested headings? Probably not needed. We could just make a flat list of benefit items, preserving the details. But we need to preserve all substantive information; we can keep the subheadings as or within

      text. Better: Under

      Benefits

      , we can have a

      with each benefit area as a
      • containing the details. For example:
      • Compensation & Financial Security: Competitive base salary, Performance-based annual bonus eligibility, 401(k) retirement savings plan, Tuition reimbursement for eligible education programs
      Similarly for Health & Wellness, Time Away & Work-Life Balance, Growth & Purpose. Also include the note about eligibility varying by location as a

      after the list. We must not include boilerplate like EEO, equal-opportunity, scam-warning, etc. The posting includes a paragraph about ZT Group Int’l. being an Equal Opportunity Employer and prohibits discrimination... Also includes export control license requirement. Those are legal/EEO boilerplate; we should remove them. Also the line "Please be aware that certain positions may require the applicant to either 1) be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. 1157, or (iv) Asylee under 8 U.S.C.1158, or 2) be eligible to obtain an export control license or license exception from the Bureau of Industry and Science & U.S. Department of Commerce. All offers of employment will be conditional subject to the foregoing." That's also legal/EEO; remove. Also "Learn more about our benefits here." is a link; we can keep as text but maybe it's okay. It's not boilerplate; it's a reference. We can keep as part of

      . Now produce HTML. Structure:

      About the role

      The Sustaining Systems Engineer will be responsible for assessing ECO’s, change requests, debug, and coordination and creation of validation plans to support mass production server platforms. In addition, the Systems Engineer will play a critical role in documenting key learnings and proposing/designing new and complex system requirements for future programs as improved methodologies and system designs evolve on next generation server products.

      Responsibilities

      • Determine system specifications, I/O processes, and working parameters for hardware/software compatibility.
      • Coordinate the validation/debug/design of subsystems and the integration of the total system.
      • Maintain updated overall server and system product configurations as they evolve during the sustenance phase through EoL.
      • Work as part of a cross-functional team to define/create validation and debug methodologies for customer change requests, alternative source part validation, 2nd source qualifications, updated FW/BMC/UEFI, etc.
      • Optimize system performance and resolve performance problems post launch.
      • Ensure and maintain the manufacturability, reliability, and serviceability of designs.

      Requirements

      • Bachelor’s degree in Electrical Engineer or Computer Science and 6+ years of server design experience (alternatively a MS and 4+ years)
      • Strong understanding of x-86 system architecture
      • Robust technical knowledge and expertise in Platform execution
      • Understanding of System-level server platforms and how each component interacts with the system
      • Board level development skills
      • Good understanding of hardware and system software interactions, and ability to apply this knowledge to resolve technical issues
      • Proactively oriented to seize opportunities and identify potential problems
      • Ability to use time, energy, and resources in an effective manner to achieve set goals
      • Ability to identify the elements of a situation/ability to visualize, articulate, and solve problems
      • Collaborative, flexible, and adaptable

      About ZT Systems

      At ZT Systems, a Sanmina Company, you’ll get to do work you are proud of alongside smart, passionate people. Every day, there are opportunities to collaborate with the best in the industry to design, build, and deliver impactful solutions to world-class customers. Along the way, you will gain hands-on experience in a fast-paced environment that’s challenging, rewarding, and career-defining. A culture built around our values we work hard and think fast. We view challenges as opportunities—to do better, push harder, and be faster than we were the day before. When we fail, we learn from it and move on together. And when we succeed, we use the momentum to go even further. We create value with everything we do, building the foundation of today—and transforming the future of tomorrow. Join ZT