Data Engineering at CVS

CVS's 3.2 Glassdoor rating sits toward the bottom of the pack, and Blind sentiment runs mixed, which together suggest a workplace where day-to-day conditions vary sharply by team. The happiness picture is neutral and trending up, so conditions aren't deteriorating, but the gap between Glassdoor and a company's public-facing culture promises is wider here than at peers. Pay comes in in line with other Healthcare companies: you're not taking a comp cut to be in healthcare, but you're also not closing the gap to tech-sector ceiling offers. What CVS offers that many tech employers don't is exposure to regulated, high-stakes data at a scale most engineers never see. What you give up is some pace of tooling modernization and the autonomy that comes with flatter org structures. The tension is whether the domain depth compensates for an environment that Glassdoor reviewers find inconsistent.

CVS has 1 tracked layoff in the past 12 months, the most recent in Jul 2026, and no executive departures in the same window, which points to relative leadership continuity compared to healthcare peers that have seen C-suite turnover drive reorganizations. The low 30-day layoff risk reading reinforces that near-term stability is reasonable to assume. Hiring volume is modest: 2 open data engineering roles across 2 cities, concentrated in Hartford. That low open-role count either signals a lean data team running efficiently or a constrained headcount budget; given the integration work that Aetna and CVS Caremark still require, the former is more likely. Engineers joining now would enter during a consolidation phase rather than an expansion one, which typically means more ownership over existing systems and fewer opportunities to build from scratch.

CVS runs one of the largest integrated pharmacy and health benefits operations in the country, and that scale creates data problems that are unglamorous and hard. Claims adjudication, pharmacy dispensing, and insurance enrollment each generate high-volume transactional records that have to reconcile across Aetna's payer systems and CVS's retail and specialty pharmacy lines. The data engineering job here is largely about stitching those worlds together: building pipelines that can handle regulated PHI, enforcing data contracts across business units that didn't originally share a schema, and keeping SLAs intact when upstream sources are batch-heavy and irregular. The AWS, CI/CD and BigQuery stack suggests a cloud-forward warehouse posture on a foundation that still depends on scripted orchestration. Engineers who join should expect to spend real time on interoperability problems between acquired systems, not greenfield architecture.