supabase - Cloud Platform Engineer

• WHAT YOU’LL BE RESPONSIBLE FOR • 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. • YOU MIGHT BE A GOOD FIT IF YOU • Have 5+ years of experience in cloud governance, platform engineering, and/or operations, have operated production systems at scale, and carried on-call for them. • Have previously undertaken 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. • Enjoy building internal platform and self-service experiences for other engineers. • Are genuinely deep in at least one—ideally two—of the three strength areas below (and tell us which is your center of gravity): • Tooling & ecosystem: You’re intimately familiar with the breadth of AWS services in general, and IAM/SSO in particular. You know their Well-Architected Framework, and when to reach outside. You have working knowledge of GCP. You use IaC routinely and have run it in production, whichever tool. You’ve probably collaborated with auditors on meeting compliance requirements. • Software engineering: You write real production code (Go, Rust, or a comparable systems language), and can build reliable, maintainable services. You thrive across all stages of the SDLC, set technical direction, know how to de-risk projects, and produce written artifacts such as RFCs. • Operations: You’ve run production infrastructure yourself: carried the pager, written the alerts and runbooks, used SLOs or similar to decide what to fix first, and made shared systems less risky over time. You like owning systems, simplifying complex infrastructure problems, and turning best practices into reusable building blocks. • Are comfortable treating infrastructure as software and have relevant experience with IaC and automation. • Communicate clearly, work with a wide range of stakeholders, and thrive in async, globally distributed teams. • Are comfortable navigating ambiguity and iterating toward better systems over time.