Area 01
Storage and transactions
Where rows live, how commits stay correct, how changes are captured, and how values are encoded.
store-*, cdc, codec, column
Jobs
You, press start
We are hiring a full-time, remote Rust engineer to build the database engine with us. Hackers who ship, not ticket movers.
The job
ReifyDB is a database written in Rust. It keeps live application state in one place: tables, incremental views, queues, and the logic around them, instead of Postgres plus Redis plus cron plus glue.
We are looking for a full-time Rust engineer to build it with us. You work across the whole engine, directly with the founder, and your code ships in the open.
If you would rather ship a fix than write a proposal about it, read on.
What you will touch
One role, the whole engine. These are the areas, with the crates you will find them in.
Area 02
RQL and query execution
The query language from parser to plan, and the engine that runs it.
rql, engine, evaluate, filter, routine
Area 03
Incremental views
Views that update as the data changes instead of re-running the query. The heart of ReifyDB.
flow, flow-sync, flow-async, subscription
Area 04
Servers and wire protocols
The HTTP, WebSocket, and gRPC servers, telemetry, and the SDK that clients talk to.
sub-server-*, sdk
Area 05
Testing and performance
Chaos tests, the test harness, benches, and the profiler. Finding the bug before a user does.
testing-chaos, test-harness, benches, profiler
You
- You have shipped real Rust: a crate, a service, a tool people use.
- You measure before you optimize. A flame graph beats a hunch.
- You fix the bug, write the test that would have caught it, and move on.
- You open a pull request instead of a meeting.
- You do your best work with little process and a lot of trust.
Bonus points
- You have worked on a database, a query engine, or a stream processor.
- You know your way around MVCC, LSM trees, or incremental view maintenance.
- You have run Rust under real load.
- You have broken systems on purpose with fuzzing or chaos tests.
- You have open source code we can read.
The deal
Full-time
You are part of the company, not a contractor on the side.
Remote
Work from wherever you get the most done.
Straight to the source
You work directly with the founder. No layers, no ticket relay.
No venture capital, ever
No board and no exit clock. The work answers to users and to the code, not to a fund.
In the open
The engine is public on GitHub. Your work ships under your name.
How to apply
1
Read the code
Clone reifydb/reifydb, build it, and poke at it until something bugs you.
2
Show us something
A pull request to ReifyDB is the best application. A link to Rust you are proud of works too.
3
Send one email
To founder@reifydb.com: who you are, the link, and one thing in ReifyDB you would change.
INSERT COIN
Ready?
Code you are proud of and one email. That is the whole application.