Senior Product Manager

Workyard puts everything between the job site and the office on autopilot for contractors.

That's the gap where contractors lose money — manual timesheets, end-of-week data entry, cost-coding nobody in the field wants to do, compliance chased after the fact, and a payroll admin re-keying numbers they don't trust. We close it. Time is GPS-verified and corrected the moment crews arrive. Hours get coded to the right job automatically. Errors get caught before anyone sees them. Verified data flows straight into payroll and accounting without anyone touching it twice.

We were built by a brother-and-sister team who ran payroll for 500+ field workers and couldn't find a single tool that got the hours right. So they built one.

Today, thousands of workers clock in on Workyard every day across construction businesses in the US market.

Construction contractors are the most honest people you'll ever build for. They've been sold software that didn't work before, so they don't just hand out trust, we have to earn it. When we do, they tell every contractor they know that we’re the best-in-class. No marketing budget buys what a foreman saying "this one actually works" buys.

That sets a high bar, and the feedback comes back fast. It also means you'll always know whether what you shipped mattered. A payroll admin gets Friday afternoon back, or a foreman spends the day building instead of chasing paperwork. That's the whole job.

We're about 70 people and growing fast. We value people who have high agency over pedigree. There's no playbook to inherit, which means you'll reason from first principles more often than you'll follow a process, and the parts that don't exist yet are yours to build and own.

You’ll own product lines, not a random backlog of customer requests from sales.

That means you own the problem, what's broken, what it's costing them, which of those problems is worth the next eight weeks of engineering time, and what "solved" actually looks like. You'll build the solutions alongside Product Engineers that start the work, define the success criteria the release gets measured against, and be accountable for whether contractors adopt what we ship. You’ll work closely with Product Engineers (in-office) who care about the problem as much as you do, and are held accountable not for just shipping, but ensuring what is built, works.

You'll report to the Head of Product (a co-founder) and also work directly with the CEO, Head of Sales and CS.

AI has changed what a product manager actually does, so we're not fussy about where you came from. We'll take a well-credentialed senior PM and a hungry less-experience one equally seriously, most have come from one of these paths:

• Own the strategy for your product line and make the trade-offs explicit. What we're doing, what we're not, and why. Write the rationale down where the whole company can read and understand it.

• Turn customer signal and market movement into an outcome-based plan for your line, not a feature list with dates attached.

• Keep a live view of the competitive set. Know where we win, where we lose, and which of those is worth fixing and fighting for.

• Run discovery on a cadence, not when someone reminds you. Contractor interviews, transcript analysis, win/loss review, support escalation analysis.

• Build your own tooling to make your discovery process faster. Most of us have Claude skills wired into our transcripts, our buying-barrier data and our pain-point taxonomy.

• Prototype and pressure-test before we fully commit. Have good product sensibility to build your own prototypes, instead of relying solely on a designer to help out.

• Partner with Product Engineers, who own the solution alongside you, to get into the weeds on how the experience will work. Be the judgement layer for trade-off calls on what the minimum-lovable version is going to be to solve the problem defined.

• Own the success criteria in customer-outcome terms, and the success metric with a time period and a definition of done attached. That's the finish line the release gets measured against.

• Know the platform well enough to hold a real conversation with your Product Engineers about trade-offs and delivery details and estimations. You don't need to write the code. You do need to be technical enough to understand why decisions are being made the way they are and have the confidence to challenge assumptions.

• Own the value proposition for your product line and contribute to pricing and packaging. Be able to say why a contractor picks us over the alternative in one sentence.

• Write the GTM material yourself. Positioning, the release note, the help article, the in-app copy, the CS briefing. We believe that to own product outcomes, you need to be able to talk about them too.

• Own adoption, not shipping. A release nobody turns on didn't happen. Watch the number for weeks afterward and report it honestly, including when it's worse than you predicted, and what to do next.

• 4-5+ years in product roles. We care more about what you've shipped than the years on it. We'll take a well-credentialed senior PM and a hungry less-experienced one equally seriously, and we don't care about logos.

• Evidence you can find a real problem yourself. Not "worked with the research team". You talked to users, read the tickets, dug through the data, and came back with a unique insight nobody else had.

• Comfort with numbers. You can pull your own query, read a funnel, and size an opportunity without waiting for help.

• You believe good software can make someone's day genuinely better, and that getting the small things right changes how someone's whole day goes.

• Writing that's short and clear. Every doc, release note and update you produce here gets read by an engineer, a CEO or a contractor. Sometimes all three.

• Being open-minded to change when someone shows you better information. You'll disagree with engineers who are more technical than you and salespeople who are closer to the money.

• You use AI tools to improve your work, but not own your judgement and taste. Show us what you've built with them.

• Construction, field service, payroll or ERP experience is a real advantage. Not required. However, being genuinely interested in an industry most tech people haven’t thought about is required.

• Be motivated that a foreman standing in the rain at 6am has a better morning because of something you shipped. If that reads as sentimental rather than as the point, this isn't the job.