Careful defaults matter
We say no to features, deals, and shortcuts that make the answer path harder to explain. The product has to stand up to buyer review.
We are early, deliberate, and focused on a product that has to make sense to operators, source owners, security reviewers, and buyers.
We say no to features, deals, and shortcuts that make the answer path harder to explain. The product has to stand up to buyer review.
Most work happens in writing, on a weekly rhythm. We use meetings for decisions and customer context, not constant status reporting.
Postgres, TypeScript, Go, Python, plain HTTP. We pick the option that an on-call engineer can debug at 3am, not the one with the best blog post.
Product and engineering stay close to sales calls, procurement questions, and support patterns. The work is downstream of the customer's actual problem.
We hire where we can support people well and keep team rituals documented.
Every role will publish a range before interviews move past the first conversation.
Full-time roles include country-appropriate health coverage, paid leave, and time away from work.
Books, courses, conferences, and expert help are part of the job, not a side favor.
We pay for the hardware, software, and workspace setup needed to do focused work.
Early teammates work directly with the founders on product, customers, and company operating rhythm.
If the problem space fits your work, send a note. We hire deliberately and prefer to meet strong people before a role is perfectly shaped.