Careers
No open roles right now
We are not advertising open roles at the moment. Rather than list positions that do not exist yet, here is what we are building, what it is like, and how to get in touch if it sounds like your kind of problem.
What we are building
A governed layer between an organization's data and the questions people actually want to ask of it. The interesting engineering is not the conversational part — it is the semantic model, the access resolution, the validator between a generated query and a database, and the machinery that binds every figure in an answer back to the result cell it came from.
Alongside it, a data business: collecting published datasets that are painful to use, resolving the entities inside them, and keeping them current. Less fashionable than the model work and probably more durable.
We are small and based in Chicago, Illinois, with remote work normal rather than exceptional.
What working here is like
Correctness beats throughput
The whole product is a claim that a number can be trusted. That makes a wrong answer worse than a slow one, and it shapes how everything here gets reviewed. If that sounds tedious rather than interesting, this is not the right place.
You will talk to customers
Every role here touches the people using it. The definitions that make the platform work come out of conversations with the person who currently answers these questions by hand, and those conversations are not delegated to one function.
Small, and honest about it
There is no layer between you and the decision. There is also no established process to lean on, no team already covering the thing you would rather not do, and a fair amount of work that is unglamorous by nature.
Regulated buyers, real reviews
Our customers' security teams read what we write. That is a good constraint: it rules out the version of this product that demos well and cannot ship.
Where we will need people
These are the areas we expect to hire into as the company grows. None of them is an open position today, and we will not treat a note as an application to one.
- Product and platform engineering
- Data engineering and ingestion
- Solutions engineering and implementation
- Customer success and account management
- Data research and operations
- Enterprise sales
Send something speculative
Tell us what you are good at and what you want to work on. Two paragraphs is plenty. We read these, we keep the ones that fit, and we come back to them when a role opens — which is a slower answer than you probably want, and an honest one.
If you would rather email directly: hello@deepgarden.io
Interested anyway?
No role attached, no process to go through. Just tell us what you do.