Smart Data Engine
Open client libraries, a private control plane and a shared data contract. The next challenges include the integrated AI workflow, workload-qualified migrations and a complete customer setup path.
Build the data layer. Shape the hard decisions.
Work on Smart Data Engine, our open-core data layer, and the specialised engines behind it. The SDKs and control-plane components already exist. The work now is making the whole workflow dependable: placement, migrations and safe access to data.
What You Would Actually Be Doing
From the client SDK to the storage engine. The public repositories show the engineering problems, tests and trade-offs you would work with.
Engines and hardware
The low-level half. C++20 with nothing between you and the machine, lock-free structures, seqlocks, cache lines you can count, and bespoke engines for clients whose workload nothing off the shelf fits.
- C++20
- Bare metal, no containers
- Public conformance tests
- Reproducible benchmarks
Why Join Us?
Technical ownership, measurable results and direct contact with clients.
Shape the architecture
The libraries and control-plane components are working, but key integration and operational decisions remain. Your designs, code and measurements help turn them into a dependable product.
Microseconds, Not Milliseconds
The target is a latency percentile agreed with the client before the work starts. You will profile, count cache misses, and defend numbers instead of opinions.
Nobody Between You and the Client
You sit in the call where the benchmark gets agreed. No one translates the requirement for you, and no one translates your answer back.
Bare Metal, No Containers
Our engines are written for specific hardware and never run in a container, because a container is overhead between the code and the machine. You tune against the real thing.
What You Get
Real influence, clear expectations and ownership of what you ship.
You Shape the Company
Not only the code. How we hire, how we review, what we promise a client and what we refuse: those are decisions being made right now, and you would be in the room for them.
The Range, Up Front
You hear the salary range in the first conversation, not after three rounds. It is transparent inside the company and it moves as the company does.
Warsaw Office, Five Days
Said plainly so nobody wastes a week finding out. The work happens in the room together, and the hours around that are yours to arrange.
You Ship It Yourself
No ticket queue, no six-month roadmap, no handover to a team that owns deploys. You write it, you release it, you watch the graph afterwards.
How Hiring Works Here
No whiteboard puzzles. We read code, starting with yours.
-
You send something you built
A repository, a patch, a write-up of something you made faster. Anything we can actually read. A CV is welcome but it is not the first thing we open.
-
We read it, then we talk
One conversation, with the person who writes the code rather than with a recruiter. Bring questions about the architecture. They are the interesting part for both of us.
-
A real problem, together
Half a day on something from the actual backlog, side by side. No take-home marathon and no invented puzzle about binary trees.
-
An answer either way
Within a week, with the reason attached. If it is a no, you get to hear what would have changed it.
Open Positions
What we are looking for right now.
Loading positions...
Not on the list?
If you can build a control plane, write a storage engine, or run databases that other people depended on, write anyway. Tell us what you built and what it cost you to make it fast.
Send Us Something You Built