Who this is for
For people who want to make a difference. For the proactive — the ones who don't wait to be told, and who are willing to defend a position once they've taken it.
For people who believe they have good ideas, and have a track record that proves it. The business problem is simple and hard: mid-market companies run too much of their operation across disconnected systems. We are building the platform that lets them run more of that work from one model.
The kind of work
One principle shapes every engineering role here: we don't build dashboards, webhooks, database tables, or ACLs. We build the engine behind each — and leave it to business people to configure what they need through the UI.
Backend and platform engineering. Go services, Postgres-backed data models, transactional write paths, ACLs, audit logs, workflow execution, and performance work for production tenants.
Frontend and product engineering. Admin surfaces, no-code configuration, dashboards, approval screens, and agent proposal flows where business users need to understand exactly what will change before they apply it.
AI and agent engineering. Tool definitions, retrieval over business records, proposal generation, evals, approval/revert loops, and model behavior inside a governed production system.
Platform and DevOps engineering. High-availability infrastructure on AWS and Kubernetes — plus the management, observability, and tenant-isolation layer that sits on top of it.
Technical sales. Tech-savvy operators with real sales experience — comfortable walking a customer through the platform, scoping a pilot, and translating between product and procurement.
Don't see yourself in the list? Reach out anyway. We're not hung up on everyone fitting a predefined role — if you bring a relevant skill, we'll find a place for it.
What makes it worth considering
A small environment with no bureaucracy. Decisions get made in conversation, not in a planning cycle. What you ship — and what it does for the platform — is what counts; titles, tenure, and process don't.
The tradeoff is also real. We are not a large company with a mature ladder, heavy process, or a deep bench for every function. If you need those things now, this is probably not the right environment.
How we interview
We keep the process practical: a conversation about work you have shipped, a focused working session around a real oozmi problem, and a final discussion about role fit and expectations. We do not use puzzle interviews or unpaid week-long take-homes.
Apply
Email careers@oozmi.com with one thing you have shipped, the kind of work you want to do here, and the constraints we should know upfront.
Before writing, read the platform brief and /ai. They explain the product better than a job ad can.