The last time you applied for an engineering job, something screened you before a human did. A timed puzzle, a take-home you did on a Sunday, a recruiter reading for keywords. Supabase hired its first 32 developers without any of it, and did not send a recruiting email until the company was more than two years old.

That is co-founder Ant Wilson's own account, published on their blog in 2022, and the reason it worked is the same reason the company exists at all: the people they hired had already shown up in the repo.

Wilson is blunt about what that replaced. "One of the biggest complaints developers make while looking for their next gig is having to solve LeetCode problems or do take-home tests in the interview process," he wrote. If someone has been contributing to your open source project for months, you have already seen how they write code, how they take feedback, and how they behave in a thread at midnight in a timezone you do not share. The interview was the contribution history.

This is the second Remoet Company Spotlight: one company at a time, picked from the companies our users star, read closely. How they build and how they hire, nothing else. Companies don't pay for spotlights; we choose them from what our users star.

The bet was Postgres, and the bet was the whole company

Supabase started in January 2020 as an open source alternative to Firebase, a sentence that undersells the actual decision. Plenty of people wanted a friendlier backend. Copplestone and Wilson decided it should be a database everyone already had, with the good parts of the ecosystem stapled on and none of it hidden.

That put them in an unusual position: the thing their company depended on, they did not own. Postgres belongs to nobody (which is either the best or the worst property of it, depending on the week you are having), and the tools that turn it into a product (an HTTP layer, an auth layer, extensions for search and vectors) belong to whoever maintains them.

Five months in, they did the thing that would become the pattern. In June 2020, Paul Copplestone announced that Steve Chavez, "a maintainer of PostgREST, one of the core tools which makes Supabase possible," had joined the company.

Read that again with the hiring lens on. Their early move was not to hire someone who could build an HTTP layer for Postgres. It was to hire the person already maintaining the one they were using.

Buying the ecosystem one maintainer at a time

Six years later the pattern has not changed, it has just gotten more expensive.

Supabase has put more than $250,000 into sponsoring open source projects it depends on: PostgREST, PGroonga, pgsodium, OrioleDB, Elixir. Their main repo has passed 106,000 GitHub stars with more than 1,500 contributors. And they recruited Sugu Sougoumarane, who co-created Vitess at YouTube, to build Multigres: the same idea as Vitess (sharding, pooling, failover, backup orchestration) aimed at Postgres instead of MySQL, released as Apache 2 rather than kept in the product.

And it is not only history. Their openings today still recruit straight out of the upstream community: one asks for an existing PostgreSQL core contributor in as many words, another points candidates at a public contributor-qualifications document, and several ask for ex-founders. The 2022 essay and the 2026 job ads describe the same strategy.

There is a version of this that is just good marketing. We do not think that is what this is, and the tell is in our own data.

Of the 29 open roles we track at Supabase in July 2026, 25 list Postgres or one of its satellites in the stack.

Be careful with that denominator, because we were: we only track technical roles, so this is 25 of 29 engineering, design and solutions openings, not 25 of the whole company. The marketing and finance hires are invisible to us and always were.

Even inside that narrower frame it is a strange shape. At most infrastructure companies the database is what the platform team worries about while everyone else consumes an API. At Supabase it turns up in the support engineering and solutions architect roles too, where you would expect product knowledge to be the qualification and instead the qualification is the database. Someone answering a support ticket there is answering a Postgres question.

Only four skip Postgres entirely, and they are the work you would expect: two design roles, mobile, and (with some irony) deployment tooling, which is the layer that wraps Postgres without ever having to name it.

That is the part their about page will not tell you: the org chart and the Postgres ecosystem have started to be the same diagram.

No offices, no geo-adjusted pay, no opinion about your calendar

The careers page states it without hedging: "We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices." No headquarters to be near, no hub city that quietly matters more. Two policies make that more than branding.

The first is pay. "We don't do geo-adjusted pay," they wrote in 2023, adding that "you should get the same pay for the same job, geo-adjusted pay always seemed a bit bizarre." This is the road not taken by most remote companies, including PostHog, whose public salary calculator multiplies by a location factor. Neither approach is obviously right (the location factor is what lets a company hire widely without wrecking its budget) but they produce very different companies, and Supabase picked the expensive one on principle.

The second is time. "We don't care when you work." Async by default, written by default, with the coordination cost paid in documents instead of meetings.

Our data backs the remote claim up harder than most companies could survive. Every single open role we track carries a remote policy. Zero onsite, zero hybrid, as of July 2026. Of the 29, 23 are open to anywhere and 6 carry a regional restriction, usually for customer coverage or compliance reasons. That ratio is the part worth keeping: a company can be honestly all-remote and still region-lock a fifth of its jobs, and most all-remote companies lock a good deal more than that.

What the growth number hides

Supabase raised $500M at a $10B pre-money valuation in June 2026, and the figures in that announcement are the kind that get screenshotted: nearly 10 million developers, database launches up 600% in a year, more than 60% of new databases created by AI tools rather than by humans (make of that last one what you will, we are still deciding).

The hiring shape underneath is quieter and, we think, more informative. Of the 29 roles we track, 16 are senior and exactly one is junior.

That is the sharp edge of the open source hiring strategy. Hiring from your contributor pool is wonderful if you are already in it, and a closed door if you are not, because the qualification is a body of public work that takes years to build and nobody pays you to build it. Supabase is not unusual here (junior roles are scarce everywhere, around 4.6% of everything we tracked when we counted in June) but it is a company whose front door is unusually open and whose actual entrance is narrow.

And here is the hole in this piece, which we would rather point at than paper over. The upstream hiring is still visible in their current openings, but those are specialist roles, the ones where the only qualified people are already in the codebase. That is a narrower claim than the one the 32 number implies. Whether the repo is still a general way in at 350 people, or has become the route for database internals and a story about how the company used to hire for everything else, our data cannot tell you. Job posts do not record how somebody got noticed.

If it is still the route, it is the same one 32 people took before recruiting existed here. The repo is public. It always was.

Frequently asked questions

What is Supabase's tech ecosystem?

Postgres first, with TypeScript across the product surface and Rust and Go in the infrastructure. The full tech stack, tag by tag, lives on the Supabase listing.

Does Supabase hire remote workers?

Yes, exclusively. Supabase has no offices and hires globally, with a team spread across more than 60 countries. Every open role we track is remote (July 2026), though roughly a fifth carry a regional restriction, so check the individual role.

Does Supabase pay the same salary everywhere?

Yes. Supabase does not use geo-adjusted pay, stating that the same job should earn the same pay regardless of where you live.

Does Supabase hire junior developers?

Rarely. Of the 29 open roles we track in July 2026, one is junior and 16 are senior. Historically their strongest route in has been contributing to their open source projects first.

One company at a time

Companies don't pay for spotlights; we choose them from what our users star.

Supabase's full tech stack and all of its open roles are live on the Supabase listing. Star the company and you (or your agent) will know when new roles open up.

Got a company that deserves the next one? Make the case on Discord. We are doing these one at a time, so the bar is high.