CVS Health SDE onboarding and first 90 days tips 2026

What does the CVS Health SDE onboarding schedule look like for the first 90 days?

The schedule is a fixed 90‑day plan: Day 1‑5 orientation and access setup, Day 6‑15 buddy‑driven code‑base walkthrough, Day 16‑30 first small feature ticket, Day 31‑60 cross‑team project, Day 61‑90 ownership of a medium‑scale service and a formal review.

On Day 1 you receive a laptop pre‑loaded with CVS Health’s internal toolchain, including Jira, Confluence, and the Artifactory repository; you also attend a 90‑minute welcome talk from the VP of Digital Health engineering.

During Days 6‑15 your assigned buddy, a senior SDE on the Pharmacy Claims platform, walks you through the microservice architecture, shows you how to run the local Docker compose stack, and assigns you a “hello‑world” bug fix in the prescription‑eligibility service.

By Day 16 you are expected to pick up a Jira ticket tagged “good‑first‑issue” that touches the API layer for refill requests; the ticket includes explicit acceptance criteria and a definition of done that requires unit test coverage above 80 %.

The cross‑team project from Day 31‑60 typically involves the MinuteClinic scheduling system; you pair with a backend engineer from the Aetna integration team to design a REST endpoint that consolidates appointment slots.

The final 30‑day period culminates in a demo to the hiring manager and a written self‑assessment using the CVS Health SDE Competency Rubric, which scores you on code quality, system design, and collaboration.

How do I set up my development environment at CVS Health as a new SDE?

You follow the “New Engineer Onboarding Playbook” stored in the Confluence space ENG‑ONBOARD, which prescribes a step‑by‑step script.

First, you enroll your device in CVS Health’s MDM solution (Microsoft Intune) to receive the corporate certificate; this takes roughly 15 minutes after you accept the enrollment email.

Next, you clone the internal GitLab group cvs-health/platform and run the provided setup.sh script, which installs Java 17, Maven 3.9, Docker Desktop, and the internal Nexus proxy.

The script also configures your IDE (IntelliJ IDEA Ultimate) with the CVS Health code style XML and the SpotBugs plugin; you then run the command ./gradlew clean build to verify the build passes.

If you encounter a “certificate‑not‑trusted” error, you must run the internal script fix‑certs.sh, which adds the CVS Health root CA to your Java truststore—a step documented in the troubleshooting section with ticket INFRA‑4521.

Once the build succeeds, you are granted read‑only access to the production‑like staging environment via the internal VPN; you receive a temporary AWS IAM role with read‑only permissions to the claims‑processing S3 bucket.

What are the key expectations for an SDE during the first 30 days at CVS Health?

You are expected to deliver at least one production‑ready change and to demonstrate fluency in the team’s agile ceremonies.

Your manager will ask you to present the design of your first feature ticket in the sprint planning meeting; the presentation must include a sequence diagram, a data‑flow description, and a risk‑mitigation plan.

You must also achieve a minimum of 70 % test coverage on the code you modify, as enforced by the pre‑commit hook that runs Jacoco; failure blocks the merge request.

Participation in the daily stand‑up is mandatory; you are to give a 60‑second update that covers what you completed yesterday, what you plan today, and any blockers, following the format prescribed in the SDE Engineering Handbook.

By the end of week 4 you should have completed the “SDE Foundations” badge on CVS Health’s internal learning platform, which consists of four modules: secure coding, observability, API versioning, and privacy‑by‑design.

How does CVS Health measure success for new SDEs in their first 90 days?

Success is measured through a combination of quantitative metrics and qualitative feedback captured in the 90‑day review form.

Quantitatively, the hiring manager looks at three numbers: story points completed (target ≥ 45), defect leakage rate (target ≤ 2 % of total bugs found in QA), and mean time to recover (MTTR) from incidents you caused (target ≤ 30 minutes).

Qualitatively, you receive feedback from three sources: your buddy, your squad lead, and a peer from a different tribe; each fills out a short form rating you on communication, ownership, and adherence to CVS Health’s engineering principles.

The scores are combined into a weighted 0‑100 index; a score above 75 is considered “meets expectations” and triggers eligibility for the first performance‑based bonus, which is typically 5 % of base salary.

If your score falls below 60, you are placed on a 30‑day performance improvement plan that pairs you with a mentor from the Platform Engineering tribe.

What common mistakes do new SDEs make during CVS Health onboarding and how to avoid them?

Mistake 1: Treating the onboarding buddy as a ticket‑resolution service instead of a learning partner.

BAD: You ask your buddy to fix every build error you encounter, then close the ticket without understanding the root cause.

GOOD: You schedule a 15‑minute “debug‑pair” session each morning, ask the buddy to explain the failing test, and then attempt to fix it yourself before seeking help.

Mistake 2: Ignoring the internal documentation standards and committing code that lacks required comments or architecture decision records.

BAD: You add a new utility class with no Javadoc and push it directly to the main branch, causing the pre‑commit hook to fail and slowing the squad’s velocity.

GOOD: You read the CONTEMPLATE template in the repo’s docs folder, fill out an ADR for any change that touches a public API, and run the markdown‑lint check locally before committing.

Mistake 3: Over‑engineering the first feature to impress the team, resulting in scope creep and missed deadlines.

BAD: You spend two weeks designing a plug‑in architecture for a simple CSV‑import tool when the ticket only required a straightforward parser.

GOOD: You break the ticket into two sub‑tasks, deliver the parser in three days, and open a separate improvement ticket for the plug‑in layer after the initial demo.

Preparation Checklist

  • Review the CVS Health Engineering Handbook, focusing on the sections “Secure Coding Standards” and “Observability Requirements” (the handbook is updated quarterly; the latest version is v3.2 released in March 2026).
  • Set up a personal GitLab account with two‑factor authentication and add your SSH key; verify you can clone the cvs-health/platform group without errors.
  • Install Docker Desktop version 24.0+ and allocate at least 8 GB of RAM to avoid container‑startup failures during the build‑validation step.
  • Practice writing architecture decision records using the ADR template found in Confluence under ENG‑DOCS‑ADR; a good example is the “API versioning for prescription‑claims” record from Q4 2025.
  • Complete the “SDE Foundations” learning path on CVS Health’s internal LMS before your start date; the path includes a quiz that you must pass with ≥ 80 % to unlock the badge.
  • Work through a structured preparation system (the PM Interview Playbook covers behavioral storytelling with real debrief examples) to sharpen your communication style for squad meetings and the 90‑day review.
  • Prepare a 5‑minute “impact story” that highlights a past project where you improved system reliability, quantifying the result (e.g., reduced latency by 35 % or cut incident MTTR from 45 min to 12 min).

Mistakes to Avoid

  • BAD: Assuming that the first sprint is a “grace period” where you can skip writing unit tests because the code is “just a prototype.”

GOOD: Treat every line of code as production‑ready from day 1; run the pre‑commit hook locally and fix any coverage gaps before opening a merge request.

  • BAD: Waiting for the hiring manager to schedule your 90‑day review and then showing up unprepared with no data or self‑assessment.

GOOD: Export your Jira report, Jenkins build stats, and SonarQube quality gate results two days before the meeting; draft a one‑page self‑assessment using the CVS Health SDE Competency Rubric template.

  • BAD: Using public Stack Overflow snippets directly in internal repositories without checking licensing or security approvals.

GOOD: Copy the snippet into a personal sandbox, run it through the internal Black Duck scan, and only commit after receiving a “clear” tag from the security portal.

📖 Related: CVS Health PM mock interview questions with sample answers 2026

FAQ

What is the typical base salary for an entry‑level SDE at CVS Health in 2026?

The base salary for a new graduate SDE ranges from $115,000 to $130,000, with a target annual bonus of 10 % and equity grants averaging 0.025 % of fully diluted shares; a sign‑on bonus of $12,000 to $18,000 is common for candidates with prior internship experience.

How long does it take to receive the first code‑push approval after starting?

Most new SDEs receive their first approved merge request within 10 to 15 business days, assuming they complete the environment setup on Day 1 and pick up a “good‑first‑issue” ticket by Day 6; delays usually stem from missing access to the Artifactory repository, which is resolved by submitting an internal access request ticket (INFRA‑7832).

Which internal tools should I prioritize learning during the first month?

Prioritize mastering Jira for backlog tracking, Confluence for documentation, and the internal observability stack (Grafana, Loki, and Tempo) for debugging; proficiency in these tools is explicitly evaluated in the 90‑day review under the “Systems Thinking” competency.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.

Related Reading

  • Review the CVS Health Engineering Handbook, focusing on the sections “Secure Coding Standards” and “Observability Requirements” (the handbook is updated quarterly; the latest version is v3.2 released in March 2026).