Senior Product Manager

Welcome to Campspot! Whether you are an avid camper, the occasional glamper, an expert RV-er, or new to the outdoors entirely, we're interested in working with you. Our team values diverse perspectives as we seek to create an easy-to-navigate and meaningful camping experience for everyone.

We hope you will consider joining our team! ALL human beings are welcome, and we are committed to helping you thrive here. We believe our team, as well as the outdoors, is for everyone.

You will own a slice of Campspot's business — a customer problem, the outcome it drives, and the product that solves it. Today, Campspot is the leading Campground Management Software, and you will work to make it even better.

AI is changing where a product manager's time goes. Specs, user stories, research syntheses, status decks, and the translation layer between customers and engineers can now be produced in minutes. We are looking less for someone who produces them faster and more for the judgment those documents were always meant to contain: knowing which problems matter, how to create real value, and when to kill a plausible idea.

The scarce thing is no longer whether we can build something. It is whether we should, and whether it got used. That is the heart of the job.

• An outcome, not a backlog. You are accountable for a business result in a defined part of the product — a revenue line, a retention number, an adoption rate — and for the customer segment behind it. Features are how you get there, not what you are measured on.
• The customer, unmediated. You will come to know campground operators deeply: their economics, their seasonality, their business problems, how they actually make decisions. You will get that by talking to them directly and often. You will build that understanding firsthand.
• The first version. The spec is a working prototype. When you have a hypothesis, you will build it — with AI tools, with our data, with whatever gets you to something clickable and testable in a day — before an engineer touches it. Engineers get a working input, not a document.
• The decision to kill. Building is cheaper now, so you will have no shortage of plausible options. Your job is to choose, to say no, and to keep the product coherent instead of letting it fragment into a hundred locally-reasonable features. You will hold a wider scope than a traditional PM, and that means more things you decline than things you ship.
• Whether it worked. You define success before you build, instrument it, and run the loop honestly. Shipping and course-correcting are cheap; not noticing is not. You will own the measurement, not delegate it.
• Adoption. In our market the hard part was never the build. It is getting a park manager to change how they work. Rollout, change management, customer communication, and working with our customer-facing teams are the core of the role, not an afterthought once engineering is done.

We want this to be a good fit for both of us, so it helps to be clear up front. This role may not be right for you if:

• Your proudest work is a document. A great PRD, a thorough competitive analysis, a beautiful roadmap deck. We value the thinking behind them more than the artifact itself.
• You measure your week by how much you shipped, how many stories you wrote, or how many stakeholders you aligned. We measure it by what customers did differently.
• You need engineers to build your ideas before you can see whether they are any good.
• You are looking for a role where process ownership — running ceremonies, grooming backlogs, keeping Jira clean — counts as impact. We have those things. They matter, but they are not the core of the job.
• You are most comfortable when the plan is settled before you act.…