Solution Delivery Lead

We need to output HTML fragment with sections: About the role? The posting includes summary, responsibilities, qualifications, etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove "What You Should Expect In This Role" maybe part of schedule? It mentions remote, travel, pipeline req, pay range. So we can have sections: About the role (summary), Responsibilities (list of duties), Requirements (education/experience), Qualifications (maybe same as requirements?), Skills (maybe abilities), Benefits (vacation policy, 401k match, health benefits, educational assistance, leadership academies), Pay (pay range), Schedule (remote, travel). Need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. We must preserve all substantive information, not invent or summarize away detail. So we need to include details from posting. Let's parse content: Intro paragraph: "Great companies need great teams...". That's generic fluff; maybe part of About the role? Could be considered summary. Then "Summary Provides Principal-level leadership for complex Provider DDI solution delivery initiatives..." That's summary. Then "Your role in our mission" bullet list of responsibilities (many sentences). We'll turn into

• items. Then "What We're Looking For" list of qualifications: Bachelor's degree..., Seven or more years..., Experience leading..., Demonstrated ability..., Strong understanding..., Proven ability..., Excellent communication..., Success in this role looks like... (maybe outcomes). We'll treat as Requirements/Qualifications/Skills. Then "What You Should Expect In This Role": remote, up to 15% travel annually, pipeline req, pay range, etc. So Schedule: remote, travel. Pay: range. Then "Put your passion to work at Gainwell..." repeats earlier fluff. Then "All salaried, full-time candidates are eligible for our generous, flexible vacation policy, a 401(k) employer match, comprehensive health benefits, and educational assistance. We also have a variety of leadership and technical development academies to help build your skills and capabilities." That's Benefits. Then mission statement etc. Probably ignore. We need to output only HTML fragment, no /. Use

  headings. We must not duplicate lines. Ensure we include all substantive info. Let's craft sections:

  About the role

  Provides Principal-level leadership for complex Provider DDI solution delivery initiatives, with accountability for integrated execution, readiness, quality, and measurable client outcomes. This role orchestrates functional, technical, data, testing, PMO, vendor, client, architecture, and operational workstreams to keep delivery synchronized, technically sound, and aligned to contractual commitments. The Principal Solution Delivery Lead owns the delivery operating model, manages dependencies, risks, tradeoffs, readiness, and executive escalations, and advises the Engagement Lead on delivery strategy, recovery actions, and go-live readiness. For complex Medicaid Enterprise implementations, this role serves as the central orchestration leader and single point of accountability for integrated solution delivery execution.

  Maybe also include the introductory fluff? Could be considered part of About the role but it's generic. Might be okay to include as part of About the role: "Great companies need great teams to propel their operations. Join the group that solves business challenges and enhances the way we work and grow. Working at Gainwell carries its rewards. You’ll have an incredible opportunity to grow your career in a company that values your contributions and puts a premium on work flexibility, learning, and career development." That's substantive? It's fluff but maybe considered part of About the role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. It's not boilerplate; it's company description. So include. Thus About the role paragraph includes that intro plus the summary. Now Responsibilities: list items from "Your role in our mission". Let's extract each sentence as a bullet. - Own and maintain integrated Provider DDI delivery plans, schedules, budgets, milestones, dependencies, and readiness gates for large or highly complex implementation programs. - Lead the integrated delivery operating model and execution cadence, driving accountability, follow-through, and alignment across functional, technical, data, testing, PMO, vendor, client, architecture, and operational workstreams. - Partner with Enterprise Architecture, engineering, domain leads, and delivery managers to validate solution design, confirm technical feasibility, and keep execution aligned with architecture standards and solution intent. - Manage cross-workstream dependencies, handoffs, blockers, sequencing conflicts, delivery tradeoffs, critical path activities, and commitment risks with clear recommendations and recovery options. - Drive closure of cross-workstream risks, issues, assumptions, actions, decisions, change requests, and other governance items that affect integrated delivery outcomes. - Own readiness execution across SIT, UAT, operational readiness, integration validation, deployment preparation, and go-live readiness, ensuring required evidence, deliverables, and team preparedness are in place. - Partner with PMO to maintain delivery rigor, schedule compliance, delivery health assessments, action tracking, governance preparation, financial visibility, and executive-ready reporting. - Partner with and advise the Engagement Lead on delivery strategy, program-wide execution, client communications, executive escalations, and recovery actions for at-risk workstreams or milestones. - Influence stakeholders and gain alignment on scope, objectives, schedules, budgets, dependencies, readiness criteria, decision points, and other critical program commitments. - Lead resource planning, staffing alignment, and coaching of delivery resources to resolve technical, operational, and execution challenges and achieve program goals. - Translate technical delivery risks, architecture impacts, integration concerns, and readiness gaps to clear business implications, decision options, and executive-level recommendations. - Develop and deliver governance materials, executive updates, and presentations that support delivery decisions, client confidence, proposal efforts, and future business opportunities. Now Requirements: maybe combine education and experience. We have "What We're Looking For" bullet list: - Bachelor’s degree or equivalent combination of education and experience; degree in business, information technology, engineering, healthcare administration, or related field preferred. - Seven or more years of progressive program management, principal project management, or solution delivery leadership experience in large-scale implementation environments. - Experience leading complex Provider, Medicaid Enterprise, healthcare, or highly regulated delivery programs across multiple workstreams, vendors, and client stakeholders. - Demonstrated ability to manage integrated plans, dependencies, RAID, change control, governance, readiness gates, executive reporting, and delivery health for complex programs. - Strong understanding of enterprise architecture, solution design, system integration, integration testing, deployment planning, and operational readiness. - Proven ability to influence executive stakeholders, client leaders, vendors, and internal delivery teams, including leadership of delivery recovery, escalation, tradeoff, and readiness decisions. - Excellent communication, facilitation, and stakeholder management skills, with the ability to translate technical topics into business implications and executive-level recommendations. - Success in this role looks like Provider DDI workstreams execute with clear ownership, synchronized plans, and minimal delivery friction. Risks, dependencies, decisions, readiness status, and integration health are visible, actively managed, and clearly communicated. The solution is delivered as designed, tested, operationally ready, and aligned with architecture and contractual commitments. Clients and internal stakeholders have confidence in delivery execution, issue resolution, executive communication, and go-live readiness. That last bullet is more about success criteria; could be part of Responsibilities or Outcomes. Might be better placed under "What Success Looks Like" but we don't have that heading. Could include under Responsibilities or maybe a separate section "Outcomes". But we only allowed headings from list. Could put under Responsibilities as additional bullet? It's describing success, not a duty. Might be okay to include under Responsibilities as it's still substantive. However we might create a separate section "Qualifications" for the success criteria? Not ideal. We could treat the success criteria as part of "What Success Looks Like" but we don't have that heading. Perhaps we can incorporate into Responsibilities as bullet about ensuring those outcomes. But it's more description of success. Might be okay to include under Responsibilities as it's still about role expectations. Alternatively we could create a section "Qualifications" for the success criteria? But qualifications usually about candidate attributes. The success criteria is about role outcomes, not candidate qualifications. So maybe better to put under Responsibilities as it's describing what the role should achieve. Thus we keep that bullet under Responsibilities. Now Skills: we could extract communication, facilitation, stakeholder management, ability to translate technical topics, etc. But those are already in Requirements. Might be redundant. We could create a Skills section for those soft skills. However we must avoid thin sections. Perhaps we combine Requirements and Skills into one section "Requirements". But the instruction says use headings only when posting has real specific content for it. We have content for Requirements (education/experience) and also for Skills (communication etc). Could split. Let's decide: We'll have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Now Requirements: education and experience bullets (first four maybe). Skills: communication, facilitation, stakeholder management, ability to translate technical topics, etc. Also maybe "Strong understanding of enterprise architecture..." could be considered knowledge, but that's more requirement. Might be okay to put under Requirements. Let's allocate: Requirements: - Bachelor’s degree or equivalent combination of education and experience; degree in business, information technology, engineering, healthcare administration, or related field preferred. - Seven or more years of progressive program management, principal project management, or solution delivery leadership experience in large-scale implementation environments. - Experience leading complex Provider, Medicaid Enterprise, healthcare, or highly regulated delivery programs across multiple workstreams, vendors, and client stakeholders. - Demonstrated ability to manage integrated plans, dependencies, RAID, change control, governance, readiness gates, executive reporting, and delivery health for complex programs. - Strong understanding of enterprise architecture, solution design, system integration, integration testing, deployment planning, and operational readiness. Skills: - Proven ability to influence executive stakeholders, client leaders, vendors, and internal delivery teams, including leadership of delivery recovery, escalation, tradeoff, and readiness decisions. - Excellent communication, facilitation, and stakeholder management skills, with the ability to translate technical topics into business implications and executive-level recommendations. Benefits: - Generous, flexible vacation policy. - 401(k) employer match. - Comprehensive health benefits. - Educational assistance. - Variety of leadership and technical development academies to help build skills and capabilities. Pay: - Pay range: $103,300 - $147,600 per year (base pay may vary depending on geographic region, internal equity, job-related knowledge, skills, and experience among other factors). Schedule: - Position is 100% remote with up to 15% travel annually. - This is a pipeline req and we will accept applications ongoing. (Maybe we can include pipeline note under Schedule or maybe under About the role? It's about hiring process; could be omitted as it's not substantive about role? It's still info. Might include under Schedule as note.) We should remove boilerplate like EEO, legal, etc. Also remove duplicated lines like "Put your passion to work at Gainwell..." repeats earlier fluff; we already included intro fluff; we can skip duplicate. Now ensure we don't include any headings with empty content. All sections have content. Now produce HTML fragment:

  About the role

  Great companies need great teams to propel their operations. Join the group that solves business challenges and enhances the way we work and grow. Working at Gainwell carries its rewards. You’ll have an incredible opportunity to grow your career in a company that values your contributions and puts a premium on work flexibility, learning, and career development. Provides Principal-level leadership for complex Provider DDI solution delivery initiatives, with accountability for integrated execution, readiness, quality, and measurable client outcomes. This role orchestrates functional, technical, data,