The opportunity
We're looking for a SDK Engineer - Python to join our SDK team and own how developers talk to Supabase from Python. You'll work closely with the rest of the SDK team, our Auth, Realtime, Storage, PostgREST, Functions, CLI and Docs teams, and the open-source community, helping us…
What you'll do
Build and evolve our Python SDK across database, auth, storage, realtime and: functions, with both sync and async APIs that feel natural in Python.
Start new things. Alongside the maintenance work, find what's missing, make: the case for it, and build it. Nobody will hand you the list.
Work in the open. Triage inbound issues, review and shepherd outside: contributions, keep CI and release automation healthy, and hold a clear, kind line on scope.
Own the typing experience. Make the SDK fully typed and checker-friendly, so: autocomplete and static analysis stay correct in real codebases.
Keep us honest across environments. Multiple Python versions, sync and async: frameworks, workers, serverless and notebooks — with dependency ranges that don't fight our users' projects. 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 functions: ship a change, make sure the SDK reflects 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 SDK legible to AI coding agents , which are now a major consumer of it.
- Know modern Python typing deeply. You use generics, protocols, overloads and: TypedDict as design tools, run strict type checking, and fix type errors without reaching for Any.
