Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles14360 openings
5825-5832 of 14360
Supabase
Free to start · No card · 5 credits the moment you sign up
Supabase is the Postgres development platform, built by developers for developers. We provide a complete backend solution including Database, Auth, Storage, Edge Functions, Realtime, and Vector Search. All services are deeply integrated and designed for growth.
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 make the Python SDK a library Python developers genuinely enjoy using.
Python developers reach Supabase from backend services, data pipelines, notebooks, and a growing number of AI agents and agent frameworks. The Python SDK is how all of them talk to the platform: database queries, auth, storage, realtime and edge functions, in both sync and async flavors.
This is a library-authoring role, and the work happens in the open: public repos, public issue trackers, and API decisions whose consequences last for years. If you get satisfaction from a type checker that catches the bug before your users do, from an async client that cleans up after itself, and from an issue tracker that isn't a graveyard, you'll like it here.
This role is ideal for someone who thrives in async, fast-paced environments and is excited about building developer tools that scale to millions.
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.
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.
Have authored or maintained a published library with a public API and users outside your own company. You know what it costs to change something people depend on.
Know the maintainer side of open source. 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.
Are fluent in asyncio and have opinions on how a library should serve both sync and async callers.
Know Python packaging for libraries: pyproject.toml, wheels, modern tooling, version support policy, and why libraries shouldn't pin their dependencies tightly.
Test as a habit: unit, type-level and end-to-end against a real stack. Every fix comes with a regression test.
Write well. Design docs, changelogs and issue replies are a large part of the output here, much of it public, and we're async by default.
Have 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
Bonus points if you: have run a major-version migration for a public package, know your way around JWT/OAuth, have built integrations for AI agent frameworks, or have generated idiomatic clients from a schema.
Fully Remote
We hire globally. We believe you can do your best work from anywhere. There are no Supabase offices, but we provide a WeWork membership or co-working allowance you can use anywhere in the world.
ESOP
Every team member receives ESOP (equity ownership) in the company. We want everyone to share in the upside of what we’re building together.
Tech Allowance
Use this budget to set up your ideal work environment—laptop, monitor, headphones, or whatever helps you do your best work.
Health Benefits
Supabase covers 100% of health insurance for employees and 80% for dependents, wherever you are. Your wellbeing and your family’s health are important to us.
Annual Off-Sites
Once a year, the entire company gathers in a new city for a week of connection, collaboration, and fun. It’s a highlight of our year.
Flexible Work
We operate asynchronously and trust you to manage your own time. You know what needs to be done and when.
Professional Development
Every team member receives an annual education allowance to spend on learning—courses, books, conferences, or anything that supports your growth.
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.
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.