Supabase's Remote Hiring in June 2026

Supabase is aggressively expanding with 2 technical roles open for global remote work, including opportunities for engineers worldwide. They're looking for SDK Engineer - Kotlin and Multigres Engineer — both rare and highly specialized positions.

TL;DR — key points:

• Spotify — Fullstack Engineer - Generative UI Platform, salary not disclosed, remote.
• Notion — Staff Frontend Engineer, salary not disclosed, remote.
• World Data Lab — DevOps Engineer (m/f/d), salary not disclosed, remote.
• Supabase — SDK Engineer - Kotlin, salary not disclosed, remote.
• Tailor — Product Designer, salary not disclosed, remote.

TL;DR for the impatient:

• 🛠️ 2 roles open: Kotlin SDK Engineer and Multigres Engineer (distributed database)
• 💰 Estimated salary: $70,000–$100,000 USD/year for mid-level (global range, anecdotal Levels.fyi)
• 🚀 Tech stack: Kotlin, Postgres, distributed systems, cloud infrastructure
• 🌍 Remote-first since inception, not just because of the pandemic
• ⚠️ Hiring process intense: technical deep dive + real-world problem solving

What is Supabase and why are they attractive?

Supabase is an open-source Firebase alternative built on Postgres. Unlike companies that just jumped on the remote bandwagon, they've been remote-first from the start. According to CEO Paul Copplestone, their team is spread across 20+ countries without a headquarters — truly decentralized.

What's interesting is that during the global tech layoffs (38,242 job cuts in the US in May according to Challenger, Gray & Christmas), Supabase is still actively hiring. This is a strong signal that their product is growing or they've received new funding.

What roles are currently open?

1. SDK Engineer - Kotlin

This position isn't just a "Kotlin developer" role. They're looking for engineers who can:

• Build and maintain Kotlin SDK for Supabase
• Optimize performance and developer experience
• Collaborate with the open-source community
• Create sample implementations and documentation

The tech stack is typical Kotlin/JVM ecosystem: Gradle, Ktor, coroutines, plus Postgres integration. They're looking for someone who truly understands how Android/Kotlin developers work and their pain points.

2. Multigres Engineer

This is even more niche — a role for building a distributed database system based on Postgres. Requirements include:

• Deep experience with Postgres internals
• Knowledge of distributed systems (consensus algorithms, replication, sharding)
• Cloud infrastructure (AWS, GCP, or Azure)
• Performance optimization at scale

Both roles aren't for juniors. From the job descriptions, they're looking for mid to senior level engineers with proven work in these specific areas.

How much does a remote engineer earn at Supabase?

This is the tricky part. Supabase doesn't publish salary ranges in their job descriptions. But based on various sources and industry benchmarks, we can estimate.

According to the Stack Overflow Developer Survey 2025, the median salary for developers working remotely for foreign companies is $45,000–$75,000 USD/year. However, for specialized roles like those at Supabase, the range can be higher.

From anecdotal data at Levels.fyi for remote positions, mid-level engineers at open-source companies typically fall in the $70,000–$100,000 USD/year range. Seniors can exceed $120,000+, especially for rare expertise.

*Assuming local salary ~$10,000/year

But remember: these are rough estimates. Actual offers depend on negotiation skills, experience, and how well you perform in technical interviews.

Supabase's hiring process: what to expect

Based on the experiences of engineers who've applied to Supabase, the process typically includes:

1. Initial screening — CV and portfolio review
2. Technical interview — deep dive into specific expertise (Kotlin or database)
3. Take-home assignment — real-world problem related to the role
4. Final interview — with engineering lead or C-level

What makes their process different is the strong emphasis on open-source contribution and practical problem solving. They care more about what you can build than just solving leetcode problems.

Benefits of working at Supabase

• Direct impact: Their product is used by hundreds of thousands of developers worldwide. Your work is visible and has real-world impact.
• Strong engineering culture: Small team but highly technical. Lots to learn from top engineers.
• True remote: Not just hybrid pretending to be remote. Entire team is distributed across timezones.
• Open-source focus: Contributions to the community and open-source portfolio are highly valued.

Drawbacks and contrarian take

I have to be honest: Supabase isn't for everyone.

First, because they're a relatively young startup (compared to Firebase or AWS), stability might be a concern. Although they've raised $80 million in 2025, startups always carry some risk.

Second, compensation might be lower than FAANG companies. If you're looking to maximize salary, you might be better off applying to Spotify or Notion which typically pay more.

Third, work-life balance might be tricky. During startup phases, work hours can be longer. If you prefer strict 9-5 hours, established companies like GitLab might be a better fit.

Tips for engineers applying

1. Highlight open-source work — Supabase highly values open-source contributions. If you have a GitHub portfolio with stars/reputation, that's a big plus.
2. Prepare for deep technical discussion — It's not just algorithms, but real-world problem solving in your specific area.
3. Show community involvement — They're looking for engineers who can engage with the community, not just code monkeys.
4. Be ready for async communication — Since it's fully remote, communication is mostly through Slack, GitHub issues, and documentation.

How does Supabase compare to other remote companies?

From the table above, it's clear that Supabase offers competitive compensation for regional hires, although it's slightly below unicorns like Notion or Spotify.

What to consider before applying

Before you send your application to Supabase, ask yourself:

1. Are you comfortable working fully asynchronously? This means fewer meetings, more written communication, and needing to be proactive.
2. Does your expertise match what they need? Don't apply if you only have "I want a remote job" without specific skills.
3. Are you comfortable with a startup environment? Priorities can change quickly, scope can expand, and stability is less predictable.

If you read our article about Drake Maroc, you'll see the same pattern: companies hiring specialized roles are typically looking for exact fits, not generalists.

FAQ

Does Supabase pay in USD?

Typically, remote companies pay in USD via TransferWise, PayPal, or direct wire transfer. The rate follows market conditions, not a fixed nominal. Make sure to negotiate a package that includes tax obligations in your country.

How long is the hiring process at Supabase?

Usually 3-4 weeks from application to offer. Because their team is distributed, scheduling interviews requires coordination across timezones.

Is fluent English required?

Yes. All internal communication is in English, including documentation, code reviews, and async discussions. The minimum level should be able to communicate technical concepts clearly.

Are there any relocation options?

Supabase is fully remote without physical offices, so relocation isn't applicable. They hire based on skills, not location.

So, is it worth applying to Supabase?

If you:

• Have expertise in the Kotlin ecosystem or Postgres internals
• Are comfortable with open-source and collaborative development culture
• Are ready to work asynchronously with a global team
• Aren't purely looking to maximize compensation

Then yes, Supabase could be a great opportunity. The impact is significant, the learning opportunities are massive, and the brand is solid in the tech community.

But if you're still junior or looking to maximize stability, you might want to consider more established companies first.

Action step: If you feel you qualify, don't just apply through job portals — find Supabase engineers on Twitter/LinkedIn, mention your relevant portfolio, and ask for a referral. In startups, warm introductions are still far more effective than cold applications.