Who We Hire at Supabase

Summary

Supabase describes the hiring traits and operating model it believes support its growth, arguing that people matter more than methodology. It looks for extreme asynchronous effectiveness, egoless execution, continuous incremental improvement, a bias toward immediate action, ambitious problem-solving, and a founder mindset; seniority does not exempt anyone from independent-contributor work, self-management, or maintenance. The 60-person team spans 25 countries, uses meetings as a last resort, and gives autonomous product teams access to shared metrics, user feedback, and equity through an ESOP. Teams are organised around products such as Postgres, Auth, Storage, Realtime, and Functions, while cross-cutting groups consult rather than merely receive delegated tasks. Three-month product cycles set ambitious goals, and Kaizen Weeks focused on QA, documentation, and performance help address technical debt and incorporate improvements into ongoing workflows.

Takeaways

1. 1

   Major projects can proceed from inception through implementation, marketing, and launch without a synchronous meeting; meetings are treated as a last resort across a 60-person team in 25 countries.

2. 2

   Cross-cutting teams such as Front End, QA, and Docs act as consultants to product teams, while feature teams remain responsible for their own documentation.

3. 3

   Three-month product cycles replace continuous two-week sprint loops, with Kaizen Weeks used to address QA, documentation, and performance and embed improvements into regular workflows.