Build the database
the world's markets run on
QuestDB powers mission-critical systems across capital markets, crypto, energy, and aerospace. We're a performance-obsessed team turning a category-defining product into a category-defining company. Engineers, infrastructure, and go-to-market: we want to hear from you.
Very real workloads.
The database itself
Columnar storage, vectorized SQL, open data lakehouse, Horizon joins, streaming materialized views. Written in low-latency Java (zero-GC), Rust, C++, and assembly.
The system around it
Kubernetes operators, multi-region replication, live migrations, the control plane that runs QuestDB inside a customer's own AWS or Azure account without them losing sleep.
Built for the agentic stack
Native REST API, low-latency SQL, and open formats AI agents can read directly. As more queries come from autonomous systems, the database has to answer in milliseconds and expose its schema cleanly to any agent framework or autonomous workflow.
The thing we're known for
JIT codegen, SIMD hot loops, memory layout experiments. If shaving 220µs off a query makes you excited, read on.
“QuestDB brings a SQL-first solution able to ingest data at speed.”
Press release →
“QuestDB is used at Airbus for real-time applications involving billions of data points per day.”
Press release →
Details →“QuestDB has become the standard for data aggregation.”
Press release →
Case study →“QuestDB is a time series database truly built by developers for developers”
Details →
Powering critical data workloads at leading companies globally
Things we actually mean
Remote, with anchors in London and NYC
The team works remote by default, with local offices in London and New York for anyone who wants a desk, a whiteboard, or a drink after work.
Open source is not a side quest
Our core is Apache 2.0, PRs get reviewed in public, and the community sees the same code our enterprise customers run.
Everyone talks to users
No account-manager firewall. Whatever your role, the people running our database in production are one Slack message away.
Stay open, delete proprietary
We'd rather lose an RFP than bolt on a closed-source dependency that traps the user.
The boring stuff, done well
Equity in a company that ships
Meaningful options on transparent bands, so you benefit when the database does.
Remote, with regional hubs
Most of the team is remote; we also have offices in London and New York and are actively hiring into both.
Annual team offsite
One week, one room, the whole team. Past stops: Malta, Scotland, English countryside, London, NYC.
We're hiring. Tell us what you'd build.
Don't see your role?
We hire for impact more than headcount plans. If you can make the product, the company, or the community measurably better, we want to hear from you.
Four steps. About two weeks.
- 01
Intro
30 minutes with a hiring manager to walk through what the role actually involves and what you're looking for.
- 02
Working session
A real problem close to what the team ships, whether that's pairing on code for engineers or a strategy or operational scenario for other roles.
- 03
Team deep-dive
Two or three conversations with future teammates on substance, trade-offs, and war stories.
- 04
Offer and references
Written offer within 48 hours of the final loop. We'll ask for references; feel free to ask for ours.