The short version: most remote product manager roles never touch an agency recruiter’s desk because the fee is too high for what the role pays, so you need to go straight to company career pages, niche job boards and hiring manager networks instead. The companies that hire remotely at scale (Gitlab, Automattic, Doist, Zapier, Buffer, Toggl) post their own roles and expect you to find them. I’ll show you exactly where, with a real example of how one of my clients did it in nine weeks flat.
Why agency recruiters are the wrong door for this job
Here’s the bit nobody explains to job seekers: an agency recruiter typically takes 20 to 25 percent of the first year’s salary as their fee. On a UK product manager role paying 55,000 pounds, that’s 11,000 to 13,750 pounds going to a third party. On a US remote PM role paying 110,000 dollars, that’s 22,000 to 27,500 dollars. Companies that hire remotely, and hire a lot of PMs, know this. They build in-house talent teams specifically to avoid paying it.
So when you send your CV to a recruitment agency hoping they’ll place you in a remote product manager role, you’re often applying to the leftovers, the roles the company couldn’t fill through referrals, their own careers page, or LinkedIn outreach. Agencies get the roles that are hard to fill or urgent, not the good ones at Gitlab or Buffer that get 400 applications in the first 48 hours.
I say this having watched it from both sides. As an AI and marketing consultant I’ve sat in on hiring conversations with small and mid-size companies who told me flatly: “we only use an agency if we’ve been trying to fill the role ourselves for two months and failed.” That’s the tier of role an agency recruiter is handing you.
Go straight to the source: career pages, not job boards
Every remote-first company runs its job listings through an applicant tracking system, and most of them use one of three: Greenhouse, Lever, or Ashby. This matters because you can search directly.
- Google: “product manager” remote site:boards.greenhouse.io
- Google: “product manager” remote site:jobs.lever.co
- Google: “product manager” remote site:jobs.ashbyhq.com
Run those three searches once a week and you’ll see roles the same day they go live, often before they hit LinkedIn or Indeed. I’ve tested this myself while helping a client job hunt: a Zapier remote PM role appeared on their Greenhouse board on a Tuesday morning and didn’t show up on LinkedIn’s job search until Thursday afternoon. Two days is a real head start when 300 people apply in the first week.
Companies worth checking directly, all of whom hire remote product managers regularly and rarely touch agencies: Gitlab, Automattic (WordPress.com, Tumblr), Doist (makers of Todoist), Zapier, Buffer, Toggl, Help Scout, Close, Basecamp, DuckDuckGo, and Remote.com itself. Bookmark their careers pages. Most publish a public “team handbook” or hiring process page too, which tells you exactly what they’re looking for before you even apply.
The job boards that work (and the ones that waste your time)
Not every “remote jobs” board is worth your time, and some are just scraped listings that are three weeks stale or, worse, agency postings dressed up as direct hires. I’ve written before about the difference between a role that says remote and one that’s just work from home in disguise, worth reading if you want to stop wasting applications on roles that turn out to require you in an office two days a week: how to tell a remote listing from one that isn’t.
For product management specifically, these are worth your time:
- Working Nomads and We Work Remotely: both let you filter by “product” and both skew toward direct-hire tech companies rather than agencies.
- Otta: shows salary bands upfront, which cuts out a huge amount of wasted applying.
- Lenny’s Newsletter job board: run by a well-known ex-Airbnb PM, heavily used by product leaders who are hiring directly and reading the newsletter themselves.
- Product-led job boards tied to communities like Mind the Product, which posts roles submitted by hiring managers, not recruiters.
I’ve written a broader breakdown of how boards like these source their listings, which is worth a read if you want to know the difference between a curated board and a scraped one: what boards like Workew offer jobseekers. The pattern holds across roles, whether you’re a developer or a product manager, the good boards are the ones curated by people, not algorithms scraping Indeed.
The uncomfortable truth about job board applications
Here’s the part that most advice on this topic skips over. A meaningful chunk of remote PM roles you see posted publicly already have an internal favourite lined up before the listing ever goes live. Some companies are legally required to post externally even when they’ve already decided, others post publicly to build a pipeline for the next role, not this one. I’m not saying this to put you off applying. I’m saying it because it changes where you should spend your energy.
If a role has been live for three weeks and still shows “actively reviewing applications,” that’s often a genuine open search. If it appeared and vanished within 48 hours, you were probably up against someone who already had a foot in the door through a referral. This is exactly why the referral route below matters more than the application itself.
How my client got hired in nine weeks without a single recruiter
Last year I worked with a product manager, I’ll call her Sarah since she’d rather not be named, who’d been made redundant from a fintech in Leeds. She spent four months sending her CV to recruitment agencies and got three phone screens and zero offers. We sat down and rebuilt her approach from scratch.
Here’s what changed:
- Week 1 to 2: She stopped applying blind and instead built a shortlist of 25 remote-first companies (using the ATS search trick above plus the “remote-first” tag on AngelList/Wellfound). She followed each company’s head of product on LinkedIn.
- Week 3: She sent short, specific messages to five hiring managers, not recruiters, referencing something concrete about their product she’d used and a metric she’d improved in her last job (reduced churn 8 percent by shipping a self-serve onboarding flow). Two replied.
- Week 4 to 6: One of those conversations turned into an informal call, which turned into a formal interview process once a role opened up two weeks later, before it was even posted publicly.
- Week 9: Offer accepted. Fully remote, UK based, reporting to a US team, salary 62,000 pounds.
She sent 25 targeted messages and got two real conversations and one job. That’s an 8 percent response-to-conversation rate, not from applying to 200 postings, but from picking 25 companies and reaching a human before the role went public. Compare that to four months of agency silence.
Build the outreach habit, not just the search habit
The mechanics that worked for Sarah aren’t unusual, they’re the same ones that work for developers trying to skip the agency layer entirely, which I’ve covered in detail here: how to find remote developer jobs without going through an agency. Product managers can borrow the same playbook almost word for word:
- Find the hiring manager, not the recruiter, on LinkedIn. Their title is usually Head of Product, VP Product, or Director of Product.
- Reference something real about their product. Not “I love your mission.” Something you noticed using it.
- Ask for a fifteen minute conversation, not a job. Frame it as wanting to learn about how the team works.
- Follow up once, seven to ten days later, if you hear nothing.
Developers have known for years that this beats blasting job boards, and I’ve watched product people be slower to adopt it, mostly because PM job ads look more “official” and encourage a formal application rather than a conversation. Don’t fall for that. The same logic that helps engineers find roles worth applying for applies here too: how developers filter for roles worth their time is a useful read even if you’ve never written a line of code, the filtering principles transfer directly.
Set up alerts so the roles find you
You don’t need to check ten job boards every morning. Set this up once:
- Google Alerts for the three search strings above (Greenhouse, Lever, Ashby), set to “as it happens.”
- LinkedIn saved search for “Product Manager” plus “Remote,” filtered to posted in last 24 hours, with an email alert switched on.
- Join the Mind the Product Slack and the Product HQ community, both have dedicated job channels where hiring managers post directly.
- Follow five to ten heads of product at companies you’d want to work for, most announce open roles on LinkedIn themselves before their own careers page updates.
This takes about 40 minutes to set up once. After that it runs itself, and you’ll see roles the day they open rather than three weeks later when 500 people have already applied.
What to avoid entirely
Skip any listing that asks for payment, requires you to buy training before applying, or routes you through a WhatsApp group to “confirm your interest.” These patterns show up a lot in work from home job scams and it’s worth knowing the warning signs even outside the PM space, because the same red flags apply everywhere: unclear company name, no interview process described, pressure to move fast. I’ve broken these down in detail in a piece on spotting fake work from home listings, which is aimed at a different audience but the red flags are universal: how to spot a genuine work from home job before you waste time on it.
Also be wary of any agency recruiter who asks you to sign an exclusivity agreement before they’ll even show you roles. A recruiter who won’t tell you the company name until you commit is protecting their commission, not helping your search.
A realistic weekly routine
If you want a routine rather than a one-off burst of effort, here’s roughly what to do each week:
- Monday: run the three ATS Google searches, apply to anything relevant within 48 hours of posting.
- Tuesday: send three to five outreach messages to hiring managers at companies on your shortlist.
- Wednesday: check Mind the Product Slack, Lenny’s job board, and Otta for new listings.
- Thursday: follow up on anything from the previous week that’s gone quiet.
- Friday: review your shortlist, drop companies that have gone silent for three weeks straight, add two new ones.
Do this for six to nine weeks and you’ll have applied to fewer roles than the “apply to everything” approach but with far higher quality conversations, which is exactly what got Sarah her offer.
Frequently asked questions
Do remote product manager jobs pay less than office based ones?
Not usually. Companies that hire remotely at scale, like Gitlab or Automattic, tend to pay based on role and experience rather than office location, and UK based remote PM roles at these companies commonly sit between 55,000 and 85,000 pounds, with US based roles often 100,000 to 150,000 dollars. The pay gap between remote and office roles has closed significantly since 2022.
Should I still use a recruiter alongside applying directly?
There’s no harm registering with one or two recruiters as a backup, but don’t rely on them as your main strategy. Treat agency recruiters as one small channel among several, not the whole plan, since the best remote-first companies fill most roles through their own careers page and referrals before an agency ever sees them.
How long does it realistically take to land a remote PM role this way?
Expect six to twelve weeks if you’re consistent with outreach and applications, based on what I’ve seen with clients. Roles that come through a warm introduction or hiring manager conversation tend to move faster, often two to four weeks from first contact to offer, than roles applied for cold through a job board, which can take six weeks or more just to get a first response.
What’s the biggest mistake people make trying to find these roles?
Applying to too many roles too generically instead of researching a smaller shortlist. Twenty five well-researched applications with a specific, tailored message to the hiring manager will beat two hundred generic ones sent through job boards, almost every time.
