The opportunity
We're looking for a SDK Engineer - JavaScript to join the SDK team and own a core part of how developers talk to Supabase from JavaScript and TypeScript.
What you'll do
Build and evolve our JavaScript/TypeScript 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.
What they're looking for
- 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.
