Product Director, Vizient Reserve
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 posting.
Content:
- Opening paragraph: "When you’re the best, we’re the best. We instill an environment where employees feel engaged, satisfied and able to contribute their unique skills and talents while living and working as their authentic selves. We provide extensive opportunities for personal and professional development, building both employee competence and organizational capability to fuel exceptional performance through an inclusive environment both now and in the future."
- Then "Summary In this role, you will lead product strategy, vision, development, and lifecycle management for Vizient Reserve and interconnected product solutions. You will translate client needs, market insights, and business strategies into product priorities, roadmaps, and enhancements that deliver differentiated value. You will partner with leadership, technology, sales, marketing, and cross-functional teams to bring new capabilities to market, optimize existing solutions, and ensure alignment with broader portfolio and organizational strategies."
- Then "Responsibilities" bullet list (actually sentences separated by periods). We need to convert each bullet into
- . The list items:
- Lead product strategy, vision, roadmaps, and lifecycle management across highly complex and interconnected products while identifying portfolio integration opportunities aligned with business and solution strategies.
- Conduct client and stakeholder discovery to understand business needs, user experiences, and market opportunities and translate insights into product requirements, priorities, personas, journeys, and use cases.
- Develop product value propositions, positioning, and portfolio plans in partnership with sales and marketing to support client retention, acquisition, and market differentiation.
- Lead product development and enhancement planning by defining business requirements, prioritizing features, evaluating business value, and coordinating with application development and agile teams.
- Manage product launches and releases by developing business release plans and coordinating resources and activities across technology, marketing, sales, delivery, and other cross-functional teams.
- Lead business discovery, concept testing, user acceptance testing, and product validation activities to ensure solutions address client needs and deliver intended business outcomes.
- Assess product and portfolio performance using market research, competitive intelligence, client feedback, win/loss analysis, and performance trends to identify opportunities for improvement and innovation.
- Develop business cases and recommendations for product investments, build-buy-partner decisions, third-party relationships, and short-, mid-, and long-term product enhancements.
- Serve as a primary product contact for internal clients, providing product demonstrations, communications, education, sales support, RFP content, and guidance across assigned solutions.
- Partner with technology and business teams to monitor product health, development spend, resource requirements, and priorities while promoting consistent product management practices across teams.
- Then "Qualifications" bullet list (actually sentences). Items:
- Relevant degree preferred.
- 7 or more years of relevant experience required.
- Experience leading product strategy, product management, or development of complex technology-enabled products required.
- Demonstrated ability to translate client, market, and business needs into product strategies, roadmaps, requirements, and actionable priorities.
- Experience partnering with application development, technology, agile, sales, marketing, and other cross-functional teams.
- Strong analytical and strategic thinking skills with experience using client insights, market research, and performance data to inform product decisions.
- Experience developing business cases, product value propositions, go-to-market plans, and product launch strategies.
- Excellent verbal, written, presentation, and executive communication skills.
- Position on -site hybrid- 3 days. Locations, Irving TX, Centennial CO, Chicago IL, and Edina MN.
- Estimated Hiring Range At Vizient, we consider skills, experience, and organizational needs in our compensation approach. Geographic factors may adjust the range estimate and hires typically fall below the top range. Compensation decisions are tailored to individual circumstances. The current salary range for this role is $102,400.00 to $179,000.00. This position is also incentive eligible.
- Vizient has a comprehensive benefits plan! Please view our benefits here: http://www.vizientinc.com/about-us/careers
- Then EEO boilerplate etc to be removed.
We need to decide sections: We have an introductory paragraph (maybe "About the role" or we could just put it as a
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require we must have headings for everything, but we should use headings for sections when we have content. The intro could be under "About the role" or we could just leave as a
without heading? The examples include About the role as a possible heading. I'd put
About the role
then the intro paragraph.
Then we have Summary: Could be part of About the role or separate. The summary is basically the role description. Could combine with About the role. But we need to avoid thin sections. Perhaps we combine the intro and summary into one About the role section.
Then Responsibilities: Responsibilities
with - ... items.
Then Qualifications:
Qualifications
with - ... items.
Then Pay: The posting includes salary range and incentive eligible. So we should include a Pay section with that info. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range and incentive eligible. So we can have
Pay
with a containing that info.
Benefits: The posting mentions "Vizient has a comprehensive benefits plan! Please view our benefits here: http://www.vizientinc.com/about-us/careers". That's a statement about benefits but not detailed. It's not a list of benefits. Should we include a Benefits section? The rule says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The benefits statement is vague, just a link. It's not specific benefits. Might be considered filler. Safer to omit Benefits section.
Schedule: The posting includes "Position on -site hybrid- 3 days. Locations, Irving TX, Centennial CO, Chicago IL, and Edina MN." That's schedule/hybrid info and locations. Could be considered Schedule section? The rule says include Schedule section only if posting actually states them. It does state hybrid 3 days and locations. So we could include a Schedule section with that info. However, the location info could also be considered metadata. But we can include Schedule.
We need to avoid duplication: The location line appears also in Qualifications list as an item. Actually the Qualifications list includes "Position on -site hybrid- 3 days. Locations, Irving TX, Centennial CO, Chicago IL, and Edina MN." That's part of qualifications? It's more about work arrangement. Might be better to move that to Schedule section and remove from Qualifications list to avoid duplication. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove it from Qualifications, we are not losing info because we still include it in Schedule. That's okay as long as we keep the info somewhere. But we need to ensure we don't duplicate. We could keep it in Qualifications and also have Schedule? That would duplicate. Better to move it to Schedule and remove from Qualifications list. However, the Qualifications list originally includes that as a bullet; if we remove it, we are altering the list. But we could keep it there and also have Schedule; duplication is not ideal but maybe acceptable? The instruction says preserve ALL substantive information; does not forbid duplication, but better to avoid duplication. I'd move it to Schedule and drop from Qualifications.
Similarly, the salary range and incentive eligible could be placed in Pay section; we could also keep it in Qualifications list but better to move to Pay and remove from Qualifications.
Thus Qualifications list will contain the remaining items: relevant degree preferred, 7+ years experience, experience leading product strategy..., demonstrated ability..., experience partnering..., strong analytical..., experience developing business cases..., excellent communication skills.
Now we need to format.
Let's craft HTML:
About the role
When you’re the best, we’re the best. We instill an environment where employees feel engaged, satisfied and able to contribute their unique skills and talents while living and working as their authentic selves. We provide extensive opportunities for personal and professional development, building both employee competence and organizational capability to fuel exceptional performance through an inclusive environment both now and in the future. Summary In this role, you will lead product strategy, vision, development, and lifecycle management for Vizient Reserve and interconnected product solutions. You will translate client needs, market insights, and business strategies into product priorities, roadmaps, and enhancements that deliver differentiated value. You will partner with leadership, technology, sales, marketing, and cross-functional teams to bring new capabilities to market, optimize existing solutions, and ensure alignment with broader portfolio and organizational strategies.
Then Responsibilities:
Responsibilities
- Lead product strategy, vision, roadmaps, and lifecycle management across highly complex and interconnected products while identifying portfolio integration opportunities aligned with business and solution strategies.
- Conduct client and stakeholder discovery to understand business needs, user experiences, and market opportunities and translate insights into product requirements, priorities, personas, journeys, and use cases.
- Develop product value propositions, positioning, and portfolio plans in partnership with sales and marketing to support client retention, acquisition, and market differentiation.
- Lead product development and enhancement planning by defining business requirements, prioritizing features, evaluating business value, and coordinating with application development and agile teams.
- Manage product launches and releases by developing business release plans and coordinating resources and activities across technology, marketing, sales, delivery, and other cross-functional teams.
- Lead business discovery, concept testing, user acceptance testing, and product validation activities to ensure solutions address client needs and deliver intended business outcomes.
- Assess product and portfolio performance using market research, competitive intelligence, client feedback, win/loss analysis, and performance trends to identify opportunities for improvement and innovation.
- Develop business cases and recommendations for product investments, build-buy-partner decisions, third-party relationships, and short-, mid-, and long-term product enhancements.
- Serve as a primary product contact for internal clients, providing product demonstrations, communications, education, sales support, RFP content, and guidance across assigned solutions.
- Partner with technology and business teams to monitor product health, development spend, resource requirements, and priorities while promoting consistent product management practices across teams.
Qualifications:
Qualifications
- Relevant degree preferred.
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 posting. Content: - Opening paragraph: "When you’re the best, we’re the best. We instill an environment where employees feel engaged, satisfied and able to contribute their unique skills and talents while living and working as their authentic selves. We provide extensive opportunities for personal and professional development, building both employee competence and organizational capability to fuel exceptional performance through an inclusive environment both now and in the future." - Then "Summary In this role, you will lead product strategy, vision, development, and lifecycle management for Vizient Reserve and interconnected product solutions. You will translate client needs, market insights, and business strategies into product priorities, roadmaps, and enhancements that deliver differentiated value. You will partner with leadership, technology, sales, marketing, and cross-functional teams to bring new capabilities to market, optimize existing solutions, and ensure alignment with broader portfolio and organizational strategies." - Then "Responsibilities" bullet list (actually sentences separated by periods). We need to convert each bullet into
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require we must have headings for everything, but we should use headings for sections when we have content. The intro could be under "About the role" or we could just leave as a
without heading? The examples include About the role as a possible heading. I'd put
About the role
then the intro paragraph. Then we have Summary: Could be part of About the role or separate. The summary is basically the role description. Could combine with About the role. But we need to avoid thin sections. Perhaps we combine the intro and summary into one About the role section. Then Responsibilities:Responsibilities
with- ... items.
Then Qualifications:
Qualifications
with- ... items.
Then Pay: The posting includes salary range and incentive eligible. So we should include a Pay section with that info. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range and incentive eligible. So we can have
Pay
with acontaining that info. Benefits: The posting mentions "Vizient has a comprehensive benefits plan! Please view our benefits here: http://www.vizientinc.com/about-us/careers". That's a statement about benefits but not detailed. It's not a list of benefits. Should we include a Benefits section? The rule says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The benefits statement is vague, just a link. It's not specific benefits. Might be considered filler. Safer to omit Benefits section. Schedule: The posting includes "Position on -site hybrid- 3 days. Locations, Irving TX, Centennial CO, Chicago IL, and Edina MN." That's schedule/hybrid info and locations. Could be considered Schedule section? The rule says include Schedule section only if posting actually states them. It does state hybrid 3 days and locations. So we could include a Schedule section with that info. However, the location info could also be considered metadata. But we can include Schedule. We need to avoid duplication: The location line appears also in Qualifications list as an item. Actually the Qualifications list includes "Position on -site hybrid- 3 days. Locations, Irving TX, Centennial CO, Chicago IL, and Edina MN." That's part of qualifications? It's more about work arrangement. Might be better to move that to Schedule section and remove from Qualifications list to avoid duplication. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove it from Qualifications, we are not losing info because we still include it in Schedule. That's okay as long as we keep the info somewhere. But we need to ensure we don't duplicate. We could keep it in Qualifications and also have Schedule? That would duplicate. Better to move it to Schedule and remove from Qualifications list. However, the Qualifications list originally includes that as a bullet; if we remove it, we are altering the list. But we could keep it there and also have Schedule; duplication is not ideal but maybe acceptable? The instruction says preserve ALL substantive information; does not forbid duplication, but better to avoid duplication. I'd move it to Schedule and drop from Qualifications. Similarly, the salary range and incentive eligible could be placed in Pay section; we could also keep it in Qualifications list but better to move to Pay and remove from Qualifications. Thus Qualifications list will contain the remaining items: relevant degree preferred, 7+ years experience, experience leading product strategy..., demonstrated ability..., experience partnering..., strong analytical..., experience developing business cases..., excellent communication skills. Now we need to format. Let's craft HTML:
About the role
When you’re the best, we’re the best. We instill an environment where employees feel engaged, satisfied and able to contribute their unique skills and talents while living and working as their authentic selves. We provide extensive opportunities for personal and professional development, building both employee competence and organizational capability to fuel exceptional performance through an inclusive environment both now and in the future. Summary In this role, you will lead product strategy, vision, development, and lifecycle management for Vizient Reserve and interconnected product solutions. You will translate client needs, market insights, and business strategies into product priorities, roadmaps, and enhancements that deliver differentiated value. You will partner with leadership, technology, sales, marketing, and cross-functional teams to bring new capabilities to market, optimize existing solutions, and ensure alignment with broader portfolio and organizational strategies.
Then Responsibilities:Responsibilities
- Lead product strategy, vision, roadmaps, and lifecycle management across highly complex and interconnected products while identifying portfolio integration opportunities aligned with business and solution strategies.
- Conduct client and stakeholder discovery to understand business needs, user experiences, and market opportunities and translate insights into product requirements, priorities, personas, journeys, and use cases.
- Develop product value propositions, positioning, and portfolio plans in partnership with sales and marketing to support client retention, acquisition, and market differentiation.
- Lead product development and enhancement planning by defining business requirements, prioritizing features, evaluating business value, and coordinating with application development and agile teams.
- Manage product launches and releases by developing business release plans and coordinating resources and activities across technology, marketing, sales, delivery, and other cross-functional teams.
- Lead business discovery, concept testing, user acceptance testing, and product validation activities to ensure solutions address client needs and deliver intended business outcomes.
- Assess product and portfolio performance using market research, competitive intelligence, client feedback, win/loss analysis, and performance trends to identify opportunities for improvement and innovation.
- Develop business cases and recommendations for product investments, build-buy-partner decisions, third-party relationships, and short-, mid-, and long-term product enhancements.
- Serve as a primary product contact for internal clients, providing product demonstrations, communications, education, sales support, RFP content, and guidance across assigned solutions.
- Partner with technology and business teams to monitor product health, development spend, resource requirements, and priorities while promoting consistent product management practices across teams.
Qualifications
- Relevant degree preferred.
- ... items.
Then Pay: The posting includes salary range and incentive eligible. So we should include a Pay section with that info. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range and incentive eligible. So we can have