Principal Cloud Infrastructure Engineer (GCP)

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

We are looking for a GCP Principal Engineer to lead our Cloud Engineering team, owning the Google Cloud Platform for the enterprise. This is a foundational platform role — you are the GCP technical authority, setting architectural/engineering direction, establishing engineering standards, and ensuring the platform is secure, scalable, and built to last.

Your role will include driving designs of the platform, mentoring the engineers around you, and aligning quality and best practices. You bring deep GCP expertise, a platform-owner mindset, and the leadership presence to align engineers and stakeholders around a shared technical vision. This role demands a cloud-first thinker who ensures cloud solutions meet business needs efficiently while prioritizing Infrastructure as Code (IaC) to create repeatable, automated deployments. You need to have a proven track record of architecting cloud environments from scratch. You'll drive cloud transformation initiatives all CSP’s focusing on the GCP platform while ensuring every design decision considers security, reliability, and scalability.

This is not a hands-off leadership role — you write code, review designs, and stay close to the work.

1. GCP Platform Ownership

Own the enterprise GCP platform end-to-end: organization structure, resource hierarchy, networking architecture while collaborating with several teams to ensure the platform is stable and compliant.

Define and maintain the GCP landing zone — Shared VPC, Org Policies, and project factory patterns — as the foundation all product teams build on.

Serve as the one of the final technical authorities on GCP engineering decisions, reviewing designs for scalability, security, and operational excellence before they reach production.

Build self-service platform capabilities that enable product engineering teams to move fast without compromising standards.

2. Technical Team Leadership

Lead the GCP cloud engineering team as the technical anchor — set direction, conduct design reviews, unblock engineers, and drive delivery on platform initiatives.

Establish and enforce engineering standards: IaC patterns, naming conventions, tagging strategy, branching models, and deployment practices.

Mentor engineers at all levels, building depth on the team and raising the bar on what “excellence” looks like in cloud engineering.

Partner with architecture, security, operations, and business stakeholders to translate enterprise requirements into platform capabilities.

3. Infrastructure as Code & Automation

Drive Infrastructure as code as a core principle — reusable modules, pipeline integration, state management, and policy guardrails.

Build and maintain CI/CD pipelines using Cloud Build, GitHub Actions, and Artifact Registry for both platform infrastructure and application teams.

Write production-quality automation to extend platform functionality, integrate GCP APIs, and eliminate operational toil.

Implement policy-as-code using OPA, Config Connector, and GCP Org Policies to enforce governance at scale without manual gatekeeping.