The opportunity
Toast creates technology to help restaurants and local businesses succeed in a digital world, helping business owners operate, increase sales, engage customers, and keep employees happy.
What you'll do
Design, own, and continuously improve the monthly agent release program: one cadence, one launch process — across all lines of business. Build this as a durable operating mechanism, not a series of one-off coordination efforts.
Set and hold the platform-readiness bar. Engage credibly with engineering: teams on architecture, dependencies, and technical risk. Own the dependency and risk map. Be willing to call a postponement when a product isn't ready — and make that call stick.
Drive go-to-market coherence across LOBs so naming, packaging, and messaging: land as one platform story. Work with PMM and GTM to make sure the field can sell and operators understand what they're getting.
Instrument launch health and build reporting that matters: what shipped, what slipped, adoption signals, and the blockers that need to be resolved upstream. Feed this signal back to R&D leadership in a form they can act on.
Operate with high judgment in ambiguous situations. When the governance model: doesn't cover a case, make a defensible call and move. Surface the right decisions to leadership with the context they need — don't just escalate problems.
Establish the operating rhythms, governance structures, and cross-functional: alignment mechanisms that keep multiple engineering teams moving toward a shared cadence.
What they're looking for
- + years of technical program management working directly with software engineering teams.
- Track record of owning cross-functional programs end to end: not just coordinating them — from design through launch, across teams with competing priorities.
- Technical fluency sufficient to engage meaningfully with engineers on: architecture, dependencies, and risk: you can identify when a technical assumption is wrong before it becomes a launch problem.
- Demonstrated ability to build repeatable operating models. You've built the: system, not just run projects inside someone else's system.
