Synced from Ashby · Aug 5

SDK Engineer

SupabaseRemote, GlobalPosted Aug 5, 2026
Software EngineerSenior
Apply now - freeSave & get alerts

Mirrored from Supabase's own Ashby careers system · refreshed hourly

59
Other open Supabase roles
Aug 5
Posted
Ashby
Applicant system
Job description

About Supabase

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.

About the Role

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.

Our JS/TS SDKs are the front door to the platform: database queries, auth, storage, realtime subscriptions and edge functions, used by a very large number of developers and by most of the AI coding tools building on Supabase today.

This is a library-authoring role, and the work happens in the open: public repos, public issue trackers, and API decisions whose consequences are permanent. The type system here is a design surface rather than a formality. If you get satisfaction from an inference that Just Works, from a migration guide that saves people an afternoon, 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.

What You'll Be Responsible For

  • 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.

  • 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.

You Might Be a Good Fit If You

  • 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.

What We Offer

  • 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.

About the Team

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.

View original posting on Ashby

What applying to Supabase usually looks like

Based on publicly available information, candidates applying through ashby for roles at Supabase can generally expect an online application followed by a recruiter screen, though this may vary by role. The process may include multiple stages, potentially covering technical assessments, take-home exercises, or portfolio reviews for design and engineering positions, as well as conversations with hiring managers or team members. For technical roles like backend-engineer or security-engineer, candidates might encounter coding exercises or system design discussions, while roles such as account-executive or marketing-manager may emphasize case studies or role-specific scenarios. Communication is typically handled through the Ashby platform, and response times vary depending on the team and volume of applicants. Candidates should be prepared for a mix of asynchronous and live interview formats, and it is commonly recommended to research the company's product and culture beforehand.

Based on publicly available information. LandEarly does not verify interview process details.

Land this one early - before the req fills.

LandEarly tailors your resume and screening answers to each posting, submits within minutes of a role going live, and tracks every application in one place.

Free to start · No credit card · Cancel anytime

Keep exploring

What this role pays, where else it is open, and how to write the application.

SDK Engineer
Supabase · Remote, Global
Apply