Careers
No open roles right now.
When one opens, it is written here with what it pays.
What we make
A business owner pastes their website address and gets every problem we can find on it, priced in money lost each month, with the arithmetic shown.
190 checks run today, 62 of them free: from a missing email record that lets a stranger send invoices in the owner’s name, to a form that posts a card number over plain http.
Every figure in a report traces to a published source, and every finding comes with its fix.
How the work is done
A check is one file: a pure function from the evidence a scan gathered to a list of findings. It never touches the network itself, so it is tested with a fixture and nothing else.
The collectors that do touch the network follow a written safety rulebook, and anything that sends a request the owner did not invite waits until they have proved the domain is theirs.
Decisions are written down before the code changes, with the alternative that was turned down and why. Nothing ships until it has passed a gate: the whole suite and a production build with size budgets.
Then a browser walk through a customer’s journey from first check to closed account, a load test, a click and keyboard audit, and a read-only check of the live site afterwards.
The words matter as much as the code. A finding is explained to the person who owns the business, not to their developer, and there is no fear without a fix.
What we would look for
Somebody who can read a standard and turn it into a check with a price that survives a sceptical owner. Somebody who writes plainly and shows their working.
Somebody who would rather say no to a feature than ship a dark pattern. Which of those a role asks for depends on the role, and the role will say.
Write to us anyway
Say so on the contact page, with what you have built and a check you think we are missing.