Support Engineer (EMEA - Weekends)

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 4 10-hour shifts, permanently covering weekends during EMEA Hours: 08:00-18:00 UTC
• We are primarily looking for someone in Europe, Africa, or Middle Eastern timezones for this shift.
• This position covers Friday → Monday based on the above UTC times, so this may vary slightly for your specific timezone.

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.