Similar Jobs
Team Frontend within Supabase owns tooling for the marketing/docs website and the core product called “Studio” Its used by millions of developers around the world building insanely cool applications. We live and die by user feedback and relentlessly address issues every day to make the product better!
What You’ll OwnShip products 0→1 and then earn the next version from users. You’ll take features from a blank editor to real users in production, then use what you learn (support threads, usage data, direct conversations) to decide what to build next. We want someone who has done this before: launched something, watched real people use it, and improved it on the strength of that feedback rather than a spec handed down from above.
Own the quality pipeline, not just the feature. In a world where an agent writes a large share of the code, fast, the CI is what keeps that speed safe. You’ll build and tighten the layered checks that let us move quickly without breaking things: type safety at the boundaries, lint and format, unit and component tests, contract tests against our APIs, accessibility, visual regression, and bundle-size budgets, so a red check tells you (or the agent) exactly what to fix before anything reaches users.
Make sure a bug caught once is caught forever. When something slips through, you don’t just patch it. You add the check that would have caught it, at the cheapest stage that can, so the same regression can’t happen twice.
Work end-to-end and in the open. Frontend UI, the API contracts it depends on, preview deploys, observability. You’ll operate autonomously across the stack and do it publicly, in a codebase thousands of developers read and contribute to.
A track record of taking a product from 0→1. You’ve launched something real, put it in front of users, and iterated based on how they actually used it, ideally something you can point us to.
Deep frontend fundamentals with strong React. TypeScript and React, plus a real understanding of the modern landscape (SSR, streaming, server components, edge)
A genuine quality-and-tooling mindset. You treat tests, types, and CI as tools that let you and AI agents move faster, not as a tax. You have opinions about where a check should run and what it’s worth, and experience wiring up pipelines with tools like Vitest, Playwright, MSW, or equivalents.
Comfort working with AI coding agents: reviewing what they produce, tightening the architecture where they overreach, and giving them the guardrails to verify their own work.
Autonomy and async communication. You manage your own time, communicate clearly in writing, and thrive without someone assigning you tickets.
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.
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.
