Principal Software Engineer

We need to output HTML fragment with sections: About the role? The description includes paragraphs about mission etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We have description paragraphs: mission, position summary, expectations broken down into categories (Architect, Visionary & Strategist, Standard Setter, Technical Program Leader, Process Development and Adoption). Those could be responsibilities. Also there are required qualifications, preferred qualifications, education, business overview (maybe about the role). Benefits). Pay range given. Benefits described. No schedule info. So we will include sections: About the role (maybe position summary and mission), Responsibilities (the expectations breakdown), Requirements (maybe required qualifications?), Qualifications (maybe preferred qualifications?), Skills (maybe languages etc?), Benefits, Pay. No schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate like AI insights, EEO, etc. Also remove application instructions (like window close date? That's maybe not instruction but could be considered metadata; but we can keep as short p? The instruction says fold minor metadata into a short

or drop it. The "Qualified applicants with arrest or conviction records..." is EEO boilerplate, drop. The "We anticipate the application window..." is also maybe minor metadata; could be short p but maybe drop. Safer to drop. We need to preserve all substantive info. So include mission paragraphs, position summary, expectations details, required qualifications list, preferred qualifications list, education, benefits description, pay range. We must not invent or summarize away detail. Use

• for any list of duties/requirements/benefits. For prose use

  . For expectations breakdown, we could treat as responsibilities with subheadings? But only allowed headings are those specific; we cannot add custom headings. So we need to put responsibilities content under

  Responsibilities

  and then use prose or lists. We can embed the expectation categories as paragraphs. Similarly, Requirements section could contain required qualifications list. Qualifications section could contain preferred qualifications and education? But we have both Required Qualifications and Preferred Qualifications and Education. Could combine under Requirements and Qualifications? The instruction: use headings for those specific names. So we can have

  Requirements

  for required qualifications,

  Qualifications

  for preferred qualifications and education maybe. Or we could split: Requirements for required qualifications, Qualifications for preferred qualifications + education. Skills maybe for languages etc? But we already have languages in required qualifications. Might be redundant. Better to follow: Requirements = required qualifications list. Qualifications = preferred qualifications + education. Skills maybe not needed if covered. But we could still include Skills section for technical skills (languages, architectures, CI/CD, AI, etc.) but that would duplicate. The instruction: prefer a few substantive sections over many thin ones. So we can combine. Thus sections: About the role (mission + position summary). Responsibilities (expectations breakdown). Requirements (required qualifications). Qualifications (preferred qualifications + education). Benefits. Pay. No Schedule. Now format. We need to ensure we don't include any boilerplate like "The insights provided are generated by AI..." etc. Remove duplicated lines (the AI insights line appears twice at start). Remove. Now craft HTML. Start with

  About the role

  then

  ... mission paragraphs and position summary.

  Mission paragraphs: "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 hiring for a Principal Software Engineer, who will define and drive the technical direction for the organization and will work with high visibility enterprise teams to develop and execute Enterprise Solution Strategy for mobile. Operating as both a senior individual contributor and technical leader, you will partner closely with product, architecture, and engineering leadership to make pragmatic, high‑impact design decisions that balance speed, quality, and long‑term maintainability. The Principal Software Engineer will remain hands‑on with critical‑path systems while mentoring senior and staff engineers and translating prototypes into scalable into production‑grade platforms. You will establish clear expectations for reliability, security, performance, and operability, ensuring strong engineering fundamentals-such as testing, observability, and CI/CD-are embedded from day one. Through technical leadership, collaboration, and example, you will elevate engineering quality, accelerate delivery, and foster a culture of craftsmanship, learning, and continuous improvement." Combine into one

  maybe two paragraphs. Next

  Responsibilities

  . Then we need to list expectations breakdown. Could use
  • each with subpoints? But we can just put prose describing each category. However instruction: use
    • for any list of duties/requirements/benefits. The expectations breakdown is a list of categories with percentages and descriptions. So we should make a list. Each list item can contain the category name and description. Use maybe but not required. We'll just put text. So:
      • Architect (40% of Time): Establish and ensure adherence to technical direction, standards, guidelines, and methodology for use of specified technologies in the department. Then lead the Technical Advisory council that performs application architectural reviews on department initiatives. Partner with teams and serve as subject matter expert to provide benchmarked solutions to multiple, complex technical projects/initiatives within own area of expertise and organize cross-departmental application architectural solutions. Influence technical standards and tool selection for the entire company. Vendor technology evaluation and influence. Work with external development firms to evaluate the strength of their platforms as candidates for selection to be added to CVS' environment. Influence the vendors' technical direction to align with those of CVS. Architect for backward/forward compatibility and insulation from the shortcomings of vendor software.
      • Visionary & Strategist (10% of Time): Develop and improve strategic technical direction for functional areas. Maintain the departmental strategic multi-year roadmap and author new additions to it. Align with the Enterprise technology roadmap and extend it to include technology useful to the Specialty department. Use quantitative measures to guide architectural priorities. Engage senior technical and business leaders in the development of the technical roadmap then present the results. Keep abreast of technological trends in the industry and determine if useful and/or feasible (i.e. financial impact) and make recommendations to the organization. Build the business case for new tools and drive the funding process. Then lead Proof of Concept (POC) initiatives to evaluate technologies. When new technologies / techniques are selected, then manage the integration, cultural adoption, and transition.
      • Standard Setter (5% of Time): Lead matrixed application Technical Leads in the development and implementation of application standards through all parts of the Specialty Dispensing architectural stack. Facilitate experts in a variety of disciplines: Swift, SwiftUI, Java, Kotlin, Public & Private Cloud, Rules Engines, Open Source & Proprietary frameworks, etc. to work on how methodologies and standards will be defined.
      • Technical Program Leader (40% of Time): Act as the most senior technical contributor on strategic initiatives. During some periods leading (e.g. defining sensible sets of functionalities to be grouped into projects of a multi-year program) and other times supporting (e.g. providing application architectural designs with the Technical Lead on the project). Be deeply personally engaged in the success of this program.
      • Process Development and Adoption (5% of Time): Identifies necessary process changes for the department and methodically implements them. Leads the department's DevSecOps maturity journey. Progresses the Unit and QA Test Automation processes in collaboration with the Quality Assurance organization to "shift left". Selects and implements the tooling for the Continuous Integration & Continuous Deployment pipeline across all technology stacks (i.e. Angular, Java, Oracle). Surveys other departments, enterprise initiatives, and the industry for best practices for the department to adopt.
      Next

      Requirements

      for required qualifications list. Use
      • . Required qualifications list from posting: - 10+ years of hands-on information technology experience in systems analysis, application design, application development, and application program development - 7+ years of development experience in the following languages: Java, Swift, Swift UI, Kotlin - 5+ years of experience in design and evolve scalable, modular mobile architectures (e.g., MVVM, Clean Architecture), handle complex app lifecycles, and make long-term technical decisions across both platforms - 5+ years of experience in managing stakeholder's requirements, and technical solutions - 3+ years of experience working on CI/CD Pipeline automation - 3+ years of experience in setting engineering standards, mentor senior engineers, collaborate with product/design, and influence mobile strategy at an org-wide level - 1+ years of software development experience within AI technologies, particularly Generative AI and Large Language Models and familiarity with AI/ML frameworks and libraries (e.g., TensorFlow, PyTorch, Scikit-learn) - 1+ years of experience with Flutter - Proven ability to lead complex technical initiatives and influence engineering direction without relying on formal authority We'll list each as
      • . Next

        Qualifications

        for preferred qualifications and education. Preferred qualifications list: - Experience working with multiple foundation model providers and a clear point of view on when to use each - Experience designing or integrating AI or generative AI solutions, including APIs, models, or platforms - Hands-on working knowledge of JavaScript, AngularJS, and/or NodeJS - Experience building MCP servers and defining tool integrations for agent ecosystems - AI evaluation tooling experience (LangSmith, Braintrust, Promptfoo, or custom evaluation harnesses) - Hands‑on experience using AI coding agents (Claude Code, Codex, Cursor, GitHub Copilot) as production build tools, not just IDE assistants - Experience in the health, wellness, or pharmacy domain - Contributions to open‑source projects, published technical content, or patented innovations - Full‑stack development experience, including APIs, data stores, and cloud services Education: - Bachelor's degree or equivalent experience (HS diploma + 4 years relevant experience) We'll include education as a list item maybe. Next

        Benefits

        . Benefits description: "This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility." Also mention "Great Benefits For Great People" heading but we just put content. We could also mention "Our people fuel our future..." but that's boilerplate? Might be considered generic; but it's part of benefits section? It's more about culture. Might keep as prose but it's not specific benefit. Safer to stick to the benefits description. Next

        Pay

        . Pay range: "The Typical Pay Range For This Role Is $144,200.00 - $288,400.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS