Jobs / United States / Supabase
Cloud Platform Engineer
Supabase · 🇺🇸 Remote, Global · Remote
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal — ask the recruiter.
- No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
- The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
- No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
- Confirmed live todayWhen a source last listed this job as open.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence; it is not legal advice and never a guarantee — the employer and the immigration authority decide. Sign in to factor in where you can already work.
Or apply yourself on the official page →
Why not apply?
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
SponsorApply flags time-wasters so your applications go where they can land. These come from the posting's own wording — read the original listing to confirm. See better-fit alternatives →
Sponsor Radar — Supabase
This employer posted directly and does not match a government sponsor register.
Past sponsorship or register membership never guarantees sponsorship for this vacancy or for you. Full Sponsor Radar for Supabase →
About the role
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 is a role spanning 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. You’ll be joining at a point where many of these foundations are being actively defined or reworked. We’re looking for someone who can take ambiguous, messy, business-critical infrastructure problems and turn them into pragmatic systems, tools, standards, and written guidance that scale with the company and empower teams to go faster. 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 practice