Manufacturing Operations Program Manager
for each section heading. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role: description of role, what you'll do, etc. The posting has "What You’ll Do", "About The Role", "In This Role, You Will". So we can combine into About the role section.
- Responsibilities: list of duties: "Manufacturing Program Management", "Supply Chain Strategy", "Cross-Functional Communication and Alignment". Those are responsibilities.
- Requirements: maybe "Who You Are" bullet list of required experience.
- Qualifications: maybe "Preferred" section.
- Skills: maybe not explicit; could be derived from required/preferred but we should not invent. If no explicit Skills section, we should not create.
- Benefits: there is a list of benefits under "What We Offer". So include Benefits section.
- Pay: there is base salary range $207,000 to $275,000. Also mention discretionary bonus, equity awards. So Pay section.
- Schedule: not mentioned. So omit.
We must not include placeholder like "commensurate with experience". Not present.
We need to 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 include details like specifics of responsibilities, requirements, qualifications, benefits, pay.
We must not include boilerplate like EEO, export control, etc. Remove those.
We must not include duplicated lines.
We must not include navigation/cookie etc.
We must not include application instructions.
We must not include "Learn more at www.coreweave.com." maybe that's boilerplate? It's not essential but it's a link; maybe we can keep? It's not a duty. It's just a link. Probably can drop as it's not substantive about role. Safer to drop.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
... prose summarizing what you'll do? But we must preserve all substantive info; we cannot summarize away detail. However we can keep the prose as is, maybe using paragraphs from the posting. The posting includes "What You’ll Do The Hardware Quality & Operations organization ..." then "About The Role CoreWeave is seeking ..." then "In This Role, You Will Manufacturing Program Management ..." That's a mix. We could keep the paragraphs as they are, but we need to separate sections.
Better: For About the role, we can include the descriptive paragraphs before the bullet lists. For Responsibilities, we can list the three bullet areas with subdetails.
But we must not lose details. Let's extract.
Original text:
"What You’ll Do The Hardware Quality & Operations organization at CoreWeave is responsible for delivering reliable, high-performance hardware infrastructure at scale. The team partners across engineering, product lifecycle management, supply chain, manufacturing, and quality to ensure new products and sustaining production lines are ready to build, test, and operate successfully."
Then "About The Role CoreWeave is seeking an experienced Staff Manufacturing Operations Program Manager to join the Hardware Quality & Operations organization. This role will focus on manufacturing execution and transformation across new product introduction (NPI) and sustaining operations. You will lead cross-organizational build and test readiness alignment across NPI phases, drive sustaining program management, identify and mitigate risk, facilitate quality excursion oversight, and serve as a central point of alignment across engineering, PLM, supply chain, manufacturing, and quality stakeholders. This is a highly cross-functional, execution-focused role for someone who is comfortable bringing structure to ambiguity, translating technical risk into business impact, and holding technical teams accountable to program milestones across new product ramps and mature production lines."
Then "In This Role, You Will Manufacturing Program Management Define and own the NPI manufacturing program plan across EVT, DVT, PVT, and MP phases, including schedule, build and test readiness, exit criteria, and go/no-go gate reviews.Own the transition from NPI to sustaining, ensuring process documentation, quality plans, spares strategy, and open action items are handed off cleanly to steady-state production.Stand up and maintain risk registers covering technical, supply chain, quality, and schedule risks across contract manufacturers, suppliers, and data centers.Own readiness reviews for changes introduced into active production lines, ensuring changes are validated and risk-assessed before rollout. Supply Chain Strategy Manage manufacturing strategies encompassing contract manufacturer expansion, data enablement, and cross-contract-manufacturer standardization.Lead the evolution of the Hardware Quality metrics framework. Cross-Functional Communication and Alignment Act as a primary point of alignment across engineering, manufacturing, supply chain, quality, and program and product management for assigned NPI and sustaining programs.Prepare and deliver executive-level program updates, including status, risks, and decisions needed, to leadership and cross-functional stakeholders.Build consensus across teams with competing priorities and drive decisions to closure when programs are at risk, whether during a new product ramp or a live production issue."
Thus responsibilities can be captured as bullet list under each heading? But we need to use
- for any list of duties/requirements/benefits. So we can make a
with each responsibility as - . However each responsibility contains multiple sentences; we can keep them as is inside
- .
Thus:
Responsibilities
- Manufacturing Program Management: Define and own the NPI manufacturing program plan across EVT, DVT, PVT, and MP phases, including schedule, build and test readiness, exit criteria, and go/no-go gate reviews. Own the transition from NPI to sustaining, ensuring process documentation, quality plans, spares strategy, and open action items are handed off cleanly to steady-state production. Stand up and maintain risk registers covering technical, supply chain, quality, and schedule risks across contract manufacturers, suppliers, and data centers. Own readiness reviews for changes introduced into active production lines, ensuring changes are validated and risk-assessed before rollout.
- Supply Chain Strategy: Manage manufacturing strategies encompassing contract manufacturer expansion, data enablement, and cross-contract-manufacturer standardization. Lead the evolution of the Hardware Quality metrics framework.
- Cross-Functional Communication and Alignment: Act as a primary point of alignment across engineering, manufacturing, supply chain, quality, and program and product management for assigned NPI and sustaining programs. Prepare and deliver executive-level program updates, including status, risks, and decisions needed, to leadership and cross-functional stakeholders. Build consensus across teams with competing priorities and drive decisions to closure when programs are at risk, whether during a new product ramp or a live production issue.
Now Requirements: "Who You Are" list:
"8+ years of experience in program management, NPI, operations, or quality within hardware manufacturing environments, spanning both new product launches and sustaining or steady-state production.
Demonstrated ownership of NPI programs through EVT, DVT, PVT, and MP build phases, with direct experience driving build and test readiness.
Experience managing sustaining engineering programs, including ECOs, running changes, second-source qualification, or end-of-life and product transition planning.
A track record of facilitating cross-functional resolution of quality issues under time pressure, both during fast-moving NPI ramps and in live production environments, without formal authority over the teams involved.
Excellent structured communication skills, with the ability to present program status and risk to senior leadership and drive alignment across technical and non-technical stakeholders.
Strong program and project management fundamentals, including schedule management, risk tracking, milestone and gate reviews, and action item management.
Experience working with supply chain, contract manufacturers, or ODM/OEM partners.
Bachelor’s degree in Engineering, Operations, or a related field."
We can put each as - under Requirements.
Qualifications: "Preferred" section:
"Preferred 12+ years of direct experience in program management, NPI, operations, or quality.
Deep understanding of server architecture.
Familiarity with PLM and ERP systems.
Strong working knowledge of quality tools and methodologies, including FMEA, 8D, CAPA, root cause analysis, and containment and corrective action processes.
A strong history of building processes and systems that add structure across organizations."
We can put under Qualifications.
Skills: Not explicit; we could omit.
Benefits: list under "What We Offer". The list includes:
"Medical, dental, and vision insurance - 100% paid for by CoreWeave
Company-paid Life Insurance
Voluntary supplemental life insurance
Short and long-term disability insurance
Flexible Spending Account
Health Savings Account
Tuition Reimbursement
Ability to Participate in Employee Stock Purchase Program (ESPP)
Mental Wellness Benefits through Spring Health
Family-Forming support provided by Carrot
Paid Parental Leave
Flexible, full-service childcare support with Kinside
401(k) with a generous employer match
Flexible PTO
Catered lunch each day in our office and data center locations
A casual work environment
A work culture focused on innovative disruption"
We should keep as bullet list.
Pay: "The base salary range for this role is $207,000 to $275,000. The starting salary will be determined by job-related knowledge, skills, experience, and the market location. We strive for both market alignment and internal equity when determining compensation. In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)."
Also later: "The range we’ve posted represents the typical compensation range for this role. To determine actual compensation, we review the market rate for each candidate which can include a variety of factors. These include qualifications, experience, interview performance, and location. In addition to a competitive salary, we offer a variety of benefits to support your needs."
We can combine into Pay section prose.
Schedule: not present, omit.
Now About the role section: we need to include the prose from "What You’ll Do", "About The Role", maybe also the introductory paragraph about CoreWeave? The first paragraph about CoreWeave is company description; might be considered boilerplate? It's not about the role but about company. 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 didn't say to drop company description. However we should preserve all substantive information; the company description may be considered substantive? It's not about the role but maybe still part of posting. However typical job posting includes company overview; we could keep it as a paragraph under About the role or maybe a separate section? But we only have defined headings; we could include it in About the role as prose.
Thus About the role section will contain:
- The initial company overview paragraph: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com."
But the "Learn more at www.coreweave.com." maybe we can keep.
- Then "What You’ll Do ..." paragraph.
- Then "About The Role ..." paragraph.
We could combine them into a few
elements.
We must not include duplicated lines. Ensure we don't repeat.
Now we need to output only HTML fragment.
Let's construct:
About the role
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like specifics of responsibilities, requirements, qualifications, benefits, pay. We must not include boilerplate like EEO, export control, etc. Remove those. We must not include duplicated lines. We must not include navigation/cookie etc. We must not include application instructions. We must not include "Learn more at www.coreweave.com." maybe that's boilerplate? It's not essential but it's a link; maybe we can keep? It's not a duty. It's just a link. Probably can drop as it's not substantive about role. Safer to drop. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:
About the role
... prose summarizing what you'll do? But we must preserve all substantive info; we cannot summarize away detail. However we can keep the prose as is, maybe using paragraphs from the posting. The posting includes "What You’ll Do The Hardware Quality & Operations organization ..." then "About The Role CoreWeave is seeking ..." then "In This Role, You Will Manufacturing Program Management ..." That's a mix. We could keep the paragraphs as they are, but we need to separate sections. Better: For About the role, we can include the descriptive paragraphs before the bullet lists. For Responsibilities, we can list the three bullet areas with subdetails. But we must not lose details. Let's extract. Original text: "What You’ll Do The Hardware Quality & Operations organization at CoreWeave is responsible for delivering reliable, high-performance hardware infrastructure at scale. The team partners across engineering, product lifecycle management, supply chain, manufacturing, and quality to ensure new products and sustaining production lines are ready to build, test, and operate successfully." Then "About The Role CoreWeave is seeking an experienced Staff Manufacturing Operations Program Manager to join the Hardware Quality & Operations organization. This role will focus on manufacturing execution and transformation across new product introduction (NPI) and sustaining operations. You will lead cross-organizational build and test readiness alignment across NPI phases, drive sustaining program management, identify and mitigate risk, facilitate quality excursion oversight, and serve as a central point of alignment across engineering, PLM, supply chain, manufacturing, and quality stakeholders. This is a highly cross-functional, execution-focused role for someone who is comfortable bringing structure to ambiguity, translating technical risk into business impact, and holding technical teams accountable to program milestones across new product ramps and mature production lines." Then "In This Role, You Will Manufacturing Program Management Define and own the NPI manufacturing program plan across EVT, DVT, PVT, and MP phases, including schedule, build and test readiness, exit criteria, and go/no-go gate reviews.Own the transition from NPI to sustaining, ensuring process documentation, quality plans, spares strategy, and open action items are handed off cleanly to steady-state production.Stand up and maintain risk registers covering technical, supply chain, quality, and schedule risks across contract manufacturers, suppliers, and data centers.Own readiness reviews for changes introduced into active production lines, ensuring changes are validated and risk-assessed before rollout. Supply Chain Strategy Manage manufacturing strategies encompassing contract manufacturer expansion, data enablement, and cross-contract-manufacturer standardization.Lead the evolution of the Hardware Quality metrics framework. Cross-Functional Communication and Alignment Act as a primary point of alignment across engineering, manufacturing, supply chain, quality, and program and product management for assigned NPI and sustaining programs.Prepare and deliver executive-level program updates, including status, risks, and decisions needed, to leadership and cross-functional stakeholders.Build consensus across teams with competing priorities and drive decisions to closure when programs are at risk, whether during a new product ramp or a live production issue." Thus responsibilities can be captured as bullet list under each heading? But we need to use
- for any list of duties/requirements/benefits. So we can make a
- with each responsibility as
- . However each responsibility contains multiple sentences; we can keep them as is inside
- .
Thus:
Responsibilities
- Manufacturing Program Management: Define and own the NPI manufacturing program plan across EVT, DVT, PVT, and MP phases, including schedule, build and test readiness, exit criteria, and go/no-go gate reviews. Own the transition from NPI to sustaining, ensuring process documentation, quality plans, spares strategy, and open action items are handed off cleanly to steady-state production. Stand up and maintain risk registers covering technical, supply chain, quality, and schedule risks across contract manufacturers, suppliers, and data centers. Own readiness reviews for changes introduced into active production lines, ensuring changes are validated and risk-assessed before rollout.
- Supply Chain Strategy: Manage manufacturing strategies encompassing contract manufacturer expansion, data enablement, and cross-contract-manufacturer standardization. Lead the evolution of the Hardware Quality metrics framework.
- Cross-Functional Communication and Alignment: Act as a primary point of alignment across engineering, manufacturing, supply chain, quality, and program and product management for assigned NPI and sustaining programs. Prepare and deliver executive-level program updates, including status, risks, and decisions needed, to leadership and cross-functional stakeholders. Build consensus across teams with competing priorities and drive decisions to closure when programs are at risk, whether during a new product ramp or a live production issue.
- under Requirements.
Qualifications: "Preferred" section:
"Preferred 12+ years of direct experience in program management, NPI, operations, or quality.
Deep understanding of server architecture.
Familiarity with PLM and ERP systems.
Strong working knowledge of quality tools and methodologies, including FMEA, 8D, CAPA, root cause analysis, and containment and corrective action processes.
A strong history of building processes and systems that add structure across organizations."
We can put under Qualifications.
Skills: Not explicit; we could omit.
Benefits: list under "What We Offer". The list includes:
"Medical, dental, and vision insurance - 100% paid for by CoreWeave
Company-paid Life Insurance
Voluntary supplemental life insurance
Short and long-term disability insurance
Flexible Spending Account
Health Savings Account
Tuition Reimbursement
Ability to Participate in Employee Stock Purchase Program (ESPP)
Mental Wellness Benefits through Spring Health
Family-Forming support provided by Carrot
Paid Parental Leave
Flexible, full-service childcare support with Kinside
401(k) with a generous employer match
Flexible PTO
Catered lunch each day in our office and data center locations
A casual work environment
A work culture focused on innovative disruption"
We should keep as bullet list.
Pay: "The base salary range for this role is $207,000 to $275,000. The starting salary will be determined by job-related knowledge, skills, experience, and the market location. We strive for both market alignment and internal equity when determining compensation. In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)."
Also later: "The range we’ve posted represents the typical compensation range for this role. To determine actual compensation, we review the market rate for each candidate which can include a variety of factors. These include qualifications, experience, interview performance, and location. In addition to a competitive salary, we offer a variety of benefits to support your needs."
We can combine into Pay section prose.
Schedule: not present, omit.
Now About the role section: we need to include the prose from "What You’ll Do", "About The Role", maybe also the introductory paragraph about CoreWeave? The first paragraph about CoreWeave is company description; might be considered boilerplate? It's not about the role but about company. 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 didn't say to drop company description. However we should preserve all substantive information; the company description may be considered substantive? It's not about the role but maybe still part of posting. However typical job posting includes company overview; we could keep it as a paragraph under About the role or maybe a separate section? But we only have defined headings; we could include it in About the role as prose. Thus About the role section will contain: - The initial company overview paragraph: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com." But the "Learn more at www.coreweave.com." maybe we can keep. - Then "What You’ll Do ..." paragraph. - Then "About The Role ..." paragraph. We could combine them into a few
elements. We must not include duplicated lines. Ensure we don't repeat. Now we need to output only HTML fragment. Let's construct:
About the role