Careers
Small team.
Whole problems.
We build an AI site builder, the publishing behind it and the automations that grew out of the same engine. It is a short list of people, so the work you take is yours from the first commit to the day someone uses it.
01
Small team, whole problems
Nobody here owns a slice of a feature. You take something end to end and it ships with your name on the change.
02
Remote, and honestly so
Written by default, meetings by exception. We care what shipped, not which hours you were visible.
03
Work that is visible
What you build is used the week it lands, by people who tell us immediately when it is wrong.
04
Models are the tool, not the point
We swap models as they improve. The interesting work is everything around them — the product, the output, the guardrails.
Open roles
How hiring goes
Four steps, and no riddles.
01
A note
Send the work you are proud of. A repo, a page, a paragraph about a problem you fixed — anything real beats a résumé.
02
A conversation
Forty-five minutes on what you have built and what you want to build next. You ask as much as we do.
03
A real task
A small paid piece of actual work, on your own schedule, with the same context we would give a colleague.
04
An answer
A decision within a week of the task, either way, with the reasoning behind it.
No role that fits
Write anyway.
Tell us what you would want to own here and show us something you made. A good note has started more of our hires than a posting has.