Product Engineer - Auth

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:

• Designing and implementing secure, scalable authentication features in Go and TypeScript.
• Working across the stack: from server-side protocols to client-side libraries for frameworks like Next.js.
• Contributing to the evolution of our Auth architecture, including support for OAuth, OIDC, SAML, and other protocols.
• Writing and reviewing RFCs as part of our product development process.
• Collaborating with engineers across Supabase to ensure a seamless experience for developers using our tools.
• Supporting the community and respond to developer feedback on GitHub, Discord, and other channels.

You might be a good fit if you:

• (Required) Have 5+ years of Software Development experience in a professional setting.
• (Required) Have 2+ years of professional experience working on an authentication system (implementing protocol support, maintenance at scale).
• Have strong knowledge of web technology fundamentals (cookies, sessions, JWT, HTTP, browser APIs).
• Have good knowledge of and deep interest in authentication security (passwords, protocols such as OAuth, OIDC or SAML, cryptography fundamentals such as hash functions, signatures and ciphers).
• Have experience working with multiple web frameworks like Next.js (or other SSR alternative in the JavaScript space) and traditional web frameworks like Ruby on Rails, Django, Laravel or equivalent (in any language).
• Have strong knowledge of Go and TypeScript (languages used daily) and Postgres.
• Have good technical writing skills (RFC process is an important part of making changes to the Auth product).

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.

• 280+ team members
• 55+ countries
• 20+ languages spoken
• $500M raised
• 500,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.

Hiring Process

We keep things simple, async-friendly, and respectful of your time:

1. Apply – Our team will review your application.
2. Intro Call – A short video chat to get to know each other.

3. 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
4. Decision – We may follow up with a final question or go straight to offer.

All communication is remote and we aim to move fast.