Skip to content
Careers

No open roles today.

We would rather say that plainly than keep a page of aspirational listings for jobs that are not funded. When there is a role, it will be here with a salary band on it. In the meantime, the note at the bottom of this page is read.

How we work

Worth knowing before you write.

These are the working habits the codebase actually enforces, not a list of values chosen because they sound good.

Correctness before surface

Money is integer minor units. Inventory cannot oversell, and that is enforced by a database constraint rather than by remembering to check. The invariants are written down and tested, because an experience business that oversells a room has a real problem at a real door.

Measure it, do not assert it

Performance claims come with a benchmark, accessibility claims come from the computed accessibility tree, and load claims come from a script anyone can re-run. Work here is expected to arrive with its evidence.

Say what is not done

Every unfinished thing in this product is written down in an audit document with the reason. Nobody is penalised for a gap that is named; the failure mode we care about is a gap that is hidden.

Small team, wide surface

The product spans audience intelligence, financial modelling, commerce, operations and a public sales surface. You will not be handed one narrow slice, and you will be expected to read code you did not write.

Open applications

Write anyway, if the work is obviously yours.

Send something you built and a paragraph on a decision you made in it that you would now make differently. That is more useful than a CV, and it is what we will talk about.
Open applicationcareers@audonomics.com

We reply to every open application, including the ones we pass on. It takes a few days.

Or just use the thing.

The fastest way to understand whether you want to build this is to connect a source and watch it rank what you could create.