VP, Engineering
- for any list of duties/requirements/benefits. So we can flatten them? Probably each bullet as
- . Could group under headings? But only allowed headings are the specified ones; we cannot add custom headings like Organizational Leadership. So we just list all responsibilities as
- items under a
- under
- .
- Qualifications: maybe "Preferred Qualifications". That includes bullet points: Experience in healthcare..., Experience building enterprise platforms..., Familiarity with healthcare interoperability standards..., Experience leading geographically distributed engineering organizations. Also the later bullet points (Individual Talent Management etc.) could be considered qualifications? But they are more like responsibilities/skills. However we already have a Skills section; we could put those under Skills.
- Skills: maybe we can extract skills from the text: communication, collaboration, leadership, etc. But we already have many skill-like items in Required Qualifications (Exceptional communication, collaboration, and leadership skills). Also from Preferred Qualifications we have healthcare experience, etc. Could also list technical skills: cloud-native, Azure, DevSecOps, CI/CD, etc. But we need to avoid duplication and only include sections if there is real specific content. We could create a Skills section with bullet list of skills: communication, collaboration, leadership, healthcare domain knowledge, FHIR/HL7, Azure, Databricks, DevSecOps, CI/CD, quality engineering, observability, automation, SRE, API, data management, AI-enabled platforms, identity, security, enterprise architecture, etc. However we must not invent content not present. The posting does mention many of those. So we can extract.
- Benefits: The posting says: "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 specific details. According to rule: never create Benefits section unless posting actually states them. It does state there is a comprehensive benefits plan and provides a link. That is specific enough? It says "comprehensive benefits plan". That's a statement but not detailed. The rule 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 does state benefits exist and gives a link. That's not filler like "varies". It's a statement that there is a benefits plan. So we can include Benefits section with a
that says "Vizient offers a comprehensive benefits plan. See details at: http://www.vizientinc.com/about-us/careers". That preserves the info. - Pay: The posting includes "Estimated Hiring Range This position is also incentive eligible." That's a statement about pay range but not actual numbers. It says "Estimated Hiring Range" but no numbers. That's like placeholder? It's not a specific number. The rule says never create Pay section unless posting actually states them. It does state "Estimated Hiring Range" but no numbers; that could be considered not specific. Might be considered filler? It says "Estimated Hiring Range This position is also incentive eligible." That's vague. I'd argue it's not specific enough; better to omit Pay section. - Schedule: No mention of schedule. So omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Now we need to output HTML fragment with
for each section heading, then content:
for prose,
- for lists.
We must not repeat job title as heading. So no heading for Vice President, Engineering.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract all substantive info precisely.
First, About the role paragraph: We have two sentences? Actually: "We are seeking a Vice President, Engineering to lead the engineering organization responsible for the enterprise platforms that power our next-generation healthcare technology products. This leader will oversee a large engineering organization, drive engineering excellence and delivering secure, scalable, cloud-native platforms that enable product teams across the enterprise. Working in close partnership with internal stakeholders, this executive will define engineering strategy, shape platform investments, and foster a culture of technical excellence while collaborating across Architecture, Technology Delivery, Security, and Product organizations". That's three sentences. We'll put as
. Now Responsibilities: We need to list all duty bullets. Let's gather from Key Responsibilities and later bullet points. From Key Responsibilities: Organizational Leadership: - Lead and develop a high-performing engineering organization, fostering a culture of accountability, innovation, collaboration, and continuous improvement. - Recruit, retain, and develop exceptional engineering talent while building leadership capability through coaching, succession planning, and performance management. - Build organizational capacity by balancing full-time and contingent talent to meet evolving business priorities. Platform Engineering: - Define and execute the engineering strategy for enterprise platform capabilities that enable secure, scalable, cloud-native solutions supporting data, AI, security, identity, and shared services. - Deliver reusable platform capabilities that accelerate product delivery, improve developer productivity, and enable enterprise-wide adoption. - Ensure engineering teams deliver reliable, high-quality software with operational excellence and measurable business outcomes. Engineering Excellence & Enterprise Collaboration: - Partner with Platform Product Management in an engineering/product leadership dyad to define platform strategy, investment priorities, and roadmaps. - Establish modern engineering practices—including DevSecOps, quality engineering, automation, observability, and AI-enabled software engineering—and measure their adoption and effectiveness across teams. - Foster a culture of continuous learning, technical excellence, and innovation while evaluating emerging technologies that create business value. Now later bullet points under "Individual Talent Management", "Engineering Practices", "Technical Expertise", "Shared Coordinate...". These are also duties/responsibilities. Let's list them: Individual Talent Management: - Recruit, hire, and onboard top engineering talent. - Develop and implement training and development programs to enhance the skills and capabilities of the engineering team. - Foster a positive and inclusive work environment that promotes delivery, solid engineering practices and champions the Vizient value. - Supplement FTE engineers with effective contingent staffing partnerships balancing cost and performance. Engineering Practices: - Establish proper engineering practice. - Measure adoption and effectiveness of engineer practices across teams standardizing where appropriate. Technical Expertise: - Provide technical leadership and guidance to the engineering team. - Stay up-to-date with industry trends, best practices, and emerging technologies. - Ensure that the engineering team is using the most effective and efficient tools, technologies, and processes. - Foster a culture of innovation and continuous improvement within the engineering department. Shared Coordinate with Technology Delivery, Technology Practices, Enterprise Architecture, Solutions: - Partner with Technology Delivery and other Technology Practices to staff and
- for lists.
We must not repeat job title as heading. So no heading for Vice President, Engineering.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract all substantive info precisely.
First, About the role paragraph: We have two sentences? Actually: "We are seeking a Vice President, Engineering to lead the engineering organization responsible for the enterprise platforms that power our next-generation healthcare technology products. This leader will oversee a large engineering organization, drive engineering excellence and delivering secure, scalable, cloud-native platforms that enable product teams across the enterprise. Working in close partnership with internal stakeholders, this executive will define engineering strategy, shape platform investments, and foster a culture of technical excellence while collaborating across Architecture, Technology Delivery, Security, and Product organizations". That's three sentences. We'll put as
Responsibilities
. Must preserve all substantive info. So we need to capture each bullet. Let's list them: Organizational Leadership: - Lead and develop a high-performing engineering organization, fostering a culture of accountability, innovation, collaboration, and continuous improvement. - Recruit, retain, and develop exceptional engineering talent while building leadership capability through coaching, succession planning, and performance management. - Build organizational capacity by balancing full-time and contingent talent to meet evolving business priorities. Platform Engineering: - Define and execute the engineering strategy for enterprise platform capabilities that enable secure, scalable, cloud-native solutions supporting data, AI, security, identity, and shared services. - Deliver reusable platform capabilities that accelerate product delivery, improve developer productivity, and enable enterprise-wide adoption. - Ensure engineering teams deliver reliable, high-quality software with operational excellence and measurable business outcomes. Engineering Excellence & Enterprise Collaboration: - Partner with Platform Product Management in an engineering/product leadership dyad to define platform strategy, investment priorities, and roadmaps. - Establish modern engineering practices—including DevSecOps, quality engineering, automation, observability, and AI-enabled software engineering—and measure their adoption and effectiveness across teams. - Foster a culture of continuous learning, technical excellence, and innovation while evaluating emerging technologies that create business value. Also there is later a section "Individual Talent Management", "Engineering Practices", "Technical Expertise", "Shared Coordinate with Technology Delivery...". Those seem like more detailed responsibilities/qualifications? They appear after "Preferred Qualifications" maybe? Actually after "Preferred Qualifications" there is a block: Preferred Qualifications Experience in healthcare, healthcare technology, or other highly regulated industries. Experience building enterprise platforms for Data, AI, Identity, and shared developer capabilities Familiarity with healthcare interoperability standards such as FHIR or HL7. Experience leading geographically distributed engineering organizations. Individual Talent Management ‒ Recruit, hire, and onboard top engineering talent. ‒ Develop and implement training and development programs to enhance the skills and capabilities of the engineering team. ‒ Foster a positive and inclusive work environment that promotes delivery, solid engineering practices and champions the Vizient value. ‒ Supplement FTE engineers with effective contingent staffing partnerships balancing cost and performance. Engineering Practices ‒ Establish proper engineering practice. ‒ Measure adoption and effectiveness of engineer practices across teams standardizing where appropriate. Technical Expertise ‒ Provide technical leadership and guidance to the engineering team. ‒ Stay up-to-date with industry trends, best practices, and emerging technologies. ‒ Ensure that the engineering team is using the most effective and efficient tools, technologies, and processes. ‒ Foster a culture of innovation and continuous improvement within the engineering department. Shared Coordinate with Technology Delivery, Technology Practices, Enterprise Architecture, Solutions ‒ Partner with Technology Delivery and other Technology Practices to staff and manage high performing delivery teams while balancing cost and demand. ‒ Partner with EA and Solutions to determine the right solution design for our products, applications and services. ‒ Partner with Technology team to develop and operate a thorough 360 feedback program that ensures each employee is measured equally on delivery, practices and values. These seem like additional responsibilities or qualifications but they are under Preferred Qualifications? Actually they appear after Preferred Qualifications bullet list, but they are formatted with dash and maybe they are more responsibilities. However the instruction: include a section ONLY when the posting has real, specific content for it. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these sections. - About the role: we have description. - Responsibilities: we have the Key Responsibilities bullet points (the three categories). Also the later bullet points (Individual Talent Management etc.) could also be responsibilities. But we can include them as responsibilities as well. However we must not invent sections; we can put all duty-like bullets under Responsibilities. - Requirements: likely the "Required Qualifications" section. That includes bullet points: Bachelor’s degree..., Master's degree preferred. 15+ years..., Proven experience..., Demonstrated success..., Deep expertise..., Experience with enterprise data platforms..., Strong understanding..., Experience implementing..., Hands-on leader..., Exceptional communication... We should list each as - .
- Qualifications: maybe "Preferred Qualifications". That includes bullet points: Experience in healthcare..., Experience building enterprise platforms..., Familiarity with healthcare interoperability standards..., Experience leading geographically distributed engineering organizations. Also the later bullet points (Individual Talent Management etc.) could be considered qualifications? But they are more like responsibilities/skills. However we already have a Skills section; we could put those under Skills.
- Skills: maybe we can extract skills from the text: communication, collaboration, leadership, etc. But we already have many skill-like items in Required Qualifications (Exceptional communication, collaboration, and leadership skills). Also from Preferred Qualifications we have healthcare experience, etc. Could also list technical skills: cloud-native, Azure, DevSecOps, CI/CD, etc. But we need to avoid duplication and only include sections if there is real specific content. We could create a Skills section with bullet list of skills: communication, collaboration, leadership, healthcare domain knowledge, FHIR/HL7, Azure, Databricks, DevSecOps, CI/CD, quality engineering, observability, automation, SRE, API, data management, AI-enabled platforms, identity, security, enterprise architecture, etc. However we must not invent content not present. The posting does mention many of those. So we can extract.
- Benefits: The posting says: "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 specific details. According to rule: never create Benefits section unless posting actually states them. It does state there is a comprehensive benefits plan and provides a link. That is specific enough? It says "comprehensive benefits plan". That's a statement but not detailed. The rule 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 does state benefits exist and gives a link. That's not filler like "varies". It's a statement that there is a benefits plan. So we can include Benefits section with a