SDK Engineer - JavaScript

Build and evolve our JS/TS SDKs.

Start new things. Alongside the maintenance work, you're expected to find what's missing, make the case for it, and build it. Some of what we ship next doesn't exist yet, and nobody will hand you the list.

Work in the open. These are public repos: you'll triage inbound issues, review and shepherd outside contributions, keep CI and release automation healthy, and hold a clear, kind line on scope.

Own the type experience. Keep generated database types flowing correctly through the client APIs so autocomplete and inference stay correct in real codebases.

Keep us honest across runtimes. Node, Deno, Bun, browsers, Cloudflare Workers, React Native/Expo, including dual ESM/CJS publishing and types that resolve correctly under every module resolution mode. Test it, don't assume it.

Work on realtime. Long-lived WebSocket connections, reconnection, and subscription and presence semantics.

Track the platform. When auth, realtime, storage, postgrest or edge-runtime ship a change, make sure the SDKs reflect it, and that we say so in the changelog.

Design in public. Write the RFCs, migration guides, release notes and docs. Treat a breaking change as a deprecation path plus a migration story, not a version bump.

Make our SDKs legible to AI coding agents , which are now a major consumer of them.

Expert-level TypeScript. You use generics, conditional and mapped types as design tools, you can explain why an inference breaks.

You've authored or maintained a published library with a public API and consumers outside your own company. You know what it costs to change something people depend on.

You've worked on open-source projects and know the maintainer side of them. Issue triage at volume, reviewing outside PRs, release automation, changelogs and semver, security reports, and saying no to a feature request without losing the person who asked.

npm packaging fluency: dual ESM/CJS builds, export maps, type resolution, semver discipline, and the failure modes consumers actually hit.

Testing as a habit: unit, type-level and end-to-end against a real stack. Every fix comes with a regression test.

Strong written communication. Design docs, changelogs and issue replies are a large part of the output here, much of it public, and we're async by default.

Real autonomy: you find the important work, scope it, ship it, and say what you didn't do.

Communicate clearly across both technical and non-technical audiences

Have experience in async or globally distributed teams

Are energized by solving real-world problems for developers

Are comfortable navigating ambiguity and moving quickly

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.