VP, Engineering

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, equal opportunity, scam warning, application instructions, navigation, cookie, legal. Also remove duplicated lines. Must preserve all substantive information. We need to parse the posting. Let's extract sections: First 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." This is about company culture; could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put that under About the role. Next: "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 also about the role. Then "Key Responsibilities" heading appears in original. Under that we have bullet points (but not formatted as list). We need to convert to

• . The responsibilities listed: 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. We need to output these as list items under a Responsibilities section. Next: "Required Qualifications" heading. Then bullet list: - Bachelor’s degree in Computer Science, Engineering, Information Technology, or a related discipline; Master's degree preferred. - 15+ years of progressive software engineering experience, including executive leadership of large, multi-level engineering organizations. - Proven experience leading engineering leaders, including Directors of Engineering, Engineering Managers, and senior technical leaders. - Demonstrated success building and scaling enterprise platform engineering organizations supporting multiple product teams. - Deep expertise in cloud-native architectures, distributed systems, and modern software engineering practices, with experience delivering solutions on Microsoft Azure. - Experience with enterprise data platforms and technologies such as Azure, Databricks, data integration, and modern data engineering frameworks. - Strong understanding of platform engineering, APIs, data management, AI-enabled platforms, identity, security, and enterprise architecture principles. - Experience implementing DevSecOps, CI/CD, quality engineering, observability, automation, and Site Reliability Engineering (SRE) practices. - Hands-on leader able to build POCs and actively contribute to design, architecture, and whiteboarding sessions. - Exceptional communication, collaboration, and leadership skills. These are qualifications. Then "Preferred Qualifications" heading. Then bullet list: - 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. Then there is a section "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." Then "Engineering Practices ‒ Establish proper engineering practice. ‒ Measure adoption and effectiveness of engineer practices across teams standardizing where appropriate." Then "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." Then "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 maybe sub-sections under Responsibilities? They appear after Preferred Qualifications but before Estimated Hiring Range. They could be considered part of Responsibilities or maybe separate sections like "Individual Talent Management", "Engineering Practices", "Technical Expertise", "Shared Coordinate". However the instruction says we should prefer a few substantive sections over many thin ones. We could incorporate these bullet points into Responsibilities as additional items, or we could create separate sections if they are substantive. But we have limited allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "Individual Talent Management" etc. So we should fold them into Responsibilities (or maybe Qualifications). They seem like responsibilities/duties. So we can add them as list items under Responsibilities. Then "Estimated Hiring Range This position is also incentive eligible." This is about Pay. It says "Estimated Hiring Range This position is also incentive eligible." No actual numbers given. It's vague; we should not create a Pay section unless posting actually states them. It says "Estimated Hiring Range" but no range given; it's not specific. According to rule: 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. Since no actual numbers, we should not create Pay section. However we could note that it's incentive eligible but no range; still filler. Better to omit Pay section. Next: "Vizient has a comprehensive benefits plan! Please view our benefits here: http://www.vizientinc.com/about-us/careers". This mentions benefits but refers to external link; no specifics. According to rule, we should not create Benefits section unless posting actually states them. It just says they have a comprehensive benefits plan and link. No specifics. So we should not create Benefits section. EEO etc boilerplate to remove. Thus we have sections: About the role (culture intro), Responsibilities (all duties), Qualifications (maybe combine Required and Preferred?), Skills? The instruction includes Skills heading but we may not have explicit skills separate from qualifications. Could we treat Required Qualifications as Qualifications, and Preferred Qualifications as also Qualifications? Or we could split into Requirements and Qualifications? The headings list includes Requirements and Qualifications separate. Usually Requirements = mandatory, Qualifications = preferred? But we have both Required and Preferred. We could map Required Qualifications to Requirements section, and Preferred Qualifications to Qualifications section. Or we could combine. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use both Requirements and Qualifications. Let's assign: - Requirements: Required Qualifications (the mandatory ones) - Qualifications: Preferred Qualifications (the preferred ones) Skills: maybe we could extract skills from responsibilities? But we don't have explicit skills list; we could skip Skills section if no specific content. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications. We must not include empty sections. Now we need to format. About the role: combine the introductory paragraphs (first two paragraphs) into

  . Possibly also include the sentence about seeking VP Engineering? That is part of role description. We'll include all descriptive paragraphs before Key Responsibilities. Let's extract: Paragraph 1: "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." Paragraph 2: "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" We can combine into one

  or multiple

  . Use

  for prose. Now Responsibilities: we need to list all duties from Key Responsibilities plus the extra bullet-like items after Preferred Qualifications (Individual Talent Management, Engineering Practices, Technical Expertise, Shared Coordinate). We'll convert each bullet to

  . Ensure we preserve all content. Let's list them: From 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 the extra items: 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