You'll be the person who figures out what Firecrawl should build next , and why. Right now, our engineers are shipping great infrastructure, and our support and sales teams are handling inbound well. But the bigger product bets , the ones that turn a good tool into a dominant platform , are stalling because nobody has the bandwidth to do real customer discovery.
This isn't a PM role where you write tickets and manage a backlog. You're in the field. You talk to customers , a lot of them. You find the patterns, source the insights, and bring them back to the team in a way that changes what we prioritize. You're the bridge between what developers are actually trying to do and what we're building.
Talk to customers constantly. This is the job. You're running 15-25 customer conversations a week , discovery calls, user interviews, onboarding sessions, churn conversations. You're not surveying people. You're having real conversations that uncover what they're building, where they're stuck, and what would make Firecrawl indispensable to their workflow. You develop a sixth sense for what customers say versus what they actually need.
Find the insights that change priorities. You don't just report what customers said , you synthesize it. You spot the patterns across dozens of conversations and turn them into clear, actionable product recommendations. "Here's the use case we're missing, here's how big it is, here's what we'd need to build, here's why it matters now." You bring receipts.
Own customer discovery for new product surfaces. When the team is exploring a new direction , a new endpoint, a new pricing model, a new market segment , you're the person who goes deep. You map the landscape, talk to the right people, and come back with a clear picture of whether it's worth pursuing and how to win. You've done this at the 0-to-1 stage and you've done it at scale. You know the difference.
Be the voice of the customer in every product conversation. You're in the room when product and engineering decisions are being made. Not to slow things down , to make them sharper. You bring real user context that prevents the team from building technically impressive things nobody asked for.
Close the feedback loop. When the team ships something based on your research, you go back to the customers who informed it. You validate. You measure. You learn. Discovery isn't a one-time phase , it's a continuous cycle that compounds the more you do it.
Create content from customer conversations. The best product research doubles as marketing. Customer stories, use case write-ups, product positioning insights , you naturally produce content that helps the team sell and market, not just build.
XML job scraping automation by YubHub
