Data API Engineer
Supabase · Location not mentioned
What the posting says
Each fact carries its state:Statedfound in the postingConflictstwo statements disagree, both quotedNot mentionedthe posting does not say
- Employment typeStated
- Full time
- Work arrangementStated
- Remote OK
Not mentioned in this posting
“Not mentioned” means the posting does not say. It is not a no. You could ask the recruiter.
- PayNot mentioned
- The posting does not say
- ShiftNot mentioned
- The posting does not say
- ExperienceNot mentioned
- The posting does not say
- EducationNot mentioned
- The posting does not say
- Visa sponsorshipNot mentioned
- The posting does not say
Requirements, each with its sentence from the posting
These are the employer’s words. The index does not judge whether you meet them.
- No requirement has been itemised for this posting yet. The employer’s words are in the full posting below.
Read the full posting as the employer wrote it
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
We’re looking for a Data API Engineer to join our Data API Team and help improve the feature set, reliability and performance of our Data API, based on the PostgREST project.
This role is ideal for someone who thrives in async, fast-paced environments and is excited about building developer tools that scale to millions.
What You’ll Be Responsible For
Work on PostgREST’s PostgreSQL driver (based on Hasql) and remove bottlenecks and improve it’s performance.
Work on PostgREST development of new features and bug fixes, aligned towards the goal of a multitenant Data API.
Resolve incidents and escalated support issues, while also improving observability and performance.
Collaborate cross-functionally with other teams to debug and solve integration issues with the Supabase platform.
You Might Be a Good Fit If You
Strong Haskell skills with at least 3 years of experience.
Experience using the C language.
Solid knowledge of SQL and plpgsql scripting in PostgreSQL.
Strong track record of contributing to and engaging with open-source projects. Bonus points if you’ve maintained an open source project.
Strong experience with providing technical support to users with varying levels of technical expertise.
Experience with debugging applications under the Linux operating system.
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.
The posting text is reproduced as the employer wrote it; the index adds nothing to it.