Senior Platform Engineer (Cloud Foundations)

Heartflow•San Francisco, CA

1d•$180,000 - $215,000•Hybrid

About The Position

Heartflow is building a new AWS foundation with new accounts, Kubernetes clusters, and supporting cloud services. Existing applications running on AWS Lambda and Fargate, alongside RDS, API Gateway, and related services defined in AWS CDK, are being moved to the new platform. The Senior Platform Engineer will join the Infrastructure Platform team, which owns cloud foundations, site reliability engineering (SRE), and developer experience. The initial major project is the migration to Kubernetes, with the role broadening over time across these areas. The initial work includes developing migration patterns and reference implementations for moving CDK-based serverless applications to EKS, translating CDK stacks into Terraform/Terragrunt, Helm, service templates, and developer portal integrations, and building automated solutions for event-driven workflows on Kubernetes. The engineer will also plan data-tier and API cutovers, coordinate workload migrations with application teams, and benchmark migrated services while validating resource configurations, observability, and service-level objectives. Ongoing platform work includes building and maintaining cloud foundations as code, contributing to SRE practices, improving developer experience through Harness pipelines and the Cortex service catalog, and creating standards, guardrails, and runbooks. The role also supports Linux and Windows systems where needed, with automation preferred. The work supports products used in patient care, where reliability, security, and traceable change management are important.

Requirements

Several years of platform, infrastructure, SRE, or DevOps engineering experience.
Experience with at least one migration of production workloads to a new platform or architecture; Fargate or ECS to Kubernetes is the closest match, and serverless to containers is also relevant.
Strong working knowledge of Kubernetes on AWS (EKS), including networking, security, scaling, and day-two operations.
Solid AWS experience across compute services such as Lambda, ECS, and EKS; data services such as RDS; API Gateway; VPC networking; and IAM.
Production experience with Terraform and comfort with Helm.
Scripting and automation skills in Bash, Python, or Go.
Hands-on experience with CI/CD systems and containers.
Clear written and verbal communication skills and a record of influencing technical decisions across teams.

Nice To Haves

Experience with AWS CDK, including reading and refactoring existing stacks.
Experience with KEDA or other event-driven scaling on Kubernetes.
Experience with Terragrunt, Harness, or an internal developer portal such as Cortex or Backstage.
Windows or Linux systems administration experience.
Experience in a regulated environment such as healthcare, finance, or medical devices, including change control and audit evidence.
Experience with monorepos.
Prior ownership of a multi-quarter technical initiative.

Responsibilities

Contribute migration patterns and reference implementations for moving CDK-based serverless applications to EKS, supporting cross-account interoperability during the migration.
Translate existing CDK stacks into Terraform/Terragrunt, Helm, service templates, and developer portal integrations.
Develop robust, scalable, automated solutions for running event-driven, serverless-like workflows on Kubernetes, potentially using KEDA or similar cloud-native tools.
Plan data-tier and API cutovers to keep downtime and risk low.
Work with application teams to understand workloads, sequence migrations, and provide tooling and documentation to support migration with minimal hand-holding.
Benchmark migrated services, tune resource requests and limits, and ensure observability and service-level objectives match or exceed prior levels.
Build and maintain cloud foundations, including account structure, networking, IAM, and shared services, as code.
Contribute to SRE practices, including SLOs, alerting, incident response, capacity and cost management, and an on-call rotation as the team matures.
Improve developer experience through Harness pipelines, golden paths, and the Cortex service catalog, treating internal engineers as platform customers.
Write standards, guardrails, and runbooks for other teams.
Support Linux and Windows systems where required, preferring automation over manual work.