Programming Producer Toronto

Reports to: Harry Taylor, Director of Programming

Classes are the soul of Othership. They're the part of the product we've spent the longest mastering, and they're what makes Othership unlike anywhere else.

The next frontier is Free Flow and special events. Free Flows are the majority of Journeys we deliver, which makes them the biggest lever we have left to pull - we've started elevating them with tea service, salt scrubs, the essential oil bar cart, and a handful of other touches, and now it's time to push that work much further.

Special events sit alongside: niche, high-impact moments - breathwork takeovers, comedy nights, Music Nights, Lovership - that need to be produced with the same care and craft we bring to a class.

The gap is throughput. We concept new programming faster than we can produce them, test them and train guides to scale them. Good ideas die in chats and the ones that survive often arrive on the floor under-baked. This role exists to fix that.

A programming concept hands off to you from the leadership team - already shaped, already loose-scoped - and you take it from there. You run the experiment yourself, source the talent, brief the Guides and Stewards, manage the props, coordinate with marketing on the listing and social brief, stand in the room as the main coordinator when it goes live, and write the debrief the next day. Then you produce V2 sharper than V1, based on what you observed and the feedback you gathered.

The immediate output is a steady stream of new experiences for Journeyers. The compounding output is a tested, refined library of programming Othership can roll out reliably across cities.

Taste - and a deep working knowledge of the Othership vibe. This is the table-stakes requirement and the most important one. You've been to enough sessions as a Journeyer to know what a 10/10 Othership experience feels like, and you can articulate why a class, a Free Flow, or a Guide-to-Journeyer experience lands flat when it does. You can name the difference between a great class and a bad class, a magic moment and a moment that gets forgotten, a great Guide-to-Journeyer experience and a bad one. You can give specific, actionable feedback after watching something – not just "that didn't work" but "that didn't work because x, and my proposed solution is y." The whole iteration model depends on you being able to identify problems precisely and propose specific fixes – that's only possible if you know the product cold.

Highly organized and accountable. You'll be running multiple programming projects in parallel - each with its own talent, run-of-show, props, marketing brief, and Guide briefing. You live in calendars and Notion. You know how to leverage AI tools to help with organization, communication, and getting more done in less time. You communicate clearly and proactively. When something is at risk of slipping, you flag it before it slips. You're given full autonomy and you take ownership end to end - these projects are yours, the team relies on you to land them, and you don't need to be chased.

Communicative and unafraid of the room. You're talking to Journeyers in real time, briefing Guides on their roles, coordinating with vendors who don't know our space, and pulling feedback from the floor staff working the activation. You're the kind of person who walks up to a stranger after a session and asks how it landed. Sociability and hospitality are core to this role, not optional - feedback comes from everywhere, and you need to be confident drawing it out.

Adaptable and efficient. Things break in real time. A vendor cancels, a program that sounded great on paper is a complete flop and needs to pivot mid-night, a 60-person room reads completely differently than the 30-person test. You change things on the fly, document what you changed and whether it worked, and bring it to the next debrief. You don't over-plan, you don't get stuck in the weeds, and you'd rather test something at 70% and learn from it than wait for 100% and never ship.

Discerning. Adapting on the fly only works if you have judgment about what to change and why. You can read a room, name what's off, propose a specific fix, report back cleanly, and roll the change in next time.

Toronto-based and in the ships 4-5 evenings a week. This role doesn't work remotely. Most programming happens 5pm–10pm, and the Journeyer interviews, small-format tests, and floor-presence work happen alongside it - so 4-5 evenings a week in Yorkville or Adelaide is the actual ask, not a stretch goal. If you're not a hell yes on that, this isn't the role.

We're hiring this as a paid trial first - 20 hrs/week at $35/hour, with the runway to grow into a full-time role if it's a fit on both sides.

The first 120 days focus on producing 7–8 new programming experiences plus a parallel stream of small-format tests and existing programming auditing. Below is the working list - not exhaustive, and the priorities will shift as we learn - but it's what's on deck for V1.

Each headline activation runs through a test-and-iterate cycle (3–5 reps). The small-format tests compound across months and feed the monthly report. The cycle for each headline program looks like:

After 120 days we sit down to talk about what's next - usually scaling the role to full-time at expanded scope across both Toronto ships.