The Mandate

We're looking for ONE person to own the entire emotional arc of a Bolt Farm stay, from the moment a couple books to the check-in message ninety days after they leave.

This is not a department to caretake. It is not a role where you write briefs and hand them to someone else. It is not a seat with a middle-management layer beneath you to absorb the work. You own the outcome across Dreamweavers, Hosts, Guest Communications, Spa, Housekeeping, and Maintenance, and none of them report up through a buffer.

The Archetype: The Composer

We call this seat the Composer, because a stay is a score, not a checklist.

They hear the whole piece, not the notes. They can take a guest's intake answers and name the three moments in a 48-hour stay that will actually be remembered, then cut the other nine.

They write parts other people can play. Something they designed is still running today, executed correctly by people they no longer supervise.

They rehearse in public. They have shipped a v1 that was visibly imperfect, watched real guests use it, and rewritten it inside two weeks.
The Only Three Things That Matter

1. Can you build the machine? You have designed a service system, not just run one. Passing looks like: you can walk us through a workflow, SOP set, or communication sequence you built from scratch, show what it replaced, and tell us what got measurably better.
2. Can you make people run it without you? You have held a standard across a team you did not personally supervise every shift. Passing looks like: a specific example where quality held while you were off property.
3. Do you already work with AI? You use AI daily, unprompted, and you can show us something real it helped you build. Passing looks like: you name the thing, the tool, and the result. Buzzwords score zero.

What You Own

• The full guest journey: pre-arrival intake, arrival, in-stay, departure, and the T+24h / T+7d / T+90d follow-up cadence
• The Dreamweaver, Host, and Guest Communications teams, and the standard all three hold
• The wow framework in practice: four standardized wows plus one creative wow per stay, delivered at full occupancy
• Every guest communication that goes out, and the system that sends it
• Service recovery: the call, the fix, and the upstream change that stops the repeat
• Guest feedback as an operating input, not a report: reviews, surveys, and service data turned into a weekly change
• The guest data layer inside BoltOS, and the rule that if it isn't in BoltOS, it doesn't exist
• Rebooking, loyalty, and enhancement revenue as a function of experience design

Why This Is the Best Seat on Earth

3,300+ five-star reviews already exist, so you are not fixing a broken product. You are systematizing one that works. We are scaling from a $32M flagship toward a $200M+ portfolio, which means the system you build here becomes the operating standard at every property that follows. You get BoltOS, an AI layer already running live guest operations, and a founder who will fund the build rather than ask you to justify it. Peak season is now.

No Gates. Only Signal.

No degree required. No minimum years required. We have hired people with nonlinear backgrounds who outperformed twenty-year re9sume9s, and we will do it again.

The only criteria are the three above. A brand-name employer on your resume earns you nothing here. A guest-texting bot you built for your own Airbnb earns you a call.