Cloud Platform Engineer

About the Role

As a Cloud Platform Engineer at Supabase, you’ll join Cloud Engineering, part of Engineering Operations, and shape the foundations that let engineering teams build, ship, and operate infrastructure safely and independently across AWS and GCP.

This role spans cloud governance, platform engineering, and hands-on operations. You’ll work across AWS and GCP account structure, identity and access management, Infrastructure as Code (IaC), reusable platform primitives, security boundaries, and self-service workflows for engineers.

Responsibilities

• Designing and implementing cloud governance across AWS and GCP, including identity, account organization, access controls, and guardrails.
• Building reusable infrastructure and building blocks using Infrastructure as Code (IaC), enabling teams to provision and manage infrastructure safely and consistently.
• Creating self-service capabilities that reduce organizational friction and let engineers move more quickly within sensible boundaries.
• Owning resource governance and visibility: management tagging, a trustworthy inventory of what exists and who owns it, and consistent cross-account billing data.
• Developing reusable security primitives, including secrets storage, KMS, certificate management, token vending, direct service-to-service authentication, mTLS, and related platform services.
• Owning cloud-level network and operational primitives: IP address management, DNS, and health signals such as service-limit and quota alerting.
• Combining software engineering with hands-on operations and total ownership: building, deploying, monitoring, troubleshooting, and improving what you own.
• Establishing and sharing cloud engineering best practices through documentation, internal tooling, examples, and enablement.

Qualifications

• 5+ years of experience in cloud governance, platform engineering, and/or operations, having operated production systems at scale and carried on-call.
• Track record of undertaking a significant migration (e.g., rearchitected an AWS account topology, introduced IaC for existing infrastructure, centralized identity/SSO, or brought a second cloud under governance).
• Experience building internal platform and self-service experiences for other engineers.
• Depth in at least one (ideally two) of:

- Tooling & ecosystem: Breadth of AWS services (especially IAM/SSO), Well-Architected Framework, working knowledge of GCP, routine production IaC use, and compliance/audit experience.
- Software engineering: Writing production code (Go, Rust, or comparable systems languages), designing reliable services, SDLC ownership, technical RFCs.
- Operations: Running production infrastructure, on-call/pager duty, runbooks and alerting, SLO-driven prioritization.

• Comfortable treating infrastructure as software with hands-on IaC and automation experience.
• Clear communication, comfort collaborating with stakeholders, and thriving in async, globally distributed teams.