A technical foundation, kept current. A real background in Postgres / SQL, Linux, sysadmin, backend or platform engineering, DevOps, or database work. You may be a few years out of deep hands-on work, and that’s okay as long as you've done something deliberate to keep your edge (side project, homelab, pairing on cases, OSS) so you can still read a stack trace and a query plan without bluffing
Supabase-adjacent fluency. Comfortable reasoning about auth flows, storage, serverless functions, realtime systems, or vector workloads. If you haven't used Supabase, that's fine. You should be the kind of person who'll have it running locally in a weekend
Management experience. You've led a technical team before: support, SRE, platform, engineering, doesn't matter which. You know how to give feedback that lands, how to run a 1:1 that isn't a status update, and how to hire well
Operational instincts. You're comfortable with metrics (FRT, MTR, CSAT) but you don't let them run the team. You know when a number is telling you the truth and when it's hiding the real story
Writing. You can write clearly in English under pressure: to a customer, to an engineer, to a CEO. Most of what support produces is prose; we take it seriously
Customer instinct. You like users. You're curious about what they're trying to do, not just what they're stuck on. You believe good support works itself toward making itself smaller, by making users more capable
Familiarity with JavaScript / TypeScript and one of the major frontend frameworks (React, Vue, Svelte), plus some Node
Experience supporting a developer-facing product, an open-source project, or a platform with a public GitHub presence (Issues, Discussions)
You've been on the other side of the table (written software, run infra, been the person paged at 3am) and that shapes how you partner with the engineers you'll work alongside