About Bobyard
Construction is a multi-trillion-dollar industry that still estimates by hand. Contractors measure and count materials off drawings manually, and it caps how many jobs they can bid. Bobyard uses computer vision and NLP to automate takeoffs and estimates, so contractors bid faster and win more. We raised a $35M Series A led by 8VC, with Primary and Pear, and we're growing fast.

About the role
The product team ships constantly — new trades, features, and fixes, sometimes a dozen projects in flight at once. Right now, nobody owns whether what ships is actually fixed, actually launched, and actually communicated. That is not a coordination gap. It is an operating-system gap, and this role owns it.

You will design, build, and run Bobyard's product operating system: how work is specified, how releases are verified, how launches are communicated, and how risk is surfaced before it becomes a customer problem. You sit with engineering, product, CS, and sales — but you do not take orders from any of them on quality. You own the ship / no-ship call.

This is not a coordinator role. If you have never built a release or QA operating system from scratch, or you need coaching on how to run a launch, this is not the role for you.

What you'll own

• The release and launch operating system end to end: intake, verification, rollout, communication, and post-launch follow-through — designed by you, not inherited from a checklist

• The quality bar: what "fixed" means, how it is independently verified before anyone is told it is fixed, and what happens when it is not

• The truth of the system of record (Linear and whatever it connects to): no stale tickets, no silent slippage, no launch that goes out without CS, sales, and customers looped in beforehand

• Ship / no-ship decisions, with the reasoning documented and defensible to engineering and to customers

• The metrics that prove the system works: defect escape rate, launch slippage, time from fix to verified fix, and launch communication accuracy — and a track record of moving them

• Risk, early and in writing: you surface slippage and tradeoffs before they hit a customer, not after

What success looks like in 90 days

• A documented launch / release operating system the whole product org actually runs on, not a doc nobody reads

• A measurable drop in "told the customer it was fixed, it wasn't" incidents

• Every launch shipped with a clear, specific, honest update — to customers and internally — before the release, not after

What we're looking for

• 6+ years owning product operations, program management, or release / QA operations at a B2B software company — owning the system, not staffing it

• You have built a launch, release, or QA process from scratch, and you can show what it replaced and what it moved (cycle time, escape rate, slippage, adoption — bring numbers)

• You have owned a ship / no-ship call and held it against pressure from engineering or from a customer deadline

• You write the same update two ways without losing the truth in either: technical for engineers, plain for customers

• You push back on an engineer's "it's fixed" claim without making it a fight — and you verify anyway

• Based in, or willing to relocate to, San Francisco; in person at our San Francisco office (101 2nd Street), 4 days a week

Nice to have

• Construction tech, PropTech, or workflow-heavy B2B software

• Experience at a Series A–C startup with no dedicated QA team, where you were the QA system

• Experience scaling an operations function as a team and a product surface grew, not just as ticket volume grew

What we offer $130,000–$160,000 base, 0.02%–0.04% equity (4-year vest, 1-year cliff), on-site in San Francisco.

Come build with us!