Supabase

supabase.com · 46 open roles in the last 6 months · hiring in 2 countries

Loading…

Supabase appears to be investing in a new agent-oriented database and internal AI operations, while strengthening the cloud infrastructure and developer products needed to support its growing platform.

Inferred from 52 job postings from the last year, with recent ones weighted more · updated 21 Oct 2026. Not a statement by the company.

What changed recently

The newest postings make two newer efforts more explicit: Supabase Spark is described as an agentic database intended to support billions of databases, and a central team is being formed to run AI agents across internal workflows. Alongside those bets, recent roles add dedicated SRE, FinOps, cloud-governance and compute capacity work, pointing to more focus on operating cost and reliability at scale.

Scalinghigh confidenceMostly new this month

Hardening cloud operations, capacity and cost

1m 53m 86m 81y 8

Recent infrastructure roles address reliability and economics across a platform managing millions of databases: dedicated SRE practices, multi-region compute, capacity planning, cloud governance and cost attribution across AWS and GCP. The work includes keeping compute supply ahead of demand, improving service SLOs, and giving engineering and finance trustworthy cost and margin data.

A new SRE role says reliability efforts are being consolidated into a dedicated practice.
Two recent FinOps roles focus on cloud savings, cost attribution and chargeback/showback across AWS and GCP.
Compute roles describe multi-region provisioning and a single view of capacity across millions of databases.

Scalinghigh confidenceMostly new this month

Extending the developer platform and its core products

1m 53m 66m 61y 7

Product and engineering roles continue to evolve Supabase’s Database, Auth, Realtime and platform surfaces rather than focusing on a single product. Recent work includes a Python SDK with typed sync and async APIs across database, auth, storage, realtime and functions—explicitly serving AI agents—as well as Auth flows for agents, passkeys, MFA and multi-tenant access.

The Python SDK posting names AI agents as a major consumer and covers multiple Supabase services.
Recent product-manager roles own Auth and Realtime roadmaps and developer experience.
Deployment roles cover PostgreSQL and OrioleDB releases, while Branches work targets thousands of concurrent builds.

New betmedium confidenceMostly new this month

Growing partner-led reach and developer awareness

1m 43m 56m 61y 6

Recent go-to-market roles are building partner and creator channels: a new marketplace and referral program, AWS co-marketing for gaming, enterprise, startup and AI segments, and an in-house creator roster targeted at about 50 active creators in its first year. A Head of New Media role also takes direct ownership of Supabase and founder communications on X and LinkedIn.

The partner marketplace role explicitly describes an early-stage program.
The creator role aims to bring relationships currently managed mostly through agencies in-house.
AWS partnership postings connect co-marketing and sales to gaming, AI, enterprise and startup audiences.

New bethigh confidence

Creating an internal AI agent platform

1m 13m 26m 21y 2

Supabase is forming a central team to build an internal AI operating platform, with agent execution, orchestration, evaluation and observability. The stated six-month goal is 20 or more autonomous agents in production, with evaluation suites, and at least three teams outside the core group running agents built on the platform.

A new director-level role and an earlier AI Platform Engineer role describe the same internal platform effort.
The latest posting gives concrete adoption goals: 20+ production agents and use by three or more other teams.
Evaluation, governance and regression detection are explicit parts of the platform.

Head of AI Native OperationsDirector
AI Platform Engineer

Scalingmedium confidence

Adding technical support for larger and more complex customers

1m 03m 26m 31y 3

Supabase is adding more structured technical ownership for named accounts and paid Team and Enterprise customers. A TAM leadership posting describes coverage across roughly 120 named accounts and partner-mapped accounts, while a Customer Solutions Architect lead is tasked with scaling technical onboarding and proof-of-value support.

The TAM role describes a named-account book of approximately $33.1M ARR across 120 accounts.
The CSA lead role focuses on Team and Enterprise adoption and proof-of-value onboarding.
An EMEA account executive posting adds sales coverage for developer-first startups.

New betmedium confidence

Building Spark for agentic database workloads

1m 13m 16m 21y 2

Spark is presented as a new database initiative designed to support billions of databases, with millions created daily; its engineering manager role is a fresh leadership hire for the effort. An earlier founding-role description specifies a lightweight Rust platform using an embedded SQLite-based engine with a Postgres-compatible SQL layer, sub-second provisioning and a footprint small enough for a sandbox.

The last-month Engineering Manager - Spark role is tagged as a new initiative.
The earlier Supalite posting calls itself a founding role on a brand-new team.
Postings describe both scale ambitions and concrete Rust, SQLite, and Postgres-compatibility design details.

Engineering Manager - SparkManager
Supalite Engineer

Where they are expanding

London, UK — A London-based Developer Relations Engineer posting is one of three recent DevRel roles with named hubs, alongside New York and San Francisco, suggesting added localized developer-community presence rather than only global-remote coverage.
New York, NY — A New York-based DevRel role appears alongside new named-hub DevRel postings in London and San Francisco, pointing to a deliberate effort to place developer-facing work in multiple communities.

Questions to ask in a coffee chat

How is the Spark team deciding which workloads to prioritize first, given its goal of supporting very large numbers of small databases?
What kinds of internal workflows are the first candidates for the shared agent platform, and how do teams use its evaluation and observability tools?
How are SRE and product teams sharing ownership of SLOs and incident follow-up as the dedicated reliability practice takes shape?
What are the hardest trade-offs in making cloud cost attribution useful to engineering teams without slowing infrastructure changes?
How are the Auth and Realtime roadmaps changing as more developers build AI-agent-driven applications?
How do the new marketplace and creator programs fit with Supabase’s existing developer-community and AWS partnership work?

What this can't tell you

Job postings reveal intended work and stated goals, but not how much engineering time or budget each initiative will ultimately receive.
Spark’s scale figures and the internal agent platform’s adoption goals are targets in postings, not evidence that those outcomes have already been achieved.
The data does not show how much of the core Database, Auth, Storage, Realtime and Edge Functions work is new development versus ongoing maintenance.