Delivery Leader
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We need to parse the job posting. Key sections: - About the role: The description at top: "We are seeking an experienced Delivery Leader to oversee the development, maintenance, testing and implementation of a large-scale healthcare system supporting State Medicaid clients. This role provides technical and delivery leadership across multiple teams, ensuring high-quality, compliant solutions for an established Commercial Off-The-Shelf (COTS) healthcare product. The Delivery Leader will partner closely with managers, developers, testers and infrastructure persons as well as business stakeholders to ensure consistent delivery, effective processes, and successful onboarding of new State Medicaid customers. This is a fully remote position. Requires 10% travel." That's prose, can be
. - Responsibilities: There's "Essential Duties and Responsibilities:" then bullet list? Actually they list paragraphs. Then later "Key Responsibilities" with subheadings: Delivery Leadership, Process & Quality Oversight, Team & Stakeholder Collaboration, Customer Implementation & Support, Compliance & Governance. Those are responsibilities. So we can combine into a
- list of duties. We need to preserve all substantive info, not invent. Should we break into separate
- for each bullet? The text includes paragraphs under each subheading. We can create list items summarizing each duty but must not invent or summarize away detail. However we can keep the prose as is inside
- . Probably better to output each duty as a
- containing the paragraph(s). We'll need to extract the duties.
Let's extract duties from "Essential Duties and Responsibilities:" paragraph:
"Provide strategic direction and guidance to the software engineers within the IT Applications Development team in support of application design, software development, and software integration.
Define the key priorities in pursuit of the vision and goals associated with the Software Engineering practice.
Ensure Software Engineering staff are following best practices around application design, software development, and software integration throughout the system development lifecycle.
Leads and directs the work of other employees and has responsibility for personnel actions including; hiring, performance management, and termination.
Provide leadership and direction to staff for completeness of application design, software engineering, and software integration.
Work toward the improvement of the software life cycle time by increasing the quality of requirements and reducing the amount of time spent in the application design, development, and integration phases.
Manage the Software Engineering staff as a shared service to support multiple projects.
Ensure that the Software Engineers have the appropriate tools, skills, and training to support the project needs.
Manage geographically distributed staff to maximize staff utilization.
Work closely with delivery managers and product managers to support product delivery and enhancements.
Drive all aspects of engineering recruiting including but not limited to; attracting great talent and retaining a highly skilled, proficient engineering team."
Then after that, there is "Key Responsibilities" with subheadings and paragraphs. Those are also responsibilities. We could combine them as additional list items.
Let's extract each subheading's paragraph:
Delivery Leadership:
"Oversee the development, maintenance, and enhancement of a COTS healthcare system serving Medicaid clients
Ensure delivery of high-quality, reliable, and compliant solutions, including enhancements, fixes, and customer-specific configurations
Provide direction and oversight for multiple teams through collaboration with other managers"
Process & Quality Oversight:
"Define, implement, and maintain development processes, procedures, and delivery standards
Ensure adherence to SDLC, change management, release management, and quality assurance processes
Review solution designs and deliverables to ensure technical soundness, scalability, and maintainability
Drive continuous improvement in engineering practices and delivery outcomes"
Team & Stakeholder Collaboration:
"Work closely with technical managers, architects, developers, QA teams, and operations teams
Serve as a key liaison between technical teams and business stakeholders
Communicate clearly with customers and internal stakeholders at all levels, including executive leadership
Support issue resolution and prioritization across development and support activities"
Customer Implementation & Support:
"Provide oversight for implementation of the COTS product for new and existing State Medicaid customers
Ensure consistent implementation approaches while supporting necessary configuration or customization
Support post-implementation stabilization and ongoing system maintenance
Balance enhancements for existing clients with onboarding of new customers"
Compliance & Governance:
"Ensure solutions meet healthcare, Medicaid, security, and regulatory requirements
Support audits, reviews, and compliance efforts as required
Promote documentation, traceability, and operational readiness"
We can combine all these as list items.
Now Requirements: There's "Minimum Requirements Bachelor's degree in relevant field of study and 7+ years of relevant professional experience required, or equivalent combination of education and experience."
Then "Required Qualifications - Demonstrated ability to ensure delivery quality, process compliance, and predictable outcomes Bachelor’s degree in computer science, Information Systems, or a related field (or equivalent experience) 10+ years of experience in software development with 5+ years in technical leadership or management roles Proven experience overseeing delivery for enterprise healthcare systems, preferably Medicaid-related Experience managing and supporting teams working on COTS products Strong understanding of:Software development lifecycle (SDLC)Release and change managementApplication maintenance and defect remediation"
Then "Preferred Qualifications Experience supporting state Medicaid agencies or healthcare payers Familiarity with provider enrollment, eligibility, claims, or care management systems Background collaborating with distributed or multi-vendor teams"
We need sections: Requirements, Qualifications, Skills maybe.
We can treat "Minimum Requirements" as Requirements section. "Required Qualifications" and "Preferred Qualifications" could go under Qualifications (maybe separate sub-sections but we only have heading Qualifications). We'll put all qualification statements in a
- .
Skills: The "Strong understanding of:Software development lifecycle (SDLC)Release and change managementApplication maintenance and defect remediation" could be considered skills. Also maybe other skills like "Demonstrated ability to ensure delivery quality, process compliance, and predictable outcomes". We'll put skills as list.
Benefits: The posting includes a "Why Join Maximus?" section with bullet points (emoji). Those are benefits. We need to include Benefits section only if posting actually states them. Yes, they list many benefits. So we should create Benefits section with list items.
Pay: The posting includes Minimum Salary $165,000.00 Maximum Salary $165,000.00. So we have Pay section with that info. Also there is Pay Transparency paragraph but that's boilerplate? It's about compensation but not specific numbers. We should include Pay section with the salary range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated (min and max). So include Pay.
Schedule: Not mentioned besides "This is a fully remote position. Requires 10% travel." That's not a schedule (like full-time, part-time). No explicit schedule. So we should not create Schedule section.
Now we need to output HTML fragment with headings
and content. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO Statement, Pay Transparency (maybe keep only if not boilerplate? It's generic; but we already have Pay section with salary; the Pay Transparency paragraph is generic boilerplate; we should remove it. Also Accommodations paragraph is boilerplate; remove. Also remove "Why Join Maximus?" heading? We'll keep benefits under Benefits heading; we can drop the "Why Join Maximus?" heading. We need to preserve all substantive information: the benefits list with emojis and descriptions. We'll keep them as list items. Now craft HTML. Structure:
About the role
We are seeking an experienced Delivery Leader to oversee the development, maintenance, testing and implementation of a large-scale healthcare system supporting State Medicaid clients. This role provides technical and delivery leadership across multiple teams, ensuring high-quality, compliant solutions for an established Commercial Off-The-Shelf (COTS) healthcare product. The Delivery Leader will partner closely with managers, developers, testers and infrastructure persons as well as business stakeholders to ensure consistent delivery, effective processes, and successful onboarding of new State Medicaid customers. This is a fully remote position. Requires 10% travel.
Responsibilities
- Provide strategic direction and guidance to the software engineers within the IT Applications Development team in support of application design, software development, and software integration.
- Define the key priorities in pursuit of the vision and goals associated with the Software Engineering practice.
- Ensure Software Engineering staff are following best practices around application design, software development, and software integration throughout the system development lifecycle.
- Leads and directs the work of other employees and has responsibility for personnel actions including; hiring, performance management, and termination.
- Provide leadership and direction to staff for completeness of application design, software engineering, and software integration.
- Work toward the improvement of the software life cycle time by increasing the quality of requirements and reducing the amount of time spent in the application design, development, and integration phases.
- Manage the Software Engineering staff as a shared service to support multiple projects.
- Ensure that the Software Engineers have the appropriate tools, skills, and training to support the project needs.
- Manage geographically distributed staff to maximize staff utilization.
- Work closely with delivery managers and product managers to support product delivery and enhancements.
- Drive all aspects of engineering recruiting including but not limited to; attracting great talent and retaining a highly skilled, proficient engineering team.
- Oversee the development, maintenance, and enhancement of a COTS healthcare system serving Medicaid clients.
- Ensure delivery of high-quality, reliable, and compliant solutions, including enhancements, fixes, and customer-specific configurations.
- Provide direction and oversight for multiple teams through collaboration with other managers.
- Define, implement, and maintain development processes, procedures, and delivery standards.
- Ensure adherence to SDLC, change management, release management, and quality assurance processes.
- Review solution designs and deliverables to ensure technical soundness, scalability, and maintainability.
- Drive continuous improvement in engineering practices and delivery outcomes.
- Work closely with technical managers, architects, developers, QA teams, and operations teams.
- Serve as a key liaison between technical teams and business stakeholders.
- Communicate clearly with customers and internal stakeholders at all levels, including executive leadership.
- Support issue resolution and prioritization across development and support activities.
- Provide oversight for implementation of the COTS product for new and existing State Medicaid customers.
- Ensure consistent implementation approaches while supporting necessary configuration or customization.
- Support post-implementation stabilization and ongoing system maintenance.
- Balance enhancements for existing clients with onboarding of new customers.
- Ensure solutions meet healthcare, Medicaid, security, and regulatory requirements.
- Support audits, reviews, and compliance efforts as required.
- Promote documentation, traceability, and operational readiness.
Requirements
- Bachelor's degree in relevant field of study and 7+ years of relevant professional experience required, or equivalent combination of education and experience.
Qualifications
- Demonstrated ability to ensure delivery quality, process compliance, and predictable outcomes.
- Bachelor’s degree in computer science, Information Systems, or a related field (or equivalent experience).
- 10+ years of experience in software development with 5+ years in technical leadership or management roles.
- Proven experience overseeing delivery for enterprise healthcare systems, preferably Medicaid-related.
- Experience managing and supporting teams working on COTS products.
- Strong understanding of software development lifecycle (SDLC), release and change management, application maintenance and defect remediation.
- .
Skills: The "Strong understanding of:Software development lifecycle (SDLC)Release and change managementApplication maintenance and defect remediation" could be considered skills. Also maybe other skills like "Demonstrated ability to ensure delivery quality, process compliance, and predictable outcomes". We'll put skills as list.
Benefits: The posting includes a "Why Join Maximus?" section with bullet points (emoji). Those are benefits. We need to include Benefits section only if posting actually states them. Yes, they list many benefits. So we should create Benefits section with list items.
Pay: The posting includes Minimum Salary $165,000.00 Maximum Salary $165,000.00. So we have Pay section with that info. Also there is Pay Transparency paragraph but that's boilerplate? It's about compensation but not specific numbers. We should include Pay section with the salary range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated (min and max). So include Pay.
Schedule: Not mentioned besides "This is a fully remote position. Requires 10% travel." That's not a schedule (like full-time, part-time). No explicit schedule. So we should not create Schedule section.
Now we need to output HTML fragment with headings