how this board works
where the roles come from, how each one is judged to be product management, and how often that judgement is right.
where roles come from
Every role here is read directly from a company's own applicant tracking system — Greenhouse, Ashby, Lever or Workday — not scraped from another job board. Nothing is submitted by employers and nothing is sponsored. A role disappears from the board once it disappears from the company's feed.
what counts as a PM role
Core product management only: owning what gets built and why. Forward-deployed and solutions engineering, technical program management, product marketing, product design, product analytics and product operations are all excluded, even though every one of those titles contains a word that makes them look like a match. A title alone is not enough to decide — where it is genuinely ambiguous, the responsibilities are read before the role is classified.
why there is no fit score
An earlier version of this board scored each role against one person's background. That number meant nothing to anyone else, so it is gone. Roles are ordered by how recent they are and how completely the posting describes itself — a listing that states salary, seniority and sponsorship is more useful than one that states none of them — and everything else is a filter you control.
measured accuracy
Classification is checked against a hand-labelled set of real postings, weighted towards the cases that are easy to get wrong. Precision is the number that matters: this board can afford to miss a role, but not to show you a solutions architect.