What “remote” actually means in European product hiring right now

Of the 1,655 live product roles on the index today, 268 — about one in six — are advertised as fully remote. Another 431 are hybrid, 305 are onsite, and 630 don’t state a policy at all. That last number is the quiet scandal: four years after remote became a first-class working model, 38% of European product listings still make you guess.

Remote ≠ remote

Within the fully-remote pool, scope varies enormously. Only around 30 roles are genuinely location-agnostic (“work from anywhere”). A larger group — roughly 50 — are remote within the EU or EMEA, usually for payroll and compliance reasons. The rest are remote within one country: a “remote” contract that still requires German tax residency, or UK right-to-work.

The practical consequence: if you’re in Lisbon and the ad says remote, the real question is whether the employer can put you on a Portuguese payroll or works with an employer-of-record. Companies hiring remote across many EU countries at once — GitLab, Camunda, Planday among the current listings — say so explicitly, and that explicitness is itself a maturity signal.

Does remote pay less?

The disclosed-salary pool is too small to be definitive (see our salary-transparency brief), but in it, remote roles do not price below anchored ones — the disclosed remote medians actually sit slightly higher. The “remote discount” we could measure is a discount in certainty, not in pay: remote listings state salary slightly less often.

How to search accordingly

• Filter remote, then read for scope words: “EU”, “EMEA”, “CET±2” are real constraints, not decoration.
• A country-anchored remote role in your own country is often the best of both — local contract, no office.
• On the index, remote roles carry a Global or EU label rather than a fake city, so a “Berlin” chip always means Berlin.