Skip to content

Careers

AI made writing code cheap. It made judgment expensive.

We’re hiring engineers for that second thing. If you’re the person on your team who catches what everyone else missed in review, we’d like to talk.

The delivery loopyour seat
  • Blueprint

    structures the work

    agent
  • Forge

    writes the volume

    agent
  • Redline

    first-pass scan

    agent
  • Senior review

    decides what ships

    You
  • Proof

    generates the tests

    agent
  • Ship

    approves the release

    You

Four agents write the volume. The two gates are people — and those two seats are the whole job.

The volume is generated. We're not hiring people to type it. Four internal agents — Blueprint, Forge, Redline and Proof — write the predictable seventy percent. That work is close to free now. What isn't free is the person who reads what they produced and decides what is correct, what is plausible-but-wrong, and what gets thrown away. That person is what this page is about.

Four things we look for. None of them is years of experience.

You can review faster than you can write

The scarce skill is no longer producing code. It is reading a diff you didn't write and knowing, quickly, whether it is right.

You argue with the model

Our agents produce code that compiles, reads correctly and passes its test — and is sometimes wrong anyway. We want people whose instinct on a confident answer is to check it, not to merge it.

You've shipped something people use

Side projects count. Production incidents count double. What matters is that you have owned something after launch, not just handed it over.

You explain things well

You will talk to founders directly. Being clear in writing and on a call is part of the engineering job here, not adjacent to it.

No open roles listed right now.

We hire continuously rather than in batches. If the four points above describe you, don’t wait for a posting — send us something you have built and a paragraph on what you would have done differently.

info@trivialworks.com

Show us the thing you caught.

The bug nobody else saw, the design you argued against, the diff you sent back. Send it, with a paragraph on how you found it. That tells us more than a CV does.

Not the right time? Read who you’d be working with.