The posting explicitly states 'Fully Remote' and 'We hire globally' with no geographic restrictions, no timezone requirements, no language mandates beyond English, and no work authorization gatekeeping. The target user (anglophone Caribbean resident, English-only, UTC-5, no US/EU work auth) fits squarely within the stated scope.
“There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.” Physical presence — Confirms fully remote work with no office or relocation requirement.
“We operate asynchronously and trust you to manage your own time.” Timezone — Async-first culture with no stated timezone overlap window eliminates timezone gatekeeping.
“We hire globally. We believe you can do your best work from anywhere.” Work authorization — No mention of US or EU work authorization requirements; global hiring language indicates openness to any jurisdiction.
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!
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.
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.
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.
Straight to the employer's own application — no middleman.
Tell us and we'll mark Supabase as a company that has actually hired in the Caribbean. It's the most useful thing on this board and it only exists because people report it.
I got hired here →
