Straight to the employer's own application — no middleman.
The posting explicitly states 'Fully Remote' and 'We hire globally' with 'no Supabase offices'. It is an employee role with no work authorisation requirement stated, no timezone overlap mandated, no language beyond English required, and no physical presence requirement. The target user meets all technical qualifications and geographic eligibility.
“Fully Remote” Physical presence — Clear statement of remote work eligibility with no in-office, hybrid, or relocation requirement stated anywhere in the body.
“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.” Geographic scope — Explicit worldwide hiring scope with no geographic restriction or country exclusion list.
“We hire globally.” Work authorization — No work authorisation requirement, visa sponsorship restriction, or citizenship mandate stated. Employee role with global hiring affirmed.
“We operate asynchronously and trust you to manage your own time.” Timezone — Asynchronous work model means no required timezone overlap window; UTC-5 Caribbean resident can work flexibly.
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're hiring experienced performance engineers to find and land performance wins across the Supabase stack — from the query optimiser to block device level, and across the network paths and cloud infrastructure that connect our distributed platform. This is a performance delivery role: real, measured improvements to our database, platform, and APIs as we scale toward enterprise and platform-grade workloads. The methodologies you develop and tooling you build exist to multiply that delivery.
You'd join a new performance team as one of its first members, working alongside a deeply seasoned performance engineer, with the team growing to roughly six this year. There's no legacy process to inherit — you'll help define how performance engineering works at Supabase.
You can walk the whole stack: follow a tail-latency problem from the query optimizer through the syscall boundary to the IO scheduler — or across pooler hops, network paths, and availability zones — reading profiles and traces at every layer.
Strong working knowledge of networking and cloud infrastructure performance: TCP behavior under load, network virtualization overhead, and the performance characteristics of AWS primitives (EBS throughput and IOPS, instance network limits, placement groups, cross-AZ latency).
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.
Straight to the employer's own application — no middleman.
Tell us and we'll mark Supabase as a company that has actually hired in the Caribbean. It's the most useful thing on this board and it only exists because people report it.
I got hired here →
