Founding Database Engineer
Full-time · Remote
[About Modern Relay]
Modern Relay builds the infrastructure companies use to build the context layer their AI agents work from. Our engine, Omnigraph, keeps a company's context as one shared, versioned graph in its own storage. It's written in Rust and open source.
We’re backed by Point Nine, Emerge and Amino Collective, and by angels including Charlie Songhurst (Meta board member), Martin Gould (Spotify), Thomas Clozel (Owkin) and Sarah Drinkwater (Google, Common Magic).
[The role]
Omnigraph stores a graph as Lance tables on object storage (S3-compatible stores, Azure Blob or a local disk), with typed schemas, Git-style branches, three-way merges and a readable history of every commit. Queries combine graph traversal with vector, full-text and hybrid search, on Apache Arrow and DataFusion.
You'll work on the engine itself: how data is laid out and indexed on object storage, how queries execute, and how commits, branches and merges stay correct when writers crash, race or retry. You'll also run it in production for the teams that depend on it.
[What you'll work on]
- Design storage layout and indexes on Lance, and measure what each read and write costs in requests, bytes and latency
- Build query execution that combines graph traversal with vector, full-text and hybrid search
- Keep commits, branches and three-way merges correct under crashes, concurrency and retries
- Write deterministic simulations, fuzzers and differential tests that fail on a wrong implementation
- Ship releases and storage format upgrades, and handle production incidents
[You might be a fit if]
- You've changed the internals of a real data system: a storage format, an index, a query engine or a transaction layer
- You've found or fixed a durability, consistency or race bug in such a system, and can explain why the fix holds
- You've built an automated check, such as a fuzzer or a deterministic simulation, that caught a real defect
- You've diagnosed a performance problem with measurements that showed its cause
- You've owned a production system through at least one incident
- You build mainly with coding agents, and accept their output only on tests, measurements and review
[Nice to have]
- Experience with Rust, Apache Arrow, DataFusion or Lance
- Work on graph databases, knowledge graphs or graph query processing
- A mechanism of your own design that you published or released, with an evaluation