Manufacturing Operations Program Manager
for each heading only if there is real content. Do not repeat job title. Remove boilerplate etc. Need to extract content.
Let's parse the posting.
First paragraph: description of CoreWeave (company intro). Not needed? Might be considered "About the role"? Actually "About The Role" heading appears later. The intro about CoreWeave could be considered "About the role"? But they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings.
We have sections:
- "What You’ll Do" then description of Hardware Quality & Operations organization and role. That could be "About the role" or "Responsibilities". The "About The Role" heading appears later with description.
Let's extract:
After "What You’ll Do": paragraph about organization and role.
Then "About The Role": heading and description: "CoreWeave is seeking an experienced Staff Manufacturing Operations Program Manager..." etc.
Then "In This Role, You Will": with sub-bullets: Manufacturing Program Management, Supply Chain Strategy, Cross-Functional Communication and Alignment. Those are responsibilities.
Then "Who You Are": list of requirements/experience.
Then "Preferred": additional preferred qualifications.
Then "Wondering if you’re a good fit?" with qualities.
Then "Why CoreWeave?" with culture description.
Then "The base salary range for this role is $207,000 to $275,000." plus description.
Then "What We Offer": benefits list.
Then location-specific sections (California Applicants etc.) which are boilerplate to remove.
We need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: likely the paragraph describing the role (maybe the "About The Role" section). Could combine the intro and "About The Role". We'll put a concise paragraph summarizing role.
Responsibilities: the bullet list under "In This Role, You Will" (Manufacturing Program Management, Supply Chain Strategy, Cross-Functional Communication and Alignment). Also maybe the earlier "What You’ll Do" paragraph could be considered responsibilities but we already have.
Requirements: the "Who You Are" mandatory qualifications (8+ years experience, etc.)
Qualifications: maybe the "Preferred" section (12+ years, etc.) Or we could treat "Qualifications" as the preferred qualifications.
Skills: maybe the "Wondering if you’re a good fit?" qualities (comfortable driving execution, curious, expert at translating technical risk). Could be skills.
Benefits: the list under "What We Offer".
Pay: the salary range.
Schedule: not mentioned; we should not create Schedule section if no content.
We must not create sections with filler like "not specified". So omit Schedule.
Also we should not include Pay if not specified? It is specified: base salary range $207,000 to $275,000. So include Pay.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like EVT, DVT, PVT, MP phases, etc.
We need to format lists with - . For prose use
.
We must not include boilerplate like EEO, export control, etc. Remove those.
We need to ensure we don't repeat job title as heading.
Let's extract content precisely.
**About the role** (maybe combine):
From "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."
Also earlier "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."
We could combine both into About the role.
**Responsibilities**: Under "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.
We need to keep these as list items. Could group under subheadings? But we only allowed headings for sections; subheadings not specified. We could just make a flat list of responsibilities, but that loses grouping. However we can still include the subheadings as plain text inside
- maybe. But better to keep as
- with the subheading as part of the li text.
**Requirements**: "Who You Are":
- 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.
**Qualifications** (Preferred):
- 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.
**Skills**: from "Wondering if you’re a good fit?" qualities:
- You’re comfortable driving execution across complex, cross-functional hardware programs.
- You’re curious about how manufacturing, quality, supply chain, and engineering systems work together at scale.
- You’re an expert at translating technical risk into clear decisions and measurable business outcomes.
We could also include other skills like "Excellent structured communication skills" but that's already in Requirements. We'll keep these three as Skills.
**Benefits**: list under "What We Offer":
- 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 list.
**Pay**: The base salary range for this role is $207,000 to $275,000. plus description: "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." This is somewhat repetitive; we need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the info but we can combine similar sentences without losing detail. However we must not summarize away detail; we can keep both sentences as separate paragraphs; that's fine.
We'll put Pay section with maybe two paragraphs.
**Schedule**: no info, so omit.
Now produce HTML fragment with
headings for each section we include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to ensure we don't include empty sections.
Let's craft.
About the role: combine two paragraphs.
Paragraph1: "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."
Paragraph2: "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."
Responsibilities: we can make a with each responsibility as - . Might be long; we can include sub-bullets? Not allowed? Only
- for any list. We can still have nested lists? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists
- . For prose use
. We must not include boilerplate like EEO, export control, etc. Remove those. We need to ensure we don't repeat job title as heading. Let's extract content precisely. **About the role** (maybe combine): From "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." Also earlier "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." We could combine both into About the role. **Responsibilities**: Under "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. We need to keep these as list items. Could group under subheadings? But we only allowed headings for sections; subheadings not specified. We could just make a flat list of responsibilities, but that loses grouping. However we can still include the subheadings as plain text inside
- maybe. But better to keep as
- with the subheading as part of the li text.
**Requirements**: "Who You Are":
- 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.
**Qualifications** (Preferred):
- 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.
**Skills**: from "Wondering if you’re a good fit?" qualities:
- You’re comfortable driving execution across complex, cross-functional hardware programs.
- You’re curious about how manufacturing, quality, supply chain, and engineering systems work together at scale.
- You’re an expert at translating technical risk into clear decisions and measurable business outcomes.
We could also include other skills like "Excellent structured communication skills" but that's already in Requirements. We'll keep these three as Skills.
**Benefits**: list under "What We Offer":
- 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 list.
**Pay**: The base salary range for this role is $207,000 to $275,000. plus description: "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." This is somewhat repetitive; we need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the info but we can combine similar sentences without losing detail. However we must not summarize away detail; we can keep both sentences as separate paragraphs; that's fine.
We'll put Pay section with maybe two paragraphs.
**Schedule**: no info, so omit.
Now produce HTML fragment with
headings for each section we include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't include empty sections. Let's craft. About the role: combine two paragraphs. Paragraph1: "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." Paragraph2: "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." Responsibilities: we can make a
- with each responsibility as
- . Might be long; we can include sub-bullets? Not allowed? Only
- for any list. We can still have nested lists? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists
- for any list. We can still have nested lists? The instruction says use
- . Might be long; we can include sub-bullets? Not allowed? Only
- with the subheading as part of the li text.
**Requirements**: "Who You Are":
- 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.
**Qualifications** (Preferred):
- 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.
**Skills**: from "Wondering if you’re a good fit?" qualities:
- You’re comfortable driving execution across complex, cross-functional hardware programs.
- You’re curious about how manufacturing, quality, supply chain, and engineering systems work together at scale.
- You’re an expert at translating technical risk into clear decisions and measurable business outcomes.
We could also include other skills like "Excellent structured communication skills" but that's already in Requirements. We'll keep these three as Skills.
**Benefits**: list under "What We Offer":
- 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 list.
**Pay**: The base salary range for this role is $207,000 to $275,000. plus description: "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." This is somewhat repetitive; we need to preserve all substantive information but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the info but we can combine similar sentences without losing detail. However we must not summarize away detail; we can keep both sentences as separate paragraphs; that's fine.
We'll put Pay section with maybe two paragraphs.
**Schedule**: no info, so omit.
Now produce HTML fragment with