Senior Manager - Software Development Engineering

We need to output HTML fragment with sections: headings

for sections like 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 AI insights, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Description: "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." - Position Summary: "CVS Health Digital is looking for hands-on, passionate people who want to join a high energy and growing team to make a difference in customers' lives and who want to be on the forefront of digital innovation that aims to reinvent what a pharmacy and a health care company can be in the digital world. Currently, we are seeking Senior Manager - Software Development Engineering who will lead and manage a team of software engineers, providing hands-on technical direction, architecture guidance, and mentorship while establishing measurable engineering goals aligned with business outcomes. This Senior Engineer also will drive technical strategy and execution for software initiatives by defining system requirements, architecture, timelines, and deliverables." - Expectation For The Role: bullet list? Actually it's a paragraph with multiple sentences each starting with a verb. We can treat as list of responsibilities. - Required Qualifications: list of bullet points. - Preferred Qualifications: list. - EDUCATION: "Bachelor's degree or equivalent experience (High School Diploma and 4 years relevant experience)" - Business Overview: description of CVS Health purpose etc. Might be considered "About the role" or "About the company". Could be placed under "About the role" or "Company Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: could include Description + Position Summary + Business Overview? Might be too much. But we need to include sections only when posting has real specific content. We have content for About the role (description of company and role). We have Responsibilities (Expectation For The Role). We have Requirements (Required Qualifications). We have Qualifications (Preferred Qualifications). We have Skills? Could be implied but not separate. We have Benefits (Great Benefits For Great People). We have Pay (Pay Range). We have Schedule? Not mentioned. So we omit Schedule. We must not include placeholder like "commensurate with experience". Not present. We need to output HTML fragment only, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: AI insights lines, EEO, equal-opportunity, scam-warning, etc. Also remove "Qualified applicants with arrest or conviction records will be considered..." that's EEO? It's about criminal records; might be considered EEO/legal boilerplate. Should remove. Also remove "We anticipate the application window for this opening will close on: 08/21/2026" - that's application instruction? It's a date; maybe considered application instruction? The instruction says remove application instructions. So remove that line. Also remove "Our people fuel our future..." etc? That's part of benefits? Actually it's after Pay Range. Might be considered boilerplate but it's about culture; could be kept as part of About the role? Might be okay to keep but it's somewhat generic. However it's not explicitly boilerplate like EEO. Might keep. We need to decide what to keep. Let's extract substantive sections: About the role / Company overview: - Description 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." - Position Summary paragraph: "CVS Health Digital is looking for hands-on, passionate people who want to join a high energy and growing team to make a difference in customers' lives and who want to be on the forefront of digital innovation that aims to reinvent what a pharmacy and a health care company can be in the digital world. Currently, we are seeking Senior Manager - Software Development Engineering who will lead and manage a team of software engineers, providing hands-on technical direction, architecture guidance, and mentorship while establishing measurable engineering goals aligned with business outcomes. This Senior Engineer also will drive technical strategy and execution for software initiatives by defining system requirements, architecture, timelines, and deliverables." - Business Overview paragraphs: "Bring your heart to CVS Health Every one of us at CVS Health shares a single, clear purpose: Bringing our heart to every moment of your health. This purpose guides our commitment to deliver enhanced human-centric health care for a rapidly changing world. Anchored in our brand - with heart at its center - our purpose sends a personal message that how we deliver our services is just as important as what we deliver. Our Heart At Work Behaviors™ support this purpose. We want everyone who works at CVS Health to feel empowered by the role they play in transforming our culture and accelerating our ability to innovate and deliver solutions to make health care more personal, convenient and affordable. We strive to promote and sustain a culture of diversity, inclusion and belonging every day." We could combine these into About the role section. Responsibilities: The "Expectation For The Role" paragraph contains multiple sentences each starting with a verb. We can turn each sentence into a list item. Sentences: 1. Own risk mitigation and production stability by proactively identifying system vulnerabilities, leading root cause analysis, and driving timely resolution of complex production issues to ensure high availability and minimal downtime 2. Oversee the full software development lifecycle (SDLC), including requirements engineering, system design, development, testing, and deployment, ensuring adherence to modern engineering standards, secure coding practices, and scalable architecture principles 3. Collaborate cross-functionally with Product, Data, Infrastructure, and business stakeholders to translate functional requirements into technical solutions, align priorities, and resolve dependencies while maintaining efficient delivery pipelines 4. Continuously evaluate and adopt emerging technologies, frameworks, and engineering best practices, leading innovation through proof-of-concepts and informed technology selection to enhance system performance and developer productivity 5. Build and develop high-performing engineering teams by hiring top talent, conducting technical performance evaluations, and fostering a culture of continuous improvement, technical excellence, and knowledge sharing We'll make a

  • for each. Required Qualifications: list: - 7+ years of overall software engineering experience with at least 5+ years of experience of leading projects or managing directs - 7+ years of experience using and/or managing projects using Java, Spring boot, Kafka to build/deploy, and maintain software applications using cloud platforms - 3+ years of experience leading cross-functional teams without direct authority, including documented collaboration with engineering, architecture, security, and business stakeholders in a matrixed organization - 3+ years of experience defining technology strategy and leading the adoption and operationalization of technologies such as AI/ML, cloud services, automation, and developer productivity tools in a large-scale enterprise environment with evidence of measurable impact (e.g., reduction in MTTR, cost savings, efficiency gains, or adoption KPIs) - Strong expertise in cloud platforms, distributed systems, APIs, microservices, and modern software development practices Preferred Qualifications: list: - Experience with retail or health care industry with background in fulfillment, dispensing & delivery - Experience with developing in AWS or GCP or Azure or similar public cloud environments (GCP preferred) - Proven success driving technical strategy, engineering excellence, and organizational transformation - Excellent communication, stakeholder management, and cross-functional collaboration skills - Experience managing multiple teams and developing engineering leaders - Ability to balance technical depth with business outcomes and strategic decision-making - Ensured code quality and technical excellence through reviews, testing strategies, and debt management - Owned system reliability and operational performance, including monitoring, incident management, and SLAs Education: "Bachelor's degree or equivalent experience (High School Diploma and 4 years relevant experience)" - could be under Qualifications or separate. We'll put under a section "Qualifications" maybe? But we already have Required and Preferred Qualifications. Education could be part of Required Qualifications but it's separate. We could make a section "Education". However the instruction only lists certain headings; but we can add other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Safer to stick to those headings. Education could be placed under Requirements or Qualifications. Since we have Required Qualifications and Preferred Qualifications, we could add Education as part of Required Qualifications (maybe as a bullet). But the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can use those exact headings. We'll map: - About the role: includes Description, Position Summary, Business Overview. - Responsibilities: Expectation For The Role list. - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list. - Benefits: Great Benefits For Great People paragraph. - Pay: Pay Range paragraph. We might also include Skills? Not explicitly separate; we could omit. We must not include Schedule. Now we need to format. We need to ensure we don't include any boilerplate like "Our people fuel our future..." etc. That's after Pay Range; might be considered part of benefits? Actually it's after Pay Range: "Our people fuel our future. Our teams reflect the customers, patients, members and communities we serve and we are committed to fostering a workplace where every colleague feels valued and that they belong." This is generic but could be considered part of About the role or Benefits? It's not benefits. It's more culture. Might be okay to keep in About the role. But it's somewhat generic; but not explicitly boilerplate like EEO. I'd keep it in About the role. Also we need to remove the line about "We anticipate the application window for this opening will close on: 08/21/2026". Remove. Also remove "Qualified applicants with arrest or conviction records will be considered for employment in accordance with all federal, state and local laws." Remove. Also remove the duplicated AI insights lines at top and bottom. Now produce HTML. We'll start with

    About the role

    then

    ... combine paragraphs maybe separate

    for each. We need to preserve all substantive info; we can split into multiple

    tags. Let's craft. About the role content: Paragraph1: Description. Paragraph2: Position Summary. Paragraph3: Business Overview (including Heart at Work etc.) Paragraph4: "Our people fuel our future. Our teams reflect the customers, patients, members and communities we serve and we are committed to fostering a workplace where every colleague feels valued and that they belong." We'll keep that. Now Responsibilities:

    Responsibilities

    then
    • each sentence. Requirements:

      Requirements

      then
      • each bullet. Qualifications:

        Qualifications

        then
        • each preferred bullet. Benefits:

          Benefits

          then

          the benefits paragraph. Pay: