Digital Product Implementation Manager
for section headings: 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. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc.
We need to parse the posting.
Content:
Intro paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time."
That's about the role? Could be "About the role". We'll put that in About the role
with
containing that paragraph. Job Description: "Serves as a Technical Digital Product Implementation Manager for Aetna Health Customizations supporting plan sponsors and Book of Business products. Candidate will lead and oversee the deployment and integration of advanced digital technologies, including SSO, API, and content management systems. Role requires autonomously driving successful implementation while managing multiple deliveries and collaborating with several business partners. This position requires strong communication, project management, and technical skills combined with healthcare industry knowledge to implement digital enhancements that improve the member experience, create operational efficiency, and ensure compliance with industry regulations." That's also about the role. Could combine with intro. Key Responsibilities: list bullet points. We need to output
Responsibilities
with- each.
Responsibilities bullet list:
- Independently lead the end-to-end implementation of digital technology solutions, including SSO and API integrations, in conjunction with internal and external partners.
- Own all portions of project delivery, including; requirement gathering, project documentation, facilitation and collaboration efforts with all impacted parties, testing, release, and support.
- Collaborate with business stakeholders to understand their needs, define project scope, and ensure alignment with organizational goals.
- Communicate project progress, risks, and/or blockers, to progress project and show transparency in approach.
- Provide technical guidance and expertise throughout the implementation process, troubleshoot issues, and ensure systems are integrated effectively and securely.
Note: bullet includes a semicolon after "including;" but we keep as is.
Required Qualifications: list bullet points.
- Bachelor's degree
- 5+ years of experience in the healthcare industry
- 5+ years of experience managing projects from discovery, through implementation, to delivery and support.
- 5+ years of experience in technical delivery
Preferred Qualifications: list bullet points.
- Ability to work collaboratively in a fast-paced, dynamic environment.
- Strong critical thinker who makes balanced, insightful decisions using solutions-based thinking in problem-solving, asking probing questions, and looking for underlying issues.
- Excellent leadership, communication, and problem-solving skills.
- Demonstrated relationship management skills; capacity to quickly build and maintain credible relationships at varying levels of the organization.
- Experience in agile product development.
- Strong negotiation, organizational, management, analytical, and people skills.
Education: "Bachelor's degree preferred/specialized training/relevant professional qualification." This seems like duplicate of required qualification; but we can treat as part of Qualifications? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications and Preferred Qualifications. Could combine into Qualifications section? But we have separate headings: Requirements, Qualifications, Skills. Might map Required Qualifications to Requirements, Preferred Qualifications to Qualifications? Or Skills could be derived from preferred qualifications like leadership, communication etc. However we must not invent sections; we need to include a section only when posting has real specific content for it. The posting includes "Required Qualifications" and "Preferred Qualifications". It also includes "Education". It also includes "Anticipated Weekly Hours 40", "Time Type Full time", "Pay Range". Also "Great Benefits For Great People" describing benefits.
Thus we can have sections:
- About the role (intro + job description)
- Responsibilities
- Requirements (Required Qualifications)
- Qualifications (Preferred Qualifications)
- Skills (maybe we could extract skills from preferred qualifications? But we already have Qualifications; maybe we can skip Skills if no explicit skills list separate. However the posting includes "Strong communication, project management, and technical skills combined with healthcare industry knowledge". That's in job description. Could treat as Skills? But we already have content about skills in description. Might be better to have a Skills section summarizing those? But we must not invent or summarize away detail. We could extract the skill mentions: strong communication, project management, technical skills, healthcare industry knowledge, leadership, communication, problem-solving, relationship management, agile product development, negotiation, organizational, management, analytical, people skills. That's a lot; but we could put them in Skills section as list. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Qualifications or Requirements. But we already have Required and Preferred qualifications sections. Could we treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and then we might not need Skills separate. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't mandate we must use all; we include only when posting has real specific content. So we can have Requirements and Qualifications sections, and maybe Skills not needed if content already covered. But we might still include Skills if we can pull out explicit skill statements not already in qualifications. However the preferred qualifications list includes many skill-like items: ability to work collaboratively, strong critical thinker, excellent leadership, communication, problem-solving, relationship management, experience in agile product development, strong negotiation, organizational, management, analytical, and people skills. Those are skills. So we could put those under Skills. But then we would duplicate content between Qualifications and Skills. Better to follow the posting's own headings: Required Qualifications and Preferred Qualifications. Map Required Qualifications to Requirements, Preferred Qualifications to Qualifications. Then we can omit Skills section because we already captured skills in Qualifications. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not requirement to use all. So we can omit Skills. Now Benefits: we have "Great Benefits For Great People" paragraph describing benefits: medical, dental, vision coverage, paid time off, retirement savings options, wellness programs, other resources based on eligibility. Also mention that additional details provided during application process and on Benefits Moments. So we can create Benefits section with
- items: medical coverage, dental coverage, vision coverage, paid time off, retirement savings options, wellness programs, other resources (based on eligibility). We should not invent details; we can list those as they appear.
Pay: we have Pay Range: "The Typical Pay Range For This Role Is $92,700.00 - $185,400.00". Also mention bonus/commission/incentive. So we can create Pay section with that info.
Schedule: we have "Anticipated Weekly Hours 40" and "Time Type Full time". So we can create Schedule section with that.
We must not include boilerplate like EEO, application instructions, etc. Also remove lines like "Qualified applicants with arrest or conviction records will be considered..." that's EEO/legal; remove. Also remove "We anticipate the application window for this opening will close on: 10/02/2026." That's application instruction; remove. Also remove "Our people fuel our future..." etc maybe considered boilerplate? It's about culture but could be part of About the role? It's generic; but we already have intro about CVS Health mission. The later paragraph about "Our people fuel our future..." is generic EEO/diversity; could be considered boilerplate; better to remove. Also "Great Benefits For Great People" we kept as Benefits.
Now we need to output only HTML fragment, no /, no markdown fences.
Structure:
About the role
We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time.
Serves as a Technical Digital Product Implementation Manager for Aetna Health Customizations supporting plan sponsors and Book of Business products. Candidate will lead and oversee the deployment and integration of advanced digital technologies, including SSO, API, and content management systems. Role requires autonomously driving successful implementation while managing multiple deliveries and collaborating with several business partners. This position requires strong communication, project management, and technical skills combined with healthcare industry knowledge to implement digital enhancements that improve the member experience, create operational efficiency, and ensure compliance with industry regulations.
Responsibilities
- Independently lead the end-to-end implementation of digital technology solutions, including SSO and API integrations, in conjunction with internal and external partners.
- Own all portions of project delivery, including; requirement gathering, project documentation, facilitation and collaboration efforts with all impacted parties, testing, release, and support.
- Collaborate with business stakeholders to understand their needs, define project scope, and ensure alignment with organizational goals.
- Communicate project progress, risks, and/or blockers, to progress project and show transparency in approach.
- Provide technical guidance and expertise throughout the implementation process, troubleshoot issues, and ensure systems are integrated effectively and securely.
Requirements
- Bachelor's degree
- 5+ years of experience in the healthcare industry
- 5+ years of experience managing projects from discovery, through implementation, to delivery and support.
- 5+ years of experience in technical delivery
Qualifications
- Ability to work collaboratively in a fast-paced, dynamic environment.
- Strong critical thinker who makes balanced, insightful decisions using solutions-based thinking in problem-solving, asking probing questions, and looking for underlying issues.
- Excellent leadership, communication, and problem-solving skills.
- Demonstrated relationship management skills; capacity to quickly build and maintain credible relationships at varying levels of the organization.
- Experience in agile product development.
- Strong negotiation, organizational, management, analytical, and people skills.
Benefits
- Medical coverage
- Dental coverage
- Vision coverage
- Paid time off
- Retirement savings options
- Wellness programs
- Other resources (based on eligibility)
Pay
The typical pay range for this role is $92,700.00 - $185,400.00. This position is eligible for a CVS Health bonus, commission or short‑term incentive program in addition to the base pay range.
Schedule
Anticipated weekly hours: 40. Time type: Full time.
Check for any leftover boilerplate: We removed EEO, application window, etc. Also removed "Our people fuel our future..." etc. Also removed "Additional details about available benefits are provided during the application process and on Benefits Moments." That's part of benefits but we could keep as a sentence? It's more about where to get details; could be considered boilerplate but it's
- items: medical coverage, dental coverage, vision coverage, paid time off, retirement savings options, wellness programs, other resources (based on eligibility). We should not invent details; we can list those as they appear.
Pay: we have Pay Range: "The Typical Pay Range For This Role Is $92,700.00 - $185,400.00". Also mention bonus/commission/incentive. So we can create Pay section with that info.
Schedule: we have "Anticipated Weekly Hours 40" and "Time Type Full time". So we can create Schedule section with that.
We must not include boilerplate like EEO, application instructions, etc. Also remove lines like "Qualified applicants with arrest or conviction records will be considered..." that's EEO/legal; remove. Also remove "We anticipate the application window for this opening will close on: 10/02/2026." That's application instruction; remove. Also remove "Our people fuel our future..." etc maybe considered boilerplate? It's about culture but could be part of About the role? It's generic; but we already have intro about CVS Health mission. The later paragraph about "Our people fuel our future..." is generic EEO/diversity; could be considered boilerplate; better to remove. Also "Great Benefits For Great People" we kept as Benefits.
Now we need to output only HTML fragment, no /, no markdown fences.
Structure: