Services Product Line Manager (Dallas, TX OR Houston, TX OR Raleigh, NC)
Hewlett Packard Enterprise · Raleigh, NC · 1 mo ago
Full-time
We need to output HTML fragment with sections: headings for sections present: About the role? Actually "Who We Are" could be considered About the role? The instruction: use
for sections present: About the role? Actually "Who We Are" could be considered About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have content: "Who We Are" description about HPE. That could be "About the role"? Actually "Who We Are" is about company, not role. But we can treat as "About the role"? The instruction says use those headings as examples; we can use appropriate headings based on content. Likely sections: About the role (maybe "Who We Are"), Responsibilities, Requirements (Education And Experience Required), Qualifications (maybe Knowledge And Skills?), Skills (maybe Knowledge And Skills?), Benefits (What We Can Offer You), Pay (salary range), Schedule (hybrid schedule). Also location info maybe part of schedule? Could be included in schedule or separate but not required.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accessibility, fraud alert, etc. Also remove "Accessibility" section? It's about accommodation but maybe considered boilerplate? It's not EEO but still about accommodation; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Accessibility is not exactly those but could be considered legal? Might be okay to keep? Safer to remove it as it's not substantive about role. Also remove "Let's Stay Connected", "Follow @HPECareers". Also remove "Job Engineering Job Level TCP_04". Also remove "Information about employee benefits offered in the US can be found at ..." maybe part of Benefits? We'll keep benefits description.
We need to preserve all substantive information. So we need to include:
- Who We Are: description of HPE.
- Job Description: summary of role: Product Line Manager, hybrid schedule Dallas/Houston/Raleigh-Durham, working on service and support lines, design, plan, develop and manage product/portfolio throughout lifecycle, etc.
- Responsibilities: list bullet points.
- Education And Experience Required: list.
- Knowledge And Skills: list.
- Benefits: Health & Wellbeing, Personal & Professional Development, Unconditional Inclusion (maybe duplicate of earlier). We'll keep those bullet points.
- Pay: salary range: USD 120,500 - 276,500 in North Carolina & Texas.
- Schedule: hybrid schedule, location: Dallas, TX or Houston, TX or Raleigh/Durham NC office, must reside in one of those areas.
We must not create sections with filler like "commensurate with experience". Not present.
We must not duplicate lines.
We need to output only HTML fragment, no /. Use for each section heading. Use - for lists. Use
for prose.
We need to decide which content goes into which section.
Let's outline:
About the role
maybe contains "Who We Are" and "Job Description"? But "About the role" could be a brief description of the role. The "Who We Are" is about company; maybe better as "About the company". But instruction examples include About the role. We could still use About the role to include both company overview and role summary. However we must not repeat job title as heading. It's fine.
Alternatively we could have separate sections: About the company (not in list) but we could still use About the company
though not in examples but allowed? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. So we should stick to those headings. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: could include company overview and role summary.
Responsibilities: list of responsibilities.
Requirements: Education And Experience Required.
Qualifications: maybe Knowledge And Skills? Or could be separate: Qualifications vs Skills. The posting has "Knowledge And Skills". Could treat as Skills. Qualifications maybe empty? But we must not create a section with filler. So if we don't have distinct qualifications beyond requirements, we could omit Qualifications section. However we have Knowledge And Skills which could be Skills section. So we can have Skills section for that.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We might also need Qualifications? Not needed.
Now we need to extract content.
About the role: combine "Who We Are" paragraph and "Job Description" paragraph (the first paragraph after Job Description). Let's capture:
Who We Are: "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."
Job Description: "HPE is seeking a Product Line Manager to work out of our Dallas, TX or Houston, TX office on a hybrid schedule. This person will be working on our service and support lines. This will include design, plan, develop and manage a product or portfolio of products throughout the solution portfolio lifecycle: from new product definition or enhancements to existing products; planning, design, forecasting, and production; to end of life. Our Product Line Managers contributions impact technical components of HPE products, solutions, or services regularly and sustainable. The Product Line Manager will apply advanced subject matter knowledge to solve complex business issues and is regarded as a subject matter expert. This person will also provide expertise and partnership to functional and technical project teams and may participate in cross-functional initiatives."
We should not repeat location/hybrid schedule in About the role? Might be okay but schedule will be separate.
Now Responsibilities: list bullet points from "Leads and drives..." etc.
Let's capture each bullet:
- Leads and drives the end to end strategy and operational product roadmap for one or more products.
- Defines the value proposition, target customer segments, and business case to bring one or more innovative and disruptive products to market with respect to the whole company product portfolio (i.e. Product configuration mix, Revenue/Margins, financials, market share).
- Synthesizes market requirements (MRD) into marketing/customer details through having intimate customer knowledge and business, financial and industry market acumen.
- Advises key stakeholders on the portfolio strategy across all phases of the lifecycle (e.g., planning, development, launch, management, exit).
- Creates and drives goal alignment and collaborates across one or more products' value chain partners to optimize margins and enable success of products per plans across the product lifecycle. (ie. Engineering: product development, Supply Chain: SKUs, inventory and Marketing: marketing and pricing strategies and Go To Market Plan).
Now Requirements: 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.
- 6+ years of work experience in Product Line Management.
- 6+ years of work experience in technical service and support.
- Technical understanding and knowledge of the relevant industry.
Now Skills: Knowledge And Skills:
- Expert team skills and ability to cross functionally drive/influence work through others, ability to mentor and lead teams to achieve results for complex, ambiguous projects.
- Expert skills in cost efficient solution building, financial performance metric creation and analysis.
- Expert business acumen and knowledge of root cause analysis and problem detection.
- Technical understanding and knowledge of the relevant industry and ability to provide product specific technical training to the team.
Now Benefits: What We Can Offer You:
- 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."
We could combine into a with each benefit as - containing the sentences.
Now Pay: salary range: "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 120,500 - 276,500 in North Carolina & Texas The listed salary range reflects base salary. Variable incentives may also be offered."
We need to preserve that. We'll put in
.
Now Schedule: hybrid schedule and location: "Location: This person will be working out of our Dallas, TX, OR Houston, TX , OR Raleigh / Durham NC office on a hybrid schedule therefore must reside in one of those areas." Also earlier: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home." Wait there is a conflict: earlier says Remote/Teleworker primarily work from home, later says hybrid schedule in Dallas/Houston/Raleigh-Durham. We need to preserve both. So schedule section should include both statements: remote/teleworker primarily work from home, and hybrid schedule requiring residence in those areas.
Thus schedule content: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home. The position is based out of our Dallas, TX, Houston, TX, or Raleigh/Durham, NC office on a hybrid schedule; therefore you must reside in one of those areas."
We need to ensure we don't duplicate.
Now we must not include boilerplate like EEO, accessibility, fraud alert, etc.
Now produce HTML.
Structure:
About the role
... combined who we are + job description ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine.
Now craft the content precisely.
About the role paragraph: combine who we are and job description. Ensure we don't repeat sentences. Let's write:
"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
for each section heading. Use - for lists. Use
for prose.
We need to decide which content goes into which section.
Let's outline:
About the role
maybe contains "Who We Are" and "Job Description"? But "About the role" could be a brief description of the role. The "Who We Are" is about company; maybe better as "About the company". But instruction examples include About the role. We could still use About the role to include both company overview and role summary. However we must not repeat job title as heading. It's fine.
Alternatively we could have separate sections: About the company (not in list) but we could still use About the company
though not in examples but allowed? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. So we should stick to those headings. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: could include company overview and role summary.
Responsibilities: list of responsibilities.
Requirements: Education And Experience Required.
Qualifications: maybe Knowledge And Skills? Or could be separate: Qualifications vs Skills. The posting has "Knowledge And Skills". Could treat as Skills. Qualifications maybe empty? But we must not create a section with filler. So if we don't have distinct qualifications beyond requirements, we could omit Qualifications section. However we have Knowledge And Skills which could be Skills section. So we can have Skills section for that.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We might also need Qualifications? Not needed.
Now we need to extract content.
About the role: combine "Who We Are" paragraph and "Job Description" paragraph (the first paragraph after Job Description). Let's capture:
Who We Are: "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."
Job Description: "HPE is seeking a Product Line Manager to work out of our Dallas, TX or Houston, TX office on a hybrid schedule. This person will be working on our service and support lines. This will include design, plan, develop and manage a product or portfolio of products throughout the solution portfolio lifecycle: from new product definition or enhancements to existing products; planning, design, forecasting, and production; to end of life. Our Product Line Managers contributions impact technical components of HPE products, solutions, or services regularly and sustainable. The Product Line Manager will apply advanced subject matter knowledge to solve complex business issues and is regarded as a subject matter expert. This person will also provide expertise and partnership to functional and technical project teams and may participate in cross-functional initiatives."
We should not repeat location/hybrid schedule in About the role? Might be okay but schedule will be separate.
Now Responsibilities: list bullet points from "Leads and drives..." etc.
Let's capture each bullet:
- Leads and drives the end to end strategy and operational product roadmap for one or more products.
- Defines the value proposition, target customer segments, and business case to bring one or more innovative and disruptive products to market with respect to the whole company product portfolio (i.e. Product configuration mix, Revenue/Margins, financials, market share).
- Synthesizes market requirements (MRD) into marketing/customer details through having intimate customer knowledge and business, financial and industry market acumen.
- Advises key stakeholders on the portfolio strategy across all phases of the lifecycle (e.g., planning, development, launch, management, exit).
- Creates and drives goal alignment and collaborates across one or more products' value chain partners to optimize margins and enable success of products per plans across the product lifecycle. (ie. Engineering: product development, Supply Chain: SKUs, inventory and Marketing: marketing and pricing strategies and Go To Market Plan).
Now Requirements: 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.
- 6+ years of work experience in Product Line Management.
- 6+ years of work experience in technical service and support.
- Technical understanding and knowledge of the relevant industry.
Now Skills: Knowledge And Skills:
- Expert team skills and ability to cross functionally drive/influence work through others, ability to mentor and lead teams to achieve results for complex, ambiguous projects.
- Expert skills in cost efficient solution building, financial performance metric creation and analysis.
- Expert business acumen and knowledge of root cause analysis and problem detection.
- Technical understanding and knowledge of the relevant industry and ability to provide product specific technical training to the team.
Now Benefits: What We Can Offer You:
- 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."
We could combine into a with each benefit as - containing the sentences.
Now Pay: salary range: "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 120,500 - 276,500 in North Carolina & Texas The listed salary range reflects base salary. Variable incentives may also be offered."
We need to preserve that. We'll put in
.
Now Schedule: hybrid schedule and location: "Location: This person will be working out of our Dallas, TX, OR Houston, TX , OR Raleigh / Durham NC office on a hybrid schedule therefore must reside in one of those areas." Also earlier: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home." Wait there is a conflict: earlier says Remote/Teleworker primarily work from home, later says hybrid schedule in Dallas/Houston/Raleigh-Durham. We need to preserve both. So schedule section should include both statements: remote/teleworker primarily work from home, and hybrid schedule requiring residence in those areas.
Thus schedule content: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home. The position is based out of our Dallas, TX, Houston, TX, or Raleigh/Durham, NC office on a hybrid schedule; therefore you must reside in one of those areas."
We need to ensure we don't duplicate.
Now we must not include boilerplate like EEO, accessibility, fraud alert, etc.
Now produce HTML.
Structure:
About the role
... combined who we are + job description ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine.
Now craft the content precisely.
About the role paragraph: combine who we are and job description. Ensure we don't repeat sentences. Let's write:
"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
for prose. We need to decide which content goes into which section. Let's outline:
About the role
maybe contains "Who We Are" and "Job Description"? But "About the role" could be a brief description of the role. The "Who We Are" is about company; maybe better as "About the company". But instruction examples include About the role. We could still use About the role to include both company overview and role summary. However we must not repeat job title as heading. It's fine. Alternatively we could have separate sections: About the company (not in list) but we could still useAbout the company
though not in examples but allowed? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. So we should stick to those headings. So we need to map content to those headings.
Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: could include company overview and role summary.
Responsibilities: list of responsibilities.
Requirements: Education And Experience Required.
Qualifications: maybe Knowledge And Skills? Or could be separate: Qualifications vs Skills. The posting has "Knowledge And Skills". Could treat as Skills. Qualifications maybe empty? But we must not create a section with filler. So if we don't have distinct qualifications beyond requirements, we could omit Qualifications section. However we have Knowledge And Skills which could be Skills section. So we can have Skills section for that.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We might also need Qualifications? Not needed.
Now we need to extract content.
About the role: combine "Who We Are" paragraph and "Job Description" paragraph (the first paragraph after Job Description). Let's capture:
Who We Are: "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."
Job Description: "HPE is seeking a Product Line Manager to work out of our Dallas, TX or Houston, TX office on a hybrid schedule. This person will be working on our service and support lines. This will include design, plan, develop and manage a product or portfolio of products throughout the solution portfolio lifecycle: from new product definition or enhancements to existing products; planning, design, forecasting, and production; to end of life. Our Product Line Managers contributions impact technical components of HPE products, solutions, or services regularly and sustainable. The Product Line Manager will apply advanced subject matter knowledge to solve complex business issues and is regarded as a subject matter expert. This person will also provide expertise and partnership to functional and technical project teams and may participate in cross-functional initiatives."
We should not repeat location/hybrid schedule in About the role? Might be okay but schedule will be separate.
Now Responsibilities: list bullet points from "Leads and drives..." etc.
Let's capture each bullet:
- Leads and drives the end to end strategy and operational product roadmap for one or more products.
- Defines the value proposition, target customer segments, and business case to bring one or more innovative and disruptive products to market with respect to the whole company product portfolio (i.e. Product configuration mix, Revenue/Margins, financials, market share).
- Synthesizes market requirements (MRD) into marketing/customer details through having intimate customer knowledge and business, financial and industry market acumen.
- Advises key stakeholders on the portfolio strategy across all phases of the lifecycle (e.g., planning, development, launch, management, exit).
- Creates and drives goal alignment and collaborates across one or more products' value chain partners to optimize margins and enable success of products per plans across the product lifecycle. (ie. Engineering: product development, Supply Chain: SKUs, inventory and Marketing: marketing and pricing strategies and Go To Market Plan).
Now Requirements: 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.
- 6+ years of work experience in Product Line Management.
- 6+ years of work experience in technical service and support.
- Technical understanding and knowledge of the relevant industry.
Now Skills: Knowledge And Skills:
- Expert team skills and ability to cross functionally drive/influence work through others, ability to mentor and lead teams to achieve results for complex, ambiguous projects.
- Expert skills in cost efficient solution building, financial performance metric creation and analysis.
- Expert business acumen and knowledge of root cause analysis and problem detection.
- Technical understanding and knowledge of the relevant industry and ability to provide product specific technical training to the team.
Now Benefits: What We Can Offer You:
- 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."
We could combine into a with each benefit as - containing the sentences.
Now Pay: salary range: "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 120,500 - 276,500 in North Carolina & Texas The listed salary range reflects base salary. Variable incentives may also be offered."
We need to preserve that. We'll put in
.
Now Schedule: hybrid schedule and location: "Location: This person will be working out of our Dallas, TX, OR Houston, TX , OR Raleigh / Durham NC office on a hybrid schedule therefore must reside in one of those areas." Also earlier: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home." Wait there is a conflict: earlier says Remote/Teleworker primarily work from home, later says hybrid schedule in Dallas/Houston/Raleigh-Durham. We need to preserve both. So schedule section should include both statements: remote/teleworker primarily work from home, and hybrid schedule requiring residence in those areas.
Thus schedule content: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home. The position is based out of our Dallas, TX, Houston, TX, or Raleigh/Durham, NC office on a hybrid schedule; therefore you must reside in one of those areas."
We need to ensure we don't duplicate.
Now we must not include boilerplate like EEO, accessibility, fraud alert, etc.
Now produce HTML.
Structure:
About the role
... combined who we are + job description ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine.
Now craft the content precisely.
About the role paragraph: combine who we are and job description. Ensure we don't repeat sentences. Let's write:
"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
- with each benefit as
- containing the sentences.
Now Pay: salary range: "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 120,500 - 276,500 in North Carolina & Texas The listed salary range reflects base salary. Variable incentives may also be offered."
We need to preserve that. We'll put in
. Now Schedule: hybrid schedule and location: "Location: This person will be working out of our Dallas, TX, OR Houston, TX , OR Raleigh / Durham NC office on a hybrid schedule therefore must reside in one of those areas." Also earlier: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home." Wait there is a conflict: earlier says Remote/Teleworker primarily work from home, later says hybrid schedule in Dallas/Houston/Raleigh-Durham. We need to preserve both. So schedule section should include both statements: remote/teleworker primarily work from home, and hybrid schedule requiring residence in those areas. Thus schedule content: "This role has been designated as ‘Remote/Teleworker’, which means you will primarily work from home. The position is based out of our Dallas, TX, Houston, TX, or Raleigh/Durham, NC office on a hybrid schedule; therefore you must reside in one of those areas." We need to ensure we don't duplicate. Now we must not include boilerplate like EEO, accessibility, fraud alert, etc. Now produce HTML. Structure:
About the role
... combined who we are + job description ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Now craft the content precisely. About the role paragraph: combine who we are and job description. Ensure we don't repeat sentences. Let's write: "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