Support Engineer (AMER)
- Status
- Open
- Remote policy
- Not stated
- Employment type
- Full-time
- Salary
- Not stated
- Categories
- Technical Support
- Source
- jobicy
- First observed
- 2026-08-21 15:34 UTC
- Last seen
- 2026-10-22 09:06 UTC
- Source claims posted
- 2026-10-22 04:40 UTC
- Consecutive misses
- 0 of 10
What the posting says
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.
We are seeking Support Engineers to provide world-class developer support for anyone experiencing issues or seeking guidance when using Supabase. The support team is globally distributed with a strong focus on minimizing time to fix, and works closely with the product engineering and growth teams.
You will:
Provide initial and timely responses to all support cases for a variety of topics, from billing or pre-sales requests to optimization or implementation questions.
Triage support cases including directing users to previous answers, code examples, documentation, or escalating to specific technical or business team members.
Monitor multiple feedback channels, e.g. Github Issues & Discussions (check them here: https://github.com/supabase/supabase/issues).
Identify where internal tooling might be developed or obtained to improve support efficiency.
Reproduce issues, create test cases and improve test coverage, if you have experience with testing.
You are:
Experienced in customer support, with 3+ years of experience providing developer support to technical customers.
Proficient in SQL (ideally PostgreSQL). You feel comfortable with complex SQL queries. If you have a database administration experience, it’s a plus.
Excellent communication skills and fluency in English.
Skilled in using Linux/Unix operating systems and the command line.
Experienced working with GitHub Issues and Discussions.
Bonus points if you’re familiar with popular JavaScript frameworks like React, Vue, and Svelte and have some experience with Node.js.
Having a degree in Computer Science is a plus too.
Timezones & Logistics
It’s a full-time position with a required location in North American time zones (we don’t believe in sustainability of overnight shifts).
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.
~400 team members
60+ countries
20+ languages spoken
Over $1B raised (including our $500M Series F)
540,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.
Quality
- x Salary range stated weight 35%
- x Remote policy stated weight 20%
- + Location stated weight 15%
- + Organisation stated weight 15%
- + Publication date stated weight 15%
Based on 30 observation(s).
- ! Days open - concerningOpen for 61 days so far
- ! Reopen count - concerningReopened 2 times
- + Salary range removed after publication - fineSalary range has not been removed since publication
- + Salary range narrowed - fineSalary range has not narrowed since publication
- ! Missing/reappear cycles - concerningWent missing and reappeared 3 times
Timeline
-
*
#246307 2026-08-21 15:34 UTCPublished
-
o
#281288 2026-08-22 21:11 UTCNot seenMiss 1 in a row
-
o
#283251 2026-08-22 21:43 UTCNot seenMiss 2 in a row
-
o
#283516 2026-08-22 22:43 UTCNot seenMiss 3 in a row
-
o
#284891 2026-08-22 23:44 UTCNot seenMiss 4 in a row
-
o
#285163 2026-08-23 00:44 UTCNot seenMiss 5 in a row
-
o
#286744 2026-08-23 01:46 UTCNot seenMiss 6 in a row
-
o
#287293 2026-08-23 02:46 UTCNot seenMiss 7 in a row
-
o
#288599 2026-08-23 03:47 UTCNot seenMiss 8 in a row
-
o
#288846 2026-08-23 04:48 UTCNot seenMiss 9 in a row
-
o
#290571 2026-08-23 05:49 UTCNot seenMiss 10 in a row
-
x
#290572 2026-08-23 05:49 UTCClosed
-
^
#890653 2026-09-21 11:03 UTCReopened
-
~
#890654 2026-09-21 11:03 UTCModified
-
Posted at
2026-08-21 09:50 UTC->2026-09-21 09:50 UTC
-
Posted at
-
o
#893396 2026-09-21 13:06 UTCNot seenMiss 1 in a row
-
o
#894592 2026-09-21 14:08 UTCNot seenMiss 2 in a row
-
*
#896931 2026-09-21 15:09 UTCSeen againReappeared after 2 consecutive miss(es)
-
o
#945223 2026-09-23 13:29 UTCNot seenMiss 1 in a row
-
o
#946932 2026-09-23 14:29 UTCNot seenMiss 2 in a row
-
o
#948149 2026-09-23 15:32 UTCNot seenMiss 3 in a row
-
o
#950536 2026-09-23 16:32 UTCNot seenMiss 4 in a row
-
o
#951152 2026-09-23 17:40 UTCNot seenMiss 5 in a row
-
o
#952977 2026-09-23 18:42 UTCNot seenMiss 6 in a row
-
o
#954058 2026-09-23 19:43 UTCNot seenMiss 7 in a row
-
o
#955422 2026-09-23 20:44 UTCNot seenMiss 8 in a row
-
o
#956039 2026-09-23 21:47 UTCNot seenMiss 9 in a row
-
o
#957917 2026-09-23 22:48 UTCNot seenMiss 10 in a row
-
x
#957918 2026-09-23 22:48 UTCClosed
-
^
#1476874 2026-10-22 09:06 UTCReopened
-
~
#1476875 2026-10-22 09:06 UTCModified
-
Posted at
2026-09-21 09:50 UTC->2026-10-22 04:40 UTC
-
Posted at