Careers
Build systems that actually go into production.
We're a small team turning messy operations into working software for businesses and government. There are no fixed openings — if that's the work you want, tell us.
How the work actually goes
You own the problem, not a ticket
We map the actual work before writing code — the friction, the data, the decisions. You'll talk to the people whose day the system changes.
It ships, or it didn't happen
Every engagement ends in production: a working system somebody depends on. We don't hand over recommendations and walk away.
Constraints are the interesting part
Procurement, records obligations, accessibility, protected data. Public-sector and regulated work has real rules, and designing inside them is the craft.
You stay after launch
We operate what we build — hosting, monitoring, support, improvement. You see the consequences of your decisions instead of guessing at them.
Who tends to fit
We hire as work lands, so there's no list of titles to match against. These are the traits that hold up across every role we've needed.
- You've built something end to end and watched real people use it.
- You'd rather ask why a process exists than automate it faster.
- You can write clearly for a non-technical reader — a county administrator, an owner, an ops lead.
- You're comfortable being the one who says a system shouldn't be built yet.
- You treat security, accessibility and auditability as part of the work, not a review gate at the end.
Apply
One form, no account, no portal. It reaches a person.