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
Auth, written in Go (server) and with client libraries for TypeScript, SSR and for other frameworks and technologies, is one of the most popular products in the Supabase stack. We are seeking someone to help us build new and maintain existing Auth features.
What you’ll be responsible for:
Own the performance, reliability, and scalability of the Auth server across Supabase's infrastructure.
Plan and execute safe database migrations across a large fleet of Postgres instances.
Build and improve observability: metrics, tracing, alerting, and dashboards to keep the system healthy at scale.
Collaborate with platform and infrastructure teams on deployment orchestration, deployment pipelines, and AWS resource management.
Contribute to the evolution of Auth's architecture with a focus on operational excellence and long-term maintainability.
Write and review RFCs as part of our development process.
Collaborate with engineers across Supabase to ensure a seamless experience for developers using our tools.
You might be a good fit if you:
(Required) Have 4+ years of professional experience writing and shipping Go in production.
(Required) Have hands-on experience building and operating services at significant scale.
(Required) Have strong relational database experience (Postgres or MySQL); Postgres experience is a bonus.
Have deep understanding of systems-level concerns: memory management, concurrency patterns, and compute resource optimization in Go.
Have experience with Kubernetes and AWS (or comparable cloud platform) in a production setting.
Have solid grasp of observability practices — metrics, distributed tracing, structured logging, and alerting (e.g., Prometheus, Grafana, OpenTelemetry).
Have experience managing database schema migrations safely at scale.
Are familiar with multi-tenant architecture patterns and the operational challenges they introduce.
Have authentication domain experience or interest is a plus, but not required.
Have good technical writing skills (RFC process is an important part of making changes to the Auth product and related infrastructure).
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.
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.
Hiring Process
We keep things simple, async-friendly, and respectful of your time:
Apply – Our team will review your application.
Intro Call – A short video chat to get to know each other.
Interviews – Up to four calls with:
Team Leads
Future teammates
Someone cross-functional from product, growth, or engineering (depending on the role)
Someone from our leadership/founding team
Decision – We may follow up with a final question or go straight to offer.
All communication is remote and we aim to move fast.