Senior Product Manager

LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, and they are seeking a Senior Product Manager to join their team. The role involves owning significant initiatives related to customer acquisition, service delivery, and AI-driven efficiency while collaborating cross-functionally to drive measurable business outcomes.

Responsibilities:

• A workstream within a swim lane : full ownership of multiple initiatives tied to a 2026 bet, whether that's customer acquisition, service delivery and retention, or AI-driven operating efficiency
• Problem definition : turning ambiguous, multi-layered problems into a clear "here's what we're solving and why" that earns cross-functional buy-in
• Metrics ownership : a specific business metric (conversion, retention, Pro supply, cost-to-serve) you're accountable for moving, not just influencing
• Cross-functional execution : driving a dedicated engineering/design pod from problem to shipped outcome, including calls on what NOT to build
• AI-forward workflow : using AI daily in your own work, and pushing your team to find where it compresses timelines too

Requirements:

• AI-native. You use AI daily to move faster: drafting specs, exploring data, prototyping, cutting busywork. You try new capabilities because you're curious, not because someone told you to. Unlikely to be a good fit if you're skeptical of AI or treat it as a novelty
• Exceptional at data, or exceptional at customer taste: truly great at one, and at least good at the other. Some of our best PMs are ruthlessly data-driven, reaching for the number before the opinion. Others build extraordinary product taste by living inside customer and Pro feedback until they can predict what people want before the data confirms it. Either path works. What doesn't work is being moderately competent at both and exceptional at neither
• A structured thinker in unstructured situations. You dig into problems before jumping to solutions, asking the questions that turn a simple-looking ask into the real problem underneath. If you're most comfortable executing a well-defined spec rather than defining one, this isn't the seat for you
• An excellent communicator who says no with reason. Core to this job: articulating the problem, earning buy-in in writing, and saying no to good ideas that just aren't right now. That means carving out time to think and write clearly, and it means not avoiding difficult conversations. If either of those isn't you, this role will grind you down
• Bias for action. You think problems through without tipping into perfectionism, and you're comfortable shipping something scrappy and iterating from there. Unlikely to be a good fit if you default to building the full, polished version before it's in front of real users