Principal Engineer API Platform

CVS Health•New York, IL

23h•$144,200 - $288,400

About The Position

At CVS Health, we are building a developer platform that sets the standard for how hundreds of engineers across Retail, Pharmacy, Health Solutions, and Aetna design, build, secure, and publish APIs. Our platform spans an internal and external developer portal, an API catalog that drives discovery and prevents duplication across the enterprise, and the systems responsible for delivering APIs, agent-to-agent integrations, and MCP servers to both cloud and on-premises gateways. As a Principal Engineer on this platform, you will own the technical direction and architecture across several teams building these capabilities. This is a senior, cross-cutting role with significant organizational influence. You will establish the engineering practices that teams build on, define how APIs are designed and governed at scale, and lead the effort to embed AI-powered capabilities into the developer experience itself, from intelligent coding assistance that guides engineers toward compliant API patterns to MCP servers that make the enterprise API catalog available as a live, queryable context for AI-enabled workflows. This is a rare opportunity to shape the developer experience for a Fortune 6 company from the ground up, working with a high level of autonomy and leaving a long-term imprint on how CVS engineers build and deliver software.

Requirements

10+ years of software engineering experience, with a meaningful portion spent designing and delivering APIs at enterprise scale.
5+ years of direct experience with API security, including OAuth 2.0, OIDC, mTLS, rate limiting, and API threat modeling.
5+ years working with API gateway products and API management platforms (e.g., Apigee, Kong, Azure APIM, or equivalent).
5+ years of backend development in Java/Spring Boot and/or Node.js.
5+ years working with large public cloud platforms (GCP, AWS, or Azure), including the networking and identity primitives that underpin secure API delivery.
3+ years of experience influencing technical direction across multiple teams in a principal, staff, or architect-level capacity.
3+ years partnering with product management, architecture, and program management to shape roadmaps and deliver complex platform capabilities.
Experience building or operating an API catalog, developer portal, or internal developer platform.
Experience with GraphQL schema design and federation at scale.
Experience with mature CI/CD practices, source control, automated testing, and contract-first API development.
Recognized authority on API design, able to define and enforce standards for REST, GraphQL, event-driven, and MCP-based interfaces across the enterprise.
Understand API lifecycle management from specification and contract-first design through versioning, deprecation, and eventual retirement.
Deep experience with API gateway technologies, service mesh, and the infrastructure concerns that underpin reliable, high-throughput API delivery.
Understand what it takes to build and operate an API catalog at enterprise scale, including taxonomy, discoverability, and ownership models.
Approach API security as a first-class architectural concern, with hands-on expertise in OAuth 2.0, OIDC, mTLS, scopes, rate limiting, and threat modeling for APIs.
Understand the regulatory and compliance landscape relevant to healthcare APIs (HIPAA, FHIR, CMS interoperability rules) and can translate those requirements into platform guardrails.
Comfortable working directly with security architecture teams to validate designs and respond to findings.
Understand how to prompt, instrument, and evaluate large language models in production contexts, and know when AI is the right tool and when it is not.
Think in platforms, not features: design for extensibility, self-service, and the needs of teams you have never spoken to.
Data-driven in how you measure platform health, developer adoption, and the impact of the APIs your platform delivers, and can communicate that value clearly to engineering and business leadership.
Write clean, well-tested, production-grade code in JavaScript/TypeScript (Node.js, React) and Java/Spring Boot, and hold the teams you work with to the same standard.
Strong grasp of observability, and know how to make distributed API systems understandable through structured logging, distributed tracing, and meaningful metrics.

Nice To Haves

Hands-on experience building AI-powered developer tooling, including LLM-integrated coding assistants, MCP servers, or AI-assisted API design workflows.
Experience working with agent-to-agent (A2A) integration patterns or MCP-based tooling.
Experience with healthcare data standards and APIs, including FHIR, HL7, and CMS interoperability requirements.
Experience designing and operating event-driven APIs using Kafka or comparable streaming platforms.
Strong written communication skills, particularly in technical design documents and architecture decision records (ADRs).
Demonstrated experience growing and mentoring senior engineers and technical leads.

Responsibilities

Establish the engineering practices that teams build on.
Define how APIs are designed and governed at scale.
Lead the effort to embed AI-powered capabilities into the developer experience itself, from intelligent coding assistance that guides engineers toward compliant API patterns to MCP servers that make the enterprise API catalog available as a live, queryable context for AI-enabled workflows.
Own the technical direction and architecture across several teams building these capabilities.
Define and enforce standards for REST, GraphQL, event-driven, and MCP-based interfaces across the enterprise.
Architect systems for delivering APIs and integrations to multi-environment targets, including public cloud (GCP, AWS, Azure) and on-premises gateways.
Build and operate an API catalog at enterprise scale, including taxonomy, discoverability, and ownership models.
Define and operationalize secure-by-default patterns that developers on the platform pick up naturally.
Translate regulatory and compliance requirements (HIPAA, FHIR, CMS interoperability rules) into platform guardrails.
Lead the design and delivery of AI capabilities embedded into the developer platform, including AI-powered coding skills and assistants that guide engineers toward CVS-compliant API patterns at the point of development.
Architect and build MCP servers that expose the enterprise API catalog as a queryable, real-time context, enabling AI agents and developer tools to surface relevant APIs, usage examples, ownership information, and compliance status during development workflows.
Define the strategy for how AI tooling integrates with the portal, catalog, and gateway delivery pipeline, and work with engineering teams across CVS to drive adoption.
Articulate a clear technical vision, rally engineers across multiple teams around it, and stay close enough to execution to keep quality high.
Actively participate in architecture reviews, design documents, and pull requests, providing feedback that improves both the immediate work and the long-term thinking of the engineers.
Design for extensibility, self-service, and the needs of teams you have never spoken to.
Measure platform health, developer adoption, and the impact of the APIs your platform delivers, and communicate that value clearly to engineering and business leadership.
Invest genuinely in growing the engineers around you, particularly those earlier in their careers.
Partner with product managers, architects, and program leaders to maintain a coherent strategy and roadmap across the platform.
Champion mature CI/CD practices, including automated testing, contract testing for APIs, and safe deployment strategies across cloud and on-premises targets.
Make distributed API systems understandable through structured logging, distributed tracing, and meaningful metrics.
Evaluate emerging technologies honestly, including their trade-offs and the organizational cost of adoption.