We’re looking for ONE person to build the operating system for how couples experience Bolt Farm, and then run it.
This is not a documentation project. It is not a role where you produce an SOP binder nobody opens. It is not a seat for someone who needs the system to already exist. You will inherit a live operation with strong output and weak infrastructure, and you will build the infrastructure underneath it while it runs.
The Archetype: The Machinist
We call this seat the Machinist, because the deliverable is a machine, not a memo.
They ship, then document. They have built a working system first and written it up second, and can name a time the doc came after the thing already worked.
They delete before they add. Given a recurring problem, their first instinct is to remove the step that causes it, not to add a policy on top of it.
They build with AI as a default, not a project. They have automated a real piece of their own job and can demo it running.