About the Role
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 OWN
- Ship 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.
WHAT YOU’LL BRING
- 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