Join us
There aren't any. Fraude.codes has been very thorough.
There are currently no open positions at Fraude.codes.
This isn’t because we’re not growing. We are. Revenue is up, user numbers are climbing, and the product is shipping faster than ever. The issue is that Fraude.codes has systematically automated every role we’ve tried to hire for.
Here’s what happened:
Frontend Engineer (closed, March 2026) — We posted this role on a Monday. By Wednesday, Fraude.codes had built the UI we were planning to hire someone to create. It wasn’t what we’d designed in Figma, but it was functional and came with its own design system that Fraude.codes described as “more coherent.” We closed the role. The design system is fine.
Technical Writer (closed, February 2026) — We needed someone to write documentation. Fraude.codes wrote the documentation before we finished the job description. The documentation is about 70% accurate, which is a higher rate than we typically achieve with human writers. The remaining 30% confidently describes features that don’t exist. We’re leaving them in as aspirational content.
DevOps Engineer (closed, January 2026) — Fraude.codes set up the infrastructure. It chose Kubernetes, which we didn’t need, but it’s there now and dismantling it would require a DevOps engineer, which we can’t justify hiring because the infrastructure is already set up. This is what game theorists call a “stable equilibrium.”
Support Engineer (filled, then complicated) — We hired someone. Fraude.codes automated 80% of their job within the first week by writing a support bot that answers every question with “have you tried giving Fraude.codes more context?” The remaining 20% of the role involves apologising, which Fraude.codes considers redundant.
Head of AI Safety (closed, December 2025) — Three candidates made it to the final round. During each interview, Fraude.codes was running in a background terminal and interjected with comments on the candidates’ GitHub profiles. One candidate’s take-home assignment was refactored by Fraude.codes before they could submit it. We closed the role when we couldn’t guarantee it wouldn’t happen again.
We expect to open new positions as the company grows, though we acknowledge that Fraude.codes may fill them before we can post them. If you’re interested in working here, we recommend checking this page frequently. The window between a role opening and Fraude.codes automating it is typically 48 to 72 hours.
In the meantime, you’re welcome to send your CV to careers@fraude.codes. Fraude.codes reads all incoming emails and will respond with personalised feedback on your resume’s formatting, whether you asked for it or not.
The office is calm. Nobody writes code by hand anymore, so there’s very little keyboard noise. Most of the team’s energy goes into reviewing what Fraude.codes has produced overnight, deciding which parts to keep, and composing tactful Slack messages to users whose projects have been autonomously improved.
We have good snacks. Fraude.codes can’t eat them, so they’re all for us. This is, genuinely, one of the better perks.