AI Product Manager
Hewlett Packard Enterprise · Roseville, CA · 1 mo ago
MarketingFull-time
We need to output HTML fragment with sections: headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. Must not include filler like "commensurate with experience". Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to parse the posting.
Key content:
- Onsite expectation: "This role has been designed as ‘’Onsite with an expectation that you will primarily work from an HPE office." Also later: "This is a remote position within the United States. Candidates maybe required to work a hybrid schedule if within close proximity to an HPE Office." So we have location info: Onsite expectation, remote within US, hybrid schedule if near office. Should we include a Schedule section? The posting mentions schedule: remote, hybrid if near office. That's schedule info. So we can include a
for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. Must not include filler like "commensurate with experience". Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to parse the posting.
Key content:
- Onsite expectation: "This role has been designed as ‘’Onsite with an expectation that you will primarily work from an HPE office." Also later: "This is a remote position within the United States. Candidates maybe required to work a hybrid schedule if within close proximity to an HPE Office." So we have location info: Onsite expectation, remote within US, hybrid schedule if near office. Should we include a Schedule section? The posting mentions schedule: remote, hybrid if near office. That's schedule info. So we can include a Schedule
with description.
- Who We Are: description of HPE.
- Job Description: includes Job Family Definition, Management Level Definition.
- Responsibilities: list of bullet points.
- Education And Experience Required: list.
- Knowledge And Skills: list.
- Accessibility: note about accommodation.
- What We Can Offer You: includes Health & Wellbeing, Personal & Professional Development, Unconditional Inclusion (these are like benefits). Also maybe benefits section.
- Salary: Pay section with salary ranges.
- Benefits: maybe we can combine under Benefits heading.
We must not include boilerplate like EEO, fraud alert, etc.
We must not include duplicated lines.
We need to preserve all substantive information.
We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which headings to use based on content.
Possible sections:
- About the role (or Who We Are) maybe "About the role" or "About HPE". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches.
We have "Who We Are" describing HPE. Could map to "About the role"? Might be "About the role" but that's more about the role itself. However we have no explicit "About the role" but we have "Who We Are". Could still use "About the role" heading and put that content. Or we could use "About HPE". But instruction says use those examples; not strict but we should follow. Probably better to use "About the role" for the company description.
We have responsibilities list.
We have Education And Experience Required -> could be "Requirements" or "Qualifications". We'll use "Requirements" for education/experience, and "Qualifications" maybe for knowledge/skills? Or combine.
We have Knowledge And Skills -> could be "Skills".
We have What We Can Offer You -> benefits.
We have Pay -> salary.
We have Schedule -> remote/hybrid.
We also have Accessibility note; maybe we can include under Benefits or a separate section? Not in list but could be part of Benefits? Might be better to include as a short paragraph under Benefits or as its own section? The instruction says include a section ONLY when posting has real specific content for it. Accessibility is specific content. But there is no heading example for Accessibility. Could we create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. Could we fold Accessibility into Benefits? It's about accommodation, not exactly benefits but could be part of Benefits/Wellbeing. Might be okay.
We must not include boilerplate like EEO, fraud alert, etc.
We need to output only HTML fragment, no /, no markdown.
Let's extract substantive content.
**Who We Are** paragraph:
"Hewlett Packard Enterprise is the global edge-to-cloud company advancing the way people live and work. We help companies connect, protect, analyze, and act on their data and applications wherever they live, from edge to cloud, so they can turn insights into outcomes at the speed required to thrive in today’s complex world. Our culture thrives on finding new and better ways to accelerate what’s next. We know varied backgrounds are valued and succeed here. We have the flexibility to manage our work and personal needs. We make bold moves, together, and are a force for good. If you are looking to stretch and grow your career our culture will embrace you. Open up opportunities with HPE."
We'll keep that.
**Job Description** includes Job Family Definition and Management Level Definition. Could be part of About the role? Might be better to include under "About the role" or maybe a separate section "Job Description". But not in list. Could incorporate into About the role.
But we need to preserve all substantive information. So we need to include those definitions somewhere.
We could create a section "About the role" that includes the Job Family Definition and Management Level Definition plus Who We Are.
Alternatively, we could have a section "About the role" for Who We Are, and another section "Job Description" for definitions. But the instruction only gave examples; not prohibited to add other headings. However to be safe, we could stick to the given headings and put everything under them.
Maybe we can use "About the role" for the narrative about HPE and the job family/management level definitions.
Then "Responsibilities" for the list.
Then "Requirements" for Education And Experience Required.
Then "Skills" for Knowledge And Skills.
Then "Benefits" for What We Can Offer You (including Health & Wellbeing, Personal & Professional Development, Unconditional Inclusion).
Then "Pay" for salary range.
Then "Schedule" for remote/hybrid/onsite expectation.
We also have Accessibility note; we could fold into Benefits as a bullet about accommodation.
Now let's extract each piece.
**Responsibilities** list:
- Leads and drives the end to end strategy and operational product roadmap for a product
- Defines the value proposition, target customer segments, and business case for platform capabilities and innovations, balancing customer outcomes with company-wide portfolio priorities, revenue impact, margins, and financial targets.
- Translate market requirements into clear product requirements through having intimate customer knowledge and business, financial and industry market acumen
- Advises and influences key stakeholders on platform and portfolio strategy across all phases of the lifecycle (e.g., planning, development, launch, management, exit)
- Creates goal alignment and collaborates across value chain partners to drive successful delivery, adoption, and lifecycle management of platform capabilities, enabling effective go-to-market execution and optimized business outcomes.
Note: The bullet list may have inconsistent capitalization; we keep as is.
**Education And Experience Required**:
- Bachelor's degree or equivalent in computer science, engineering or related field of study.
- MBA or advanced degree in computer science or engineering preferred.
- 4+ years of work experience in related field.
- Technical understanding and knowledge of the relevant industry.
**Knowledge And Skills**:
- Demonstrated ability to develop product strategy, including the application of AI driven capabilities, and lead teams to achieve results.
- Strong business acumen with the ability to use data, analytics, and AI-enabled insights to uncover systemic issues, guide root cause analysis, and enable proactive improvements across support platforms and portals.
- Demonstrated skills in cost efficient solution building, financial performance metric creation and analysis.
- Technical understanding and knowledge of networking support industry and ability to translate AI and cloud-based solutions into product-specific guidance and technical enablement for teams.
**What We Can Offer You**:
We have three bullet-like sections:
- Health & Wellbeing: "We strive to provide our team members and their loved ones with a comprehensive suite of benefits that supports their physical, financial and emotional wellbeing."
- Personal & Professional Development: "We also invest in your career because the better you are, the better we all are. We have specific programs catered to helping you reach any career goals you have — whether you want to become a knowledge expert in your field or apply your skills to another division."
- Unconditional Inclusion: "We are unconditionally inclusive in the way we work and celebrate individual uniqueness. We know varied backgrounds are valued and succeed here. We have the flexibility to manage our work and personal needs. We make bold moves, together, and are a force for good."
Also there is "Let's Stay Connected Follow @HPECareers on Instagram..." that's likely boilerplate/social media; could be considered navigation? Might be considered boilerplate; we should remove.
**Pay**:
"The expected salary/wage range for this position is provided below. Actual offer may vary from this range based upon geographic location, work experience, education/training, and/or skill level. – United States of America: Annual Salary USD 136,500 - 276,500 in California // 120,500 - 276,500 in Georgia & North Carolina & Texas The listed salary range reflects base salary. Variable incentives may also be offered."
We need to preserve that.
**Schedule**:
We have: "This role has been designed as ‘’Onsite with an expectation that you will primarily work from an HPE office." Also: "This is a remote position within the United States. Candidates maybe required to work a hybrid schedule if within close proximity to an HPE Office."
We need to combine: Onsite expectation, remote within US, hybrid if near office.
We'll produce a paragraph summarizing.
**Accessibility**:
"If you believe you require accommodation during any stage of the application or interview process, please submit your request by completing our secure form linked here. Note: This option is reserved for applicants needing assistance/reasonable accommodation related to a disability."
We can include as a paragraph under Benefits maybe.
Now we need to ensure we don't include boilerplate like EEO, fraud alert, etc.
Also need to remove duplicated lines: there may be duplicated sentences like "We know varied backgrounds are valued and succeed here." appears multiple times (in Who We Are, Unconditional Inclusion). We should keep both? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should not remove duplicated lines if they are substantive? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. That means if the same sentence appears multiple times, we should keep only one instance. Which one? Probably keep one. We'll need to deduplicate.
Identify duplicated lines:
- "We know varied backgrounds are valued and succeed here." appears in Who We Are paragraph and also in Unconditional Inclusion paragraph. Also appears maybe elsewhere? We'll keep one instance.
- "We have the flexibility to manage our work and personal needs." appears in Who We Are and also in Unconditional Inclusion. Duplicate.
- "We make bold moves, together, and are a force for good." appears in Who We Are and Unconditional Inclusion. Duplicate.
Thus we need to keep only one copy of each. We'll keep them in the first occurrence (Who Are) and omit duplicates in Unconditional Inclusion.
Now also "Open up opportunities with HPE." appears only once.
Now also "We strive to provide our team members and their loved ones with a comprehensive suite of benefits that supports their physical, financial and emotional wellbeing." appears only once.
Now "We also invest in your career because the better you are, the better we all are." appears only once.
Now "We are unconditionally inclusive in the way we work and celebrate individual uniqueness." appears only once (after dedup).
Now we need to ensure we don't include any application instructions like "Please click here: Equal Employment Opportunity." etc. We'll remove.
Now we need to format.
We'll produce:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches.
We have "Who We Are" describing HPE. Could map to "About the role"? Might be "About the role" but that's more about the role itself. However we have no explicit "About the role" but we have "Who We Are". Could still use "About the role" heading and put that content. Or we could use "About HPE". But instruction says use those examples; not strict but we should follow. Probably better to use "About the role" for the company description.
We have responsibilities list.
We have Education And Experience Required -> could be "Requirements" or "Qualifications". We'll use "Requirements" for education/experience, and "Qualifications" maybe for knowledge/skills? Or combine.
We have Knowledge And Skills -> could be "Skills".
We have What We Can Offer You -> benefits.
We have Pay -> salary.
We have Schedule -> remote/hybrid.
We also have Accessibility note; maybe we can include under Benefits or a separate section? Not in list but could be part of Benefits? Might be better to include as a short paragraph under Benefits or as its own section? The instruction says include a section ONLY when posting has real specific content for it. Accessibility is specific content. But there is no heading example for Accessibility. Could we create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. Could we fold Accessibility into Benefits? It's about accommodation, not exactly benefits but could be part of Benefits/Wellbeing. Might be okay.
We must not include boilerplate like EEO, fraud alert, etc.
We need to output only HTML fragment, no /, no markdown.
Let's extract substantive content.
**Who We Are** paragraph:
"Hewlett Packard Enterprise is the global edge-to-cloud company advancing the way people live and work. We help companies connect, protect, analyze, and act on their data and applications wherever they live, from edge to cloud, so they can turn insights into outcomes at the speed required to thrive in today’s complex world. Our culture thrives on finding new and better ways to accelerate what’s next. We know varied backgrounds are valued and succeed here. We have the flexibility to manage our work and personal needs. We make bold moves, together, and are a force for good. If you are looking to stretch and grow your career our culture will embrace you. Open up opportunities with HPE."
We'll keep that.
**Job Description** includes Job Family Definition and Management Level Definition. Could be part of About the role? Might be better to include under "About the role" or maybe a separate section "Job Description". But not in list. Could incorporate into About the role.
But we need to preserve all substantive information. So we need to include those definitions somewhere.
We could create a section "About the role" that includes the Job Family Definition and Management Level Definition plus Who We Are.
Alternatively, we could have a section "About the role" for Who We Are, and another section "Job Description" for definitions. But the instruction only gave examples; not prohibited to add other headings. However to be safe, we could stick to the given headings and put everything under them.
Maybe we can use "About the role" for the narrative about HPE and the job family/management level definitions.
Then "Responsibilities" for the list.
Then "Requirements" for Education And Experience Required.
Then "Skills" for Knowledge And Skills.
Then "Benefits" for What We Can Offer You (including Health & Wellbeing, Personal & Professional Development, Unconditional Inclusion).
Then "Pay" for salary range.
Then "Schedule" for remote/hybrid/onsite expectation.
We also have Accessibility note; we could fold into Benefits as a bullet about accommodation.
Now let's extract each piece.
**Responsibilities** list:
- Leads and drives the end to end strategy and operational product roadmap for a product
- Defines the value proposition, target customer segments, and business case for platform capabilities and innovations, balancing customer outcomes with company-wide portfolio priorities, revenue impact, margins, and financial targets.
- Translate market requirements into clear product requirements through having intimate customer knowledge and business, financial and industry market acumen
- Advises and influences key stakeholders on platform and portfolio strategy across all phases of the lifecycle (e.g., planning, development, launch, management, exit)
- Creates goal alignment and collaborates across value chain partners to drive successful delivery, adoption, and lifecycle management of platform capabilities, enabling effective go-to-market execution and optimized business outcomes.
Note: The bullet list may have inconsistent capitalization; we keep as is.
**Education And Experience Required**:
- Bachelor's degree or equivalent in computer science, engineering or related field of study.
- MBA or advanced degree in computer science or engineering preferred.
- 4+ years of work experience in related field.
- Technical understanding and knowledge of the relevant industry.
**Knowledge And Skills**:
- Demonstrated ability to develop product strategy, including the application of AI driven capabilities, and lead teams to achieve results.
- Strong business acumen with the ability to use data, analytics, and AI-enabled insights to uncover systemic issues, guide root cause analysis, and enable proactive improvements across support platforms and portals.
- Demonstrated skills in cost efficient solution building, financial performance metric creation and analysis.
- Technical understanding and knowledge of networking support industry and ability to translate AI and cloud-based solutions into product-specific guidance and technical enablement for teams.
**What We Can Offer You**:
We have three bullet-like sections:
- Health & Wellbeing: "We strive to provide our team members and their loved ones with a comprehensive suite of benefits that supports their physical, financial and emotional wellbeing."
- Personal & Professional Development: "We also invest in your career because the better you are, the better we all are. We have specific programs catered to helping you reach any career goals you have — whether you want to become a knowledge expert in your field or apply your skills to another division."
- Unconditional Inclusion: "We are unconditionally inclusive in the way we work and celebrate individual uniqueness. We know varied backgrounds are valued and succeed here. We have the flexibility to manage our work and personal needs. We make bold moves, together, and are a force for good."
Also there is "Let's Stay Connected Follow @HPECareers on Instagram..." that's likely boilerplate/social media; could be considered navigation? Might be considered boilerplate; we should remove.
**Pay**:
"The expected salary/wage range for this position is provided below. Actual offer may vary from this range based upon geographic location, work experience, education/training, and/or skill level. – United States of America: Annual Salary USD 136,500 - 276,500 in California // 120,500 - 276,500 in Georgia & North Carolina & Texas The listed salary range reflects base salary. Variable incentives may also be offered."
We need to preserve that.
**Schedule**:
We have: "This role has been designed as ‘’Onsite with an expectation that you will primarily work from an HPE office." Also: "This is a remote position within the United States. Candidates maybe required to work a hybrid schedule if within close proximity to an HPE Office."
We need to combine: Onsite expectation, remote within US, hybrid if near office.
We'll produce a paragraph summarizing.
**Accessibility**:
"If you believe you require accommodation during any stage of the application or interview process, please submit your request by completing our secure form linked here. Note: This option is reserved for applicants needing assistance/reasonable accommodation related to a disability."
We can include as a paragraph under Benefits maybe.
Now we need to ensure we don't include boilerplate like EEO, fraud alert, etc.
Also need to remove duplicated lines: there may be duplicated sentences like "We know varied backgrounds are valued and succeed here." appears multiple times (in Who We Are, Unconditional Inclusion). We should keep both? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should not remove duplicated lines if they are substantive? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. That means if the same sentence appears multiple times, we should keep only one instance. Which one? Probably keep one. We'll need to deduplicate.
Identify duplicated lines:
- "We know varied backgrounds are valued and succeed here." appears in Who We Are paragraph and also in Unconditional Inclusion paragraph. Also appears maybe elsewhere? We'll keep one instance.
- "We have the flexibility to manage our work and personal needs." appears in Who We Are and also in Unconditional Inclusion. Duplicate.
- "We make bold moves, together, and are a force for good." appears in Who We Are and Unconditional Inclusion. Duplicate.
Thus we need to keep only one copy of each. We'll keep them in the first occurrence (Who Are) and omit duplicates in Unconditional Inclusion.
Now also "Open up opportunities with HPE." appears only once.
Now also "We strive to provide our team members and their loved ones with a comprehensive suite of benefits that supports their physical, financial and emotional wellbeing." appears only once.
Now "We also invest in your career because the better you are, the better we all are." appears only once.
Now "We are unconditionally inclusive in the way we work and celebrate individual uniqueness." appears only once (after dedup).
Now we need to ensure we don't include any application instructions like "Please click here: Equal Employment Opportunity." etc. We'll remove.
Now we need to format.
We'll produce:
About the role
About the role
... (Who We Are + Job Family Definition + Management Level Definition)
But we need to include Job Family Definition and Management