Storage Platform Engineer
Supabase (company site, opens in a new tab)7+ yrsRemoteDirect career pageEst. 35–60 LPA
Posted 3d ago
Reach people at Supabase
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Supabase you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own the architecture, build-vs-buy decisions, integration, and production operation of Supabase’s NVMe-over-Fabrics block storage platform.
- Improve Postgres I/O performance while delivering durability, availability, tenant isolation, measurable SLOs, and production observability.
- Build the foundations for block snapshots and copy-on-write clones, and keep storage portable across cloud providers and bare-metal infrastructure.
Minimum Requirements
- Work Experience Required: 7+ years in software engineering, including significant experience building and operating production storage systems.
- Must have built or operated distributed/software-defined block storage and have hands-on NVMe/TCP or NVMe-oF experience, including targets, initiators, multipath, and failover.
- Must have deep Linux storage internals knowledge, strong systems coding skills in Go plus C, C++, or Rust, and experience measuring performance with tools such as fio, pgbench, eBPF, or perf.
- Must have technical leadership experience on complex systems, Kubernetes controller and/or CSI driver experience, and on-call experience for large production systems.
Ideal Candidate Profile
- A senior storage engineer who has owned distributed block storage in production and can make architecture and durability tradeoffs across performance, failure handling, and data integrity.
- Best suited to hands-on, end-to-end systems work: profiling the full Postgres-to-device I/O path, integrating with Kubernetes, and operating against performance and reliability SLOs.
- Relevant differentiators include SPDK, snapshots or copy-on-write, Postgres internals, AWS networking, or bare-metal/colo storage experience.