Staff Platform Engineer

PatientPoint

6d•$136,880 - $210,891•Remote

About The Position

PatientPoint's Platform team builds and runs the cloud platform our engineers use to ship patient- and provider-facing products safely and quickly. As a Staff Platform Engineer, you’ll own technical problems that cross systems and teams, turning ambiguous goals like safer deployments or fewer pages into multi-quarter plans and leading them to done. You’ll stay hands-on, writing the hardest changes and the key design documents, and make the engineers around you better.

Requirements

5+ years of professional experience in any of: software engineering, cloud or infrastructure engineering, systems or network administration, site reliability, DevOps, or platform engineering.
Deep, hands-on experience designing and operating production cloud infrastructure, containers and CI/CD (AWS, Kubernetes or similar), with infrastructure as code.
Experience leading a technical initiative that spanned multiple systems or teams, from proposal to completion.
Experience designing for reliability and security, such as access models, deployment safety, observability and incident response.

Nice To Haves

Experience designing Kubernetes platforms (EKS, GitOps) and multi-account AWS organizations, IAM and cross-account networking; Azure is a plus.
Experience securing CI/CD: federated identity, short-lived credentials, secrets management and software supply-chain controls.
Experience setting service level objectives and alerting strategy with New Relic, PagerDuty or similar tools.
Experience with build-versus-buy and vendor evaluations, including AI-assisted tooling for operational work, in a regulated environment such as healthcare (HIPAA, SOC 2).
Bachelor’s degree in computer science or a related field, or equivalent practical experience.
Influence across teams and with leadership, without formal authority.
Comfort with ambiguity: you turn it into a plan with milestones, and put numbers on the tradeoffs.
Clear technical writing: design documents and proposals that technical and non-technical readers can act on

Responsibilities

Lead multi-quarter programs that span several systems, such as how cloud accounts, CI/CD, identity and artifact management fit together and trust each other.
Set technical direction for a large part of the platform through design documents and decision records, and build agreement across Engineering and Security.
Define reliability for the services the platform supports: service levels, alerting, and on-call design that routes problems to people who can fix them.
Sequence risky changes across interconnected systems so that fixing one doesn’t break another, including how reliability fixes from our SRE team reach production safely.
Identify what the team should work on next, and make the case with cost and risk.
Grow Senior engineers through design review and mentorship, and stay hands-on on the most critical changes.