Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Supabase

Software Engineer - Turso

  • Seen live on Supabase's site today
  • Mid level
  • Remote
Pay
Not stated
Location
Remote, Global
Open for
11+ days
First seen
Oct 24, 2026
Apply on Supabase's site (opens in a new tab)

Posting record

No flags

Open 11+ days

The posting's record, oldest first
  1. Supabase's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Supabase, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

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 Software Engineer to join our Turso core database team and help bring forward the future of agentic databases. Turso is both an Open Source database that replaces SQLite—with an ongoing project to also support the Postgres interface—and a Cloud offering where users can create databases on demand. You’ll work closely with customers and other teams at Supabase to build the future of what databases look like in a world where users and agents are creating millions of databases a day.

This role is ideal for someone who thrives in async, fast-paced environments and is excited about building database technology tools that scale to billions.

What You’ll Be Responsible For

  • Driving the progress of the Turso Open Source database, in particular the Postgres compatibility layer.
  • Making sure code works , and never breaks, and putting the systems and guarantees in place for that to happen.
  • Maintaining the Turso Cloud operations, including the Cloud API and data plane operations.
  • Improving the scalability of the Turso Cloud operations to support a 100x larger number of databases

You Might Be a Good Fit If You

  • Have written databases before, and/or other high-stakes low-level systems like Hypervisors, OS Kernels, storage devices, etc.
  • Have experience working with remote teams and Open Source communities.
  • Have a passion and experience for correct systems that work, and have the experience in the tools to make that happen: Deterministic Simulation Testing, formal verification methods, fuzz and differential testing, etc.
  • Have experience deploying, operating and debugging large scale software systems in production in cloud environments such as AWS & Kubernetes
  • Have experience improving the observability, reliability and performance of complex cloud systems.
  • Are comfortable working in Rust.
  • Are comfortable with LLM-assisted development and evals.
  • Are comfortable working with Embedded databases.
  • Communicate clearly across both technical and non-technical audiences.
  • Are energized by solving real-world problems for developers
  • Are comfortable navigating ambiguity and moving quickly

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.

Something wrong with this posting?