How we curate this board (and what never makes it)

workinproduct is a curated index, and “curated” is doing real work in that sentence. Here is what happens between a company publishing a product role and that role appearing on this site — and what gets filtered out on the way.

Source: employer career sites only

We collect directly from company applicant-tracking systems — Greenhouse, Lever, Ashby, Workday, Teamtailor, SmartRecruiters, Recruitee and a growing list of others — never from aggregator feeds. Direct sourcing means the apply link goes to the employer, the posting date is real, and when a role closes at the source it closes here. No zombie listings scraped from a scrape of a scrape.

Scope: Europe-born, not EU-only

The gate is where a company is from and hires, not a passport list. UK, Swiss and Norwegian companies are in; a US-headquartered firm’s Berlin product team is in; a “remote (US only)” role at any company is out. Every listing is location-classified — work locations, remote scope, country — and roles that would require you to live outside Europe never reach the board.

Enrichment: structure before judgement

Raw job ads are unstructured prose, so we extract the fields you actually filter on: seniority, role type (PM, PO, product lead, product marketing, design, ops), remote policy and scope, salary where disclosed, skills and language requirements. Each listing then gets a quality score; postings that are too thin to judge — no description, no team context, no way to tell what you’d be doing — don’t publish.

What never makes the board

• Agency and bench postings — if the employer isn’t the company you’d work for, it’s out.
• Ghost roles: listings that vanish and reappear to look fresh keep their original age here.
• Non-product roles wearing the title: “Product Manager (industrial equipment sales)” gets classified out.
• Anything requiring relocation outside Europe.

The pipeline runs nightly, with fresh roles landing during the day as sources update. When something slips through — it happens — every job page has a feedback control, and reports feed straight back into the filters. The board you’re reading is the pipeline’s output, and this article is its contract.