Director of Engineering, NPD & VAVE
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. 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the job description.
Key sections:
- Intro about Pentair (mission, etc.) Could be "About the role" or maybe "About Pentair". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can choose appropriate ones.
We have:
- "You will lead Pentair Pool’s Mechanical, Electrical, and Value Analysis / Value Engineering (VAVE) NPD teams in Apex, NC, and is the single accountable engineering owner for design decision rights and on-time technical delivery across the new product portfolio."
- Then "You Will" with subheadings: Specification & Program Ownership, Decision Rights & Cross-Functional Coordination, Value Analysis / Value Engineering (VAVE), Team Leadership & Talent Development.
These are responsibilities/duties.
Then "Key Qualifications" list.
Then "Compensation" with pay range.
Then "Benefits" list.
Then "Equal Opportunity Employer" boilerplate to remove.
We need to remove EEO boilerplate.
We need to preserve all substantive info.
We need to format using
for sections, - for lists,
for prose.
We need to decide sections:
Potential sections:
- About the role (or About Pentair) – include intro paragraph about Pentair mission and the opportunity.
- Responsibilities – include the "You Will" bullet points (maybe as list items). Could break into sub-sections? But we can just list responsibilities as
- .
- Qualifications – include Key Qualifications bullet list.
- Benefits – include Benefits paragraph/list.
- Pay – include Compensation paragraph (pay range). The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation range, so we can include Pay section.
We should not include Schedule (not mentioned).
We should not include Skills separate if not present; qualifications cover.
We need to avoid filler like "commensurate with experience" – but that appears in compensation description: "Actual compensation will be commensurate with demonstrable level of experience and training..." That's filler? It's not placeholder like "commensurate with experience" but it's a phrase. The instruction says 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. It says we should not emit a heading followed by filler/placeholder text. That means if we have a Pay section, we must not have just filler text; we need substantive content. The Pay section includes the pay range and explanation; that's substantive. So okay.
We need to avoid duplicative lines.
We need to remove duplicated lines: maybe some sentences repeat.
Let's extract substantive content.
Intro paragraph:
"At Pentair, you will work alongside passionate problem-solvers who are committed to the future of our planet. We put our mission into practice, helping the world sustainably move, improve, and enjoy water, life's most essential resource. From our residential water filtration to industrial water management to pool products and more, our 9,000 global employees serve customers in more than 150 countries, working to help create a better world for people and the planet through smart, sustainable water solutions. We have an opportunity for a Director of Engineering, NPD & VAVE, to join our Apex, NC team."
That's the intro.
We could put that under About the role.
Then responsibilities: The "You Will" section includes four bullet-like paragraphs:
- Specification & Program Ownership: Own engineering’s accountability for specification quality at program kickoff, resolving requirements ambiguity with Product Management/PLLs and the embedded Product Engineer organization before detailed design begins. Serve as the single accountable engineering owner for technical delivery across all active NPD programs, resolving cross-team (Mechanical/Electrical/VAVE) trade-offs without escalation. Drive stage-gate discipline with PMO and track a shared spec-quality metric (post-launch ECO volume) jointly with Product Management.
- Decision Rights & Cross-Functional Coordination: Hold clear design-authority decision rights within NPD engineering, eliminating team-level ownership ambiguity with Product Management. Partner with the Product Management organization, which now owns the embedded Product Engineer function, to maintain clean specification hand-off at program kickoff and throughout the design cycle. Represent NPD Engineering in stage-gate reviews and design reviews alongside PMO, NPI, SQA, Reliability, and Field Test; close cross-functional silo gaps that delay launch readiness.
- Value Analysis / Value Engineering (VAVE): Lead Value Engineering activity inside the NPD design cycle, embedding cost-avoidance and design-for-cost discipline into concept and detailed design rather than post-launch. Partner with Sustaining Engineering and Operations on VA/VE continuity across the product lifecycle and report design-phase (OCOGS) cost improvements delivered through active programs.
- Team Leadership & Talent Development: Lead 3 Engineering Managers (Mechanical NPD, Electrical NPD, VAVE Engineering) across ~25–28 engineers, designers, and product engineers in Apex, NC. Build engineering leadership bench strength across all four teams; develop a proven successor candidate for the Sr. Director role. Champion consistent NPD standard work (specification templates, design review templates, change control) to reduce variability and rework across teams.
We can turn each of these into
- items.
Qualifications: bullet list:
- Bachelor’s degree in mechanical, Electrical, or related Engineering discipline; Master’s or MBA preferred.
- 12+ years of engineering experience in new product development, including 5+ years leading multiple engineering disciplines (Mechanical, Electrical, and/or VAVE).
- Demonstrated success leading front-end specification definition and stage-gate NPD processes in a hardware/electromechanical product environment.
- Experience leading or partnering closely with Value Analysis / Value Engineering activity, with an understanding of VE-in-design vs. VA-post-launch distinctions.
- Proven ability to manage cross-functional decision rights and RACI-based governance with Product Management peers in a functional (non-matrix) organization, including partnering effectively with a Product Management-owned Product Engineer function.
- Strong program management acumen, including stage-gate/PMBOK-aligned governance and multi-team resource and priority trade-offs.
- Consumer/durable-goods or industrial hardware product experience preferred; pool, water technology, or connected-product experience a plus.
Benefits: paragraph: "As a Pentair employee, you would enjoy a wide array of benefit options to help keep you and your family healthy and protected, health benefits, a generous 401(k), employee stock purchase program, disability benefits, life insurance, critical illness insurance, accident insurance, parental leave, caregiver leave, tuition reimbursement, plus paid time off and wellness programs to encourage a healthy work/life balance."
We could turn that into a list? It's a sentence with commas. Could be a
- each benefit? The instruction: Use
- for any list of duties/requirements/benefits. So we should split benefits into list items.
Benefits list items:
- health benefits
- a generous 401(k)
- employee stock purchase program
- disability benefits
- life insurance
- critical illness insurance
- accident insurance
- parental leave
- caregiver leave
- tuition reimbursement
- paid time off
- wellness programs to encourage a healthy work/life balance
But note the phrase "health benefits" is generic; we can keep as is.
Pay section: Compensation paragraph:
"For this full-time position working at this location, the anticipated annualized base pay range will be from $149000- $276700 / year. At Pentair, it is not typical for an individual to be hired near the bottom or top of the pay range. Pentair considers various factors in determining actual compensation for this position at the expected location. Actual compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, work location, and other relevant business or organizational needs. This position may be eligible for other forms of compensation such as, annual incentive bonus and/or long-term incentives."
We need to keep that as prose (
). Note there is a stray comma after "such as," but we keep as is.
We must not include EEO boilerplate.
Now produce HTML fragment with sections.
We need to decide order: About the role, Responsibilities, Qualifications, Benefits, Pay. Could also put Pay before Benefits but order not critical.
We'll use
for each heading.
We'll not include any extra whitespace? It's fine.
Let's craft.
First, About the role: About the role
... intro paragraph ...
Then Responsibilities: Responsibilities
- ... each bullet ...
...
Then Qualifications: Qualifications
- ... each bullet ...
...
Then Benefits: Benefits
- ... each benefit ...
...
Then Pay: Pay
... compensation paragraph ...
Make sure to preserve all substantive info.
Check for any duplicated lines: The intro includes "We have an opportunity for a Director of Engineering, NPD & VAVE, to join our Apex, NC team." That's fine.
Check responsibilities: Ensure we didn't miss any detail.
Let's write each responsibility item exactly as in text.
Specification & Program Ownership:
"Own engineering’s accountability for specification quality at program kickoff, resolving requirements ambiguity with Product Management/PLLs and the embedded Product Engineer organization before detailed design begins. Serve as the single accountable engineering owner for technical delivery across all active NPD programs, resolving cross-team (Mechanical/Electrical/VAVE) trade-offs without escalation. Drive stage-gate discipline with PMO and track a shared spec-quality metric (post-launch ECO volume) jointly with Product Management."
Decision Rights & Cross-Functional Coordination:
"Hold clear design-authority decision rights within NPD engineering, eliminating team-level ownership ambiguity with Product Management. Partner with the Product Management organization, which now owns the embedded Product Engineer function, to maintain clean specification hand-off at program kickoff and throughout the design cycle. Represent NPD Engineering in stage-gate reviews and design reviews alongside PMO, NPI, SQA, Reliability, and Field Test; close cross-functional silo gaps that delay launch readiness."
Value Analysis / Value Engineering (VAVE):
"Lead Value Engineering activity inside the NPD design cycle, embedding cost-avoidance and design-for-cost discipline into concept and detailed design rather than post-launch. Partner with Sustaining Engineering and Operations on VA/VE continuity across the product lifecycle and
for prose. Do NOT repeat the job title as a heading. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the job description. Key sections: - Intro about Pentair (mission, etc.) Could be "About the role" or maybe "About Pentair". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can choose appropriate ones. We have: - "You will lead Pentair Pool’s Mechanical, Electrical, and Value Analysis / Value Engineering (VAVE) NPD teams in Apex, NC, and is the single accountable engineering owner for design decision rights and on-time technical delivery across the new product portfolio." - Then "You Will" with subheadings: Specification & Program Ownership, Decision Rights & Cross-Functional Coordination, Value Analysis / Value Engineering (VAVE), Team Leadership & Talent Development. These are responsibilities/duties. Then "Key Qualifications" list. Then "Compensation" with pay range. Then "Benefits" list. Then "Equal Opportunity Employer" boilerplate to remove. We need to remove EEO boilerplate. We need to preserve all substantive info. We need to format using
for sections, - for lists,
for prose.
We need to decide sections:
Potential sections:
- About the role (or About Pentair) – include intro paragraph about Pentair mission and the opportunity.
- Responsibilities – include the "You Will" bullet points (maybe as list items). Could break into sub-sections? But we can just list responsibilities as
- .
- Qualifications – include Key Qualifications bullet list.
- Benefits – include Benefits paragraph/list.
- Pay – include Compensation paragraph (pay range). The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation range, so we can include Pay section.
We should not include Schedule (not mentioned).
We should not include Skills separate if not present; qualifications cover.
We need to avoid filler like "commensurate with experience" – but that appears in compensation description: "Actual compensation will be commensurate with demonstrable level of experience and training..." That's filler? It's not placeholder like "commensurate with experience" but it's a phrase. The instruction says 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. It says we should not emit a heading followed by filler/placeholder text. That means if we have a Pay section, we must not have just filler text; we need substantive content. The Pay section includes the pay range and explanation; that's substantive. So okay.
We need to avoid duplicative lines.
We need to remove duplicated lines: maybe some sentences repeat.
Let's extract substantive content.
Intro paragraph:
"At Pentair, you will work alongside passionate problem-solvers who are committed to the future of our planet. We put our mission into practice, helping the world sustainably move, improve, and enjoy water, life's most essential resource. From our residential water filtration to industrial water management to pool products and more, our 9,000 global employees serve customers in more than 150 countries, working to help create a better world for people and the planet through smart, sustainable water solutions. We have an opportunity for a Director of Engineering, NPD & VAVE, to join our Apex, NC team."
That's the intro.
We could put that under About the role.
Then responsibilities: The "You Will" section includes four bullet-like paragraphs:
- Specification & Program Ownership: Own engineering’s accountability for specification quality at program kickoff, resolving requirements ambiguity with Product Management/PLLs and the embedded Product Engineer organization before detailed design begins. Serve as the single accountable engineering owner for technical delivery across all active NPD programs, resolving cross-team (Mechanical/Electrical/VAVE) trade-offs without escalation. Drive stage-gate discipline with PMO and track a shared spec-quality metric (post-launch ECO volume) jointly with Product Management.
- Decision Rights & Cross-Functional Coordination: Hold clear design-authority decision rights within NPD engineering, eliminating team-level ownership ambiguity with Product Management. Partner with the Product Management organization, which now owns the embedded Product Engineer function, to maintain clean specification hand-off at program kickoff and throughout the design cycle. Represent NPD Engineering in stage-gate reviews and design reviews alongside PMO, NPI, SQA, Reliability, and Field Test; close cross-functional silo gaps that delay launch readiness.
- Value Analysis / Value Engineering (VAVE): Lead Value Engineering activity inside the NPD design cycle, embedding cost-avoidance and design-for-cost discipline into concept and detailed design rather than post-launch. Partner with Sustaining Engineering and Operations on VA/VE continuity across the product lifecycle and report design-phase (OCOGS) cost improvements delivered through active programs.
- Team Leadership & Talent Development: Lead 3 Engineering Managers (Mechanical NPD, Electrical NPD, VAVE Engineering) across ~25–28 engineers, designers, and product engineers in Apex, NC. Build engineering leadership bench strength across all four teams; develop a proven successor candidate for the Sr. Director role. Champion consistent NPD standard work (specification templates, design review templates, change control) to reduce variability and rework across teams.
We can turn each of these into
- items.
Qualifications: bullet list:
- Bachelor’s degree in mechanical, Electrical, or related Engineering discipline; Master’s or MBA preferred.
- 12+ years of engineering experience in new product development, including 5+ years leading multiple engineering disciplines (Mechanical, Electrical, and/or VAVE).
- Demonstrated success leading front-end specification definition and stage-gate NPD processes in a hardware/electromechanical product environment.
- Experience leading or partnering closely with Value Analysis / Value Engineering activity, with an understanding of VE-in-design vs. VA-post-launch distinctions.
- Proven ability to manage cross-functional decision rights and RACI-based governance with Product Management peers in a functional (non-matrix) organization, including partnering effectively with a Product Management-owned Product Engineer function.
- Strong program management acumen, including stage-gate/PMBOK-aligned governance and multi-team resource and priority trade-offs.
- Consumer/durable-goods or industrial hardware product experience preferred; pool, water technology, or connected-product experience a plus.
Benefits: paragraph: "As a Pentair employee, you would enjoy a wide array of benefit options to help keep you and your family healthy and protected, health benefits, a generous 401(k), employee stock purchase program, disability benefits, life insurance, critical illness insurance, accident insurance, parental leave, caregiver leave, tuition reimbursement, plus paid time off and wellness programs to encourage a healthy work/life balance."
We could turn that into a list? It's a sentence with commas. Could be a
- each benefit? The instruction: Use
- for any list of duties/requirements/benefits. So we should split benefits into list items.
Benefits list items:
- health benefits
- a generous 401(k)
- employee stock purchase program
- disability benefits
- life insurance
- critical illness insurance
- accident insurance
- parental leave
- caregiver leave
- tuition reimbursement
- paid time off
- wellness programs to encourage a healthy work/life balance
But note the phrase "health benefits" is generic; we can keep as is.
Pay section: Compensation paragraph:
"For this full-time position working at this location, the anticipated annualized base pay range will be from $149000- $276700 / year. At Pentair, it is not typical for an individual to be hired near the bottom or top of the pay range. Pentair considers various factors in determining actual compensation for this position at the expected location. Actual compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, work location, and other relevant business or organizational needs. This position may be eligible for other forms of compensation such as, annual incentive bonus and/or long-term incentives."
We need to keep that as prose (
). Note there is a stray comma after "such as," but we keep as is.
We must not include EEO boilerplate.
Now produce HTML fragment with sections.
We need to decide order: About the role, Responsibilities, Qualifications, Benefits, Pay. Could also put Pay before Benefits but order not critical.
We'll use
for each heading.
We'll not include any extra whitespace? It's fine.
Let's craft.
First, About the role: About the role
... intro paragraph ...
Then Responsibilities: Responsibilities
- ... each bullet ...
...
Then Qualifications: Qualifications
- ... each bullet ...
...
Then Benefits: Benefits
- ... each benefit ...
...
Then Pay: Pay
... compensation paragraph ...
Make sure to preserve all substantive info.
Check for any duplicated lines: The intro includes "We have an opportunity for a Director of Engineering, NPD & VAVE, to join our Apex, NC team." That's fine.
Check responsibilities: Ensure we didn't miss any detail.
Let's write each responsibility item exactly as in text.
Specification & Program Ownership:
"Own engineering’s accountability for specification quality at program kickoff, resolving requirements ambiguity with Product Management/PLLs and the embedded Product Engineer organization before detailed design begins. Serve as the single accountable engineering owner for technical delivery across all active NPD programs, resolving cross-team (Mechanical/Electrical/VAVE) trade-offs without escalation. Drive stage-gate discipline with PMO and track a shared spec-quality metric (post-launch ECO volume) jointly with Product Management."
Decision Rights & Cross-Functional Coordination:
"Hold clear design-authority decision rights within NPD engineering, eliminating team-level ownership ambiguity with Product Management. Partner with the Product Management organization, which now owns the embedded Product Engineer function, to maintain clean specification hand-off at program kickoff and throughout the design cycle. Represent NPD Engineering in stage-gate reviews and design reviews alongside PMO, NPI, SQA, Reliability, and Field Test; close cross-functional silo gaps that delay launch readiness."
Value Analysis / Value Engineering (VAVE):
"Lead Value Engineering activity inside the NPD design cycle, embedding cost-avoidance and design-for-cost discipline into concept and detailed design rather than post-launch. Partner with Sustaining Engineering and Operations on VA/VE continuity across the product lifecycle and
for prose. We need to decide sections: Potential sections: - About the role (or About Pentair) – include intro paragraph about Pentair mission and the opportunity. - Responsibilities – include the "You Will" bullet points (maybe as list items). Could break into sub-sections? But we can just list responsibilities as
- . - Qualifications – include Key Qualifications bullet list. - Benefits – include Benefits paragraph/list. - Pay – include Compensation paragraph (pay range). The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation range, so we can include Pay section. We should not include Schedule (not mentioned). We should not include Skills separate if not present; qualifications cover. We need to avoid filler like "commensurate with experience" – but that appears in compensation description: "Actual compensation will be commensurate with demonstrable level of experience and training..." That's filler? It's not placeholder like "commensurate with experience" but it's a phrase. The instruction says 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. It says we should not emit a heading followed by filler/placeholder text. That means if we have a Pay section, we must not have just filler text; we need substantive content. The Pay section includes the pay range and explanation; that's substantive. So okay. We need to avoid duplicative lines. We need to remove duplicated lines: maybe some sentences repeat. Let's extract substantive content. Intro paragraph: "At Pentair, you will work alongside passionate problem-solvers who are committed to the future of our planet. We put our mission into practice, helping the world sustainably move, improve, and enjoy water, life's most essential resource. From our residential water filtration to industrial water management to pool products and more, our 9,000 global employees serve customers in more than 150 countries, working to help create a better world for people and the planet through smart, sustainable water solutions. We have an opportunity for a Director of Engineering, NPD & VAVE, to join our Apex, NC team." That's the intro. We could put that under About the role. Then responsibilities: The "You Will" section includes four bullet-like paragraphs: - Specification & Program Ownership: Own engineering’s accountability for specification quality at program kickoff, resolving requirements ambiguity with Product Management/PLLs and the embedded Product Engineer organization before detailed design begins. Serve as the single accountable engineering owner for technical delivery across all active NPD programs, resolving cross-team (Mechanical/Electrical/VAVE) trade-offs without escalation. Drive stage-gate discipline with PMO and track a shared spec-quality metric (post-launch ECO volume) jointly with Product Management. - Decision Rights & Cross-Functional Coordination: Hold clear design-authority decision rights within NPD engineering, eliminating team-level ownership ambiguity with Product Management. Partner with the Product Management organization, which now owns the embedded Product Engineer function, to maintain clean specification hand-off at program kickoff and throughout the design cycle. Represent NPD Engineering in stage-gate reviews and design reviews alongside PMO, NPI, SQA, Reliability, and Field Test; close cross-functional silo gaps that delay launch readiness. - Value Analysis / Value Engineering (VAVE): Lead Value Engineering activity inside the NPD design cycle, embedding cost-avoidance and design-for-cost discipline into concept and detailed design rather than post-launch. Partner with Sustaining Engineering and Operations on VA/VE continuity across the product lifecycle and report design-phase (OCOGS) cost improvements delivered through active programs. - Team Leadership & Talent Development: Lead 3 Engineering Managers (Mechanical NPD, Electrical NPD, VAVE Engineering) across ~25–28 engineers, designers, and product engineers in Apex, NC. Build engineering leadership bench strength across all four teams; develop a proven successor candidate for the Sr. Director role. Champion consistent NPD standard work (specification templates, design review templates, change control) to reduce variability and rework across teams. We can turn each of these into
- items.
Qualifications: bullet list:
- Bachelor’s degree in mechanical, Electrical, or related Engineering discipline; Master’s or MBA preferred.
- 12+ years of engineering experience in new product development, including 5+ years leading multiple engineering disciplines (Mechanical, Electrical, and/or VAVE).
- Demonstrated success leading front-end specification definition and stage-gate NPD processes in a hardware/electromechanical product environment.
- Experience leading or partnering closely with Value Analysis / Value Engineering activity, with an understanding of VE-in-design vs. VA-post-launch distinctions.
- Proven ability to manage cross-functional decision rights and RACI-based governance with Product Management peers in a functional (non-matrix) organization, including partnering effectively with a Product Management-owned Product Engineer function.
- Strong program management acumen, including stage-gate/PMBOK-aligned governance and multi-team resource and priority trade-offs.
- Consumer/durable-goods or industrial hardware product experience preferred; pool, water technology, or connected-product experience a plus.
Benefits: paragraph: "As a Pentair employee, you would enjoy a wide array of benefit options to help keep you and your family healthy and protected, health benefits, a generous 401(k), employee stock purchase program, disability benefits, life insurance, critical illness insurance, accident insurance, parental leave, caregiver leave, tuition reimbursement, plus paid time off and wellness programs to encourage a healthy work/life balance."
We could turn that into a list? It's a sentence with commas. Could be a
- each benefit? The instruction: Use
- for any list of duties/requirements/benefits. So we should split benefits into list items.
Benefits list items:
- health benefits
- a generous 401(k)
- employee stock purchase program
- disability benefits
- life insurance
- critical illness insurance
- accident insurance
- parental leave
- caregiver leave
- tuition reimbursement
- paid time off
- wellness programs to encourage a healthy work/life balance
But note the phrase "health benefits" is generic; we can keep as is.
Pay section: Compensation paragraph:
"For this full-time position working at this location, the anticipated annualized base pay range will be from $149000- $276700 / year. At Pentair, it is not typical for an individual to be hired near the bottom or top of the pay range. Pentair considers various factors in determining actual compensation for this position at the expected location. Actual compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, work location, and other relevant business or organizational needs. This position may be eligible for other forms of compensation such as, annual incentive bonus and/or long-term incentives."
We need to keep that as prose (
). Note there is a stray comma after "such as," but we keep as is. We must not include EEO boilerplate. Now produce HTML fragment with sections. We need to decide order: About the role, Responsibilities, Qualifications, Benefits, Pay. Could also put Pay before Benefits but order not critical. We'll use
for each heading. We'll not include any extra whitespace? It's fine. Let's craft. First, About the role:
About the role
... intro paragraph ...
Then Responsibilities:Responsibilities
- ... each bullet ... ...
Qualifications
- ... each bullet ... ...
Benefits
- ... each benefit ... ...
Pay
... compensation paragraph ...
Make sure to preserve all substantive info. Check for any duplicated lines: The intro includes "We have an opportunity for a Director of Engineering, NPD & VAVE, to join our Apex, NC team." That's fine. Check responsibilities: Ensure we didn't miss any detail. Let's write each responsibility item exactly as in text. Specification & Program Ownership: "Own engineering’s accountability for specification quality at program kickoff, resolving requirements ambiguity with Product Management/PLLs and the embedded Product Engineer organization before detailed design begins. Serve as the single accountable engineering owner for technical delivery across all active NPD programs, resolving cross-team (Mechanical/Electrical/VAVE) trade-offs without escalation. Drive stage-gate discipline with PMO and track a shared spec-quality metric (post-launch ECO volume) jointly with Product Management." Decision Rights & Cross-Functional Coordination: "Hold clear design-authority decision rights within NPD engineering, eliminating team-level ownership ambiguity with Product Management. Partner with the Product Management organization, which now owns the embedded Product Engineer function, to maintain clean specification hand-off at program kickoff and throughout the design cycle. Represent NPD Engineering in stage-gate reviews and design reviews alongside PMO, NPI, SQA, Reliability, and Field Test; close cross-functional silo gaps that delay launch readiness." Value Analysis / Value Engineering (VAVE): "Lead Value Engineering activity inside the NPD design cycle, embedding cost-avoidance and design-for-cost discipline into concept and detailed design rather than post-launch. Partner with Sustaining Engineering and Operations on VA/VE continuity across the product lifecycle and
- for any list of duties/requirements/benefits. So we should split benefits into list items.
Benefits list items:
- health benefits
- a generous 401(k)
- employee stock purchase program
- disability benefits
- life insurance
- critical illness insurance
- accident insurance
- parental leave
- caregiver leave
- tuition reimbursement
- paid time off
- wellness programs to encourage a healthy work/life balance
But note the phrase "health benefits" is generic; we can keep as is.
Pay section: Compensation paragraph:
"For this full-time position working at this location, the anticipated annualized base pay range will be from $149000- $276700 / year. At Pentair, it is not typical for an individual to be hired near the bottom or top of the pay range. Pentair considers various factors in determining actual compensation for this position at the expected location. Actual compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, work location, and other relevant business or organizational needs. This position may be eligible for other forms of compensation such as, annual incentive bonus and/or long-term incentives."
We need to keep that as prose (
- each benefit? The instruction: Use