All remote jobs

Cloud Platform Engineer

Review the role, location requirements, compensation details, and application process before deciding whether this opportunity fits your next career move.

Remote from
🌐 Anywhere
Salary
Undisclosed
Employment
Full Time
Experience
Open level
Published
Apply before
22 Nov 2026
Listing views
27
Application actions
1
Application toolkit

Make your next move.

Prepare your resume, explore your fit, and draft a cover letter for this opportunity.

AI Summary

The role, at a glance.

Supabase is hiring a Cloud Platform Engineer to build and operate cloud foundations across AWS and GCP. The role centers on cloud governance, IAM, account organization, Infrastructure as Code, security primitives, networking, and self-service internal platforms. The engineer will own production systems end to end, including deployment, monitoring, incident response, documentation, and operational improvements. Success requires strong systems engineering judgment, experience with scalable cloud operations and on-call work, and clear asynchronous collaboration in a distributed team.

Role DNA

A quick view of the complexity, pace, ownership and collaboration implied by the job description.

Job Complexity

5/5
EasyHard

Pace & Pressure

4/5
RelaxedFast-paced

Autonomy Level

5/5
GuidedFull ownership

Communication Load

4/5
IndependentCollaborative
AI insightThis is a senior, broad-scope infrastructure role requiring deep production experience across multi-cloud governance, security, automation, and operations. The successful candidate must independently turn ambiguous platform problems into reliable standards and reusable services.

Salary analysis

Estimated compensation compared with the broader US market for similar roles.

Estimated job median (per year)Highly competitive
$180,000
US market range (per year)$145k–$215k
AI insightThe yearly pay period is inferred from the job context; it was not explicitly stated by the employer. No employer salary was disclosed. The annual USD figures are AI estimates for a senior cloud platform engineering role in the US market; the yearly cadence is inferred from the full-time senior professional role.

Core skills

Skills and capabilities most closely associated with this opportunity.

Sample interview questions
How would you approach establishing governance for a growing multi-account AWS and GCP environment?

I would first inventory accounts, projects, identities, workloads, ownership, and existing controls. I would then define a landing-zone model with centralized identity, least-privilege access, organization policies, network boundaries, mandatory tagging, audit logging, and IaC-based provisioning. I would roll this out incrementally with clear ownership and developer-friendly self-service workflows.

Describe how you would introduce Infrastructure as Code for existing unmanaged cloud infrastructure.

I would prioritize the most critical and frequently changed resources, document the current state, and import resources into a version-controlled IaC workflow. I would validate plans carefully, use peer review and staged deployments, and avoid risky large-scale changes until the state is trustworthy. The end goal would be reusable modules, policy checks, and clear ownership rather than merely representing existing resources in code.

What practices would you use to make a platform self-service without weakening security controls?

I would provide approved reusable building blocks with secure defaults, such as modules for service identities, secrets, certificates, networking, and logging. Guardrails should be encoded through policy, permissions, and automated validation rather than manual ticket reviews. Developers should receive clear documentation, actionable errors, and an escalation path for legitimate exceptions.

How do you prioritize reliability work when operating shared cloud infrastructure?

I use service objectives, incident history, customer impact, and operational risk to prioritize work. I focus first on eliminating recurring failure modes, reducing blast radius, improving detection and recovery, and documenting response procedures. I also balance immediate reliability fixes with investments that make future teams less dependent on manual operations.

How would you communicate a complex infrastructure migration to engineering and security stakeholders?

I would create a concise RFC describing the problem, target architecture, alternatives, risks, ownership, rollout stages, and rollback plan. I would involve stakeholders early, explicitly identify decisions and dependencies, and provide regular asynchronous updates with measurable progress. After the migration, I would document operational changes and capture lessons learned for future platform work.

This analysis is generated from the job description. Salary estimates, role characteristics and sample answers are guidance, not employer-provided facts.
Opportunity details

About this 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 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.

What We Offer

  • Fully Remote

    We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.

  • ESOP

    Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.

  • Tech Allowance

    Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.

  • Health Benefits

    Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family’s health are important to us.

  • Annual Off-Sites

    Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It’s a highlight of our year.

  • Flexible Work

    We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.

  • Professional Development

    Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.

About the Team

Supabase was born-remote and open-source-first. We believe our globally distributed team is our secret weapon in building tools developers love.

  • ~400 team members

  • 60+ countries

  • 20+ languages spoken

  • Over $1B raised (including our $500M Series F)

  • 540,000+ community members

We move fast, build in public, and use what we ship. If it’s in your project, we probably use it in ours too. We believe deeply in the open-source ecosystem and strive to support—not replace—existing tools and communities.

Apply now >

This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.

Next step

Apply now.

Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.

Did you apply?Let us know, and we’ll help you track your application.

Continue on the employer website

Protect your personal information and never pay to secure an interview or job offer. .

Log in to save
One quick step before you apply

Sign in to continue.

Sign in or create a free account to continue to the employer's application.

Applying is free. After signing in, return to this job and select Apply Now.
Add alert
Jobs Talent AI Tools Salaries
Menu