Principal Technical Program Manager - Hyperscale and AI Rack Systems

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections where there is real content. No job title heading. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. We need to preserve all substantive information. We need to parse the job posting. Original text includes: - "About The Role" paragraph: "In this position, the Sr. Principal Technical Program Manager (TPM) will be responsible for leading the management and execution of server platform programs, driving design and development activities from product definition and planning through production, release, and end of life." - Then "What You’ll Do" bullet list (actually sentences). We'll treat as Responsibilities. - Then "What You’ll Bring" list of qualifications/skills. - Then compensation paragraph: "ZT Systems, a Sanmina Company, assesses market data to ensure a competitive compensation package is created for all our employees. The typical base salary for this position is expected to be between $148,125 and $210,000 annually. If hired, the final base salary will be determined on an individual basis taking into consideration experience, skills, knowledge, education and/or certifications. Base salary is just one component of ZT Systems total rewards philosophy. We take pride in offering a wide range of benefits and perks that appeal to the variety of needs across our diverse employee base. Other rewards may include bonus, paid time off, 401(k) retirement savings plan, tuition reimbursement, wellbeing resources, and more." - Then "We are dedicated to building a diverse, inclusive, and authentic workplace..." (EEO) - remove. - Then "You may be just the right candidate..." (encouragement) maybe keep? It's not boilerplate? Might be considered fluff but it's substantive? Might be considered generic encouragement; but we can keep as part of About the role? Probably not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The encouragement line is not boilerplate but could be considered fluff. However it's not a list; it's a sentence encouraging to apply. Might be considered application instruction? Not exactly. Safer to keep? The instruction says remove application instructions. This is not an instruction to apply but encouragement. Might be okay to keep but could be considered fluff. I'd lean to keep as part of About the role? But we already have About the role section. Could add a paragraph after About the role. - Then ":SL :Onsite" weird; maybe location? It appears as ":SL :Onsite". Probably indicates location: Onsite. Could be schedule? Not sure. Might be location tag. We could treat as location but not required. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. This ":SL :Onsite" could be minor metadata; we could drop or put in a p. I'd drop as it's unclear. - Then "About ZT Systems" paragraph describing company. Could be considered About the role? Might be considered company overview; could be part of About the role or separate section? The instruction: use headings for sections like About the role, Responsibilities, etc. There's no explicit "About the company" heading. Could fold into About the role? Might be considered filler but it's substantive about company. Could include as a paragraph under About the role? Might be okay. - Then "What We Offer" section with benefits details. That's Benefits. - Then "Full benefits and eligibility varies by work location." etc. That's benefits. - Then EEO again - remove. - Then export control license paragraph - legal; remove. Thus we need sections: - About the role: combine the initial About The Role paragraph plus maybe company overview? Could also include the encouragement line? I'd keep the initial About The Role paragraph as About the role. Optionally add company overview as part of About the role? Might be okay. - Responsibilities: from "What You’ll Do" list. - Requirements: maybe combine "What You’ll Bring" includes education/experience etc. Could split into Requirements and Qualifications and Skills. But we need to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements". Or we could have Requirements (education/experience) and Skills (skills). But that may be thin. Better to have one section "Requirements" covering all. - Benefits: from "What We Offer" plus earlier benefits mention. - Pay: from compensation paragraph (salary range). Also mention bonus etc? Could include bonus in Pay or Benefits. The instruction: create Pay/Schedule/Benefits sections only if posting actually states them. Pay is stated (salary range). So we create Pay section. - Schedule: not mentioned (no schedule info). So omit. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tasks, specific skills, etc. Let's extract details. About the role paragraph: "In this position, the Sr. Principal Technical Program Manager (TPM) will be responsible for leading the management and execution of server platform programs, driving design and development activities from product definition and planning through production, release, and end of life." We could also add the company overview paragraph from "About ZT Systems". Let's include that as part of About the role? It's substantive about company. Might be okay. Company overview paragraph: "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." That's a lot; we should keep it. Then maybe also include the encouragement line: "We are dedicated to building a diverse, inclusive, and authentic workplace, so if you’re excited about this opportunity but your experience doesn’t align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles." This is not boilerplate; it's encouraging application. Could keep as part of About the role? Might be considered fluff but it's substantive about company's stance. I'd keep it. Now Responsibilities: list from "What You’ll Do". Let's extract each sentence as a bullet. - Work closely with Marketing and Architecture teams to translate product specifications into program deliverables. - Lead cross-functional teams to develop and introduce products on schedule while meeting sales volume targets and financial objectives. - Lead requirement definition, planning, development, and launch. - Manage feature enhancements, quality, and continuity of supply. - Interact with sales organizations to communicate organizational information, strategies, and capabilities. - Manage the execution of engineering solutions, including: Printed Circuit Boards, Mechanical, Power, OS, FW, BIOS, Solution SW, Test, Diagnostics, and vendor management. - Ensure the manufacturability, reliability, and serviceability of designs. - Develop and maintain relationships with customers and providing insight and recommendation to support. - Lead weekly program core team meetings with cross-functional teams to communicate updates, track progress, and ensure the program is on track to meet upcoming milestones. - Identify and communicate program risks to stakeholders, define risk mitigation strategies, and facilitate appropriate hardware and software engineering solutions. - Maintain documentation and disseminate project information to stakeholders, customers, and partners. - Publish appropriate metrics such as KPIs (Key Performance Indicators), as required by the program or the Office of Technical Program Management. Note: Some sentences have minor grammar issues; we keep as is. Now Requirements: from "What You’ll Bring". Let's extract each bullet. - BS in Electrical Engineering or equivalent experience and 15+ years of relevant experience in server or related industry. (alternatively a MS and 13+ years) - MBA strongly desired - Good understanding of x86 server system architecture. - Understanding of system-level server platforms, software, and component interactions. - Excellent understanding of business goals and customer use cases. - Strong cross-functional team management and adaptive communication style. - Strong project management skills in scheduling and milestone tracking. - Ability to view situations objectively from different perspectives. - Ability to frame situations and make/drive decisions. - Ability to resolve complex problems, drive results, innovate, and lead strategically. - Ability to manage multiple priorities and deliver on time. - Ability to handle stressful situations professionally. - Ability to thrive in a high-growth, fast-paced environment. - Solid business, analytical, and critical thinking skills. - Pragmatic, hands-on style with creative problem-solving. - Strong planning and priority-setting abilities. - Excellent communication, negotiation, and influencing skills. - Proven ability to build positive relationships with internal and external stakeholders. We could also include the earlier line about compensation? No that's Pay. Now Benefits: from "What We Offer" plus earlier benefits mention. We need to list benefits as bullet list. From earlier compensation paragraph: "Other rewards may include bonus, paid time off, 401(k) retirement savings plan, tuition reimbursement, wellbeing resources, and more." From "What We Offer" section: - Compensation & Financial Security - Competitive base salary - Performance-based annual bonus eligibility - 401(k) retirement savings plan - Tuition reimbursement for eligible education programs - Health & Wellness - Comprehensive medical, dental, and vision coverage with access to leading providers - Mental health resources and employee wellness support programs - Company-paid life and disability insurance - Time Away & Work-Life Balance - Paid time off (PTO) and company-paid holidays - Parental leave and family care support programs - Growth & Purpose - Structured training programs and on-the-job learning opportunities - Matching gifts and volunteer programs to support causes you care about 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." We should preserve that sentence as prose. Thus Benefits section: we can have a

  intro sentence then

  • for each benefit item. Could also keep subheadings? But we only allowed

    for section headings; subheadings not allowed. So we should just list all benefits as bullet list, maybe grouping not needed. But we need to preserve all substantive information; we can keep the category headings as plain text inside

    or as

    ? The instruction: Use

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

      for prose. So we can have a

      for intro, then

      • for each benefit. The category headings could be part of the
      • text (e.g., "Compensation & Financial Security: Competitive base salary"). That preserves info. Let's craft benefit items: - Competitive base salary - Performance-based annual bonus eligibility - 401(k) retirement savings plan - Tuition reimbursement for eligible education programs - Comprehensive medical, dental, and vision coverage with access to leading providers -