Bobyard Program Manager responsible for verifying bug fixes, managing launch communications, and coordinating between engineering and customer-facing teams. Ensures accurate status tracking and clear communication for product releases.
Responsibilities
The product team is launching new trades, features, and fixes constantly — sometimes a dozen projects in flight at once. Right now, nobody owns making sure what ships is actually fixed, actually launched, and actually communicated. That's this role. You'll sit between engineering and every customer-facing team, verify that bugs are really resolved before we tell anyone they're fixed, and make sure every launch comes with a clear, honest update to the people who need it — customers, CSMs, and sales alike.
Own the day-to-day truth of Linear — every ticket has a real status, nothing goes stale or slips silently past its target date
Independently verify that "fixed" tickets are actually fixed before they're closed or communicated
Write and send launch communications for every release — clear, specific, no corporate filler — to customers and internal teams
Build and run a standard launch checklist so marketing and CS are looped in before a release, not briefed after
Coordinate directly with Platform engineers on active projects — you're in their tickets, not waiting on a summary
Flag risk and slippage early, in the same weekly rhythm the product team already runs
Be the first call when a customer says something's broken and an engineer says it isn't
Qualification
Fluent in Linear or Jira — daily useCan write the same update two waysBackground in construction tech
Required
2–5 years in a role that combined technical coordination with customer-facing communication — Implementation, CS Ops, QA, or release coordination
Fluent in Linear or Jira — daily use, not passing familiarity
Can write the same update two ways: technical for engineers, plain for customers
Comfortable pushing back on an engineer's "it's fixed" claim without making it a fight
Genuinely enjoys verification and follow-through — you don't lose interest once something's "probably done"
Based in or willing to relocate to San Francisco
Preferred
Experience at a Series A–C startup with no dedicated QA team
Background in construction tech, PropTech, or a technical B2B product
Experience building a launch or release process from scratch
