Salary disclosure leaderboard: who publishes, who doesn't

What counts as "disclosed"

Any non-empty salary string in the source listing. A range ("$120,000 - $160,000"), a single number ("$140,000"), or an hourly equivalent all qualify. The Real Remote Score's compensation pillar separately rewards range-vs-single (25 vs 10 points) - see the RRS methodology. For this leaderboard the question is simpler: do you publish a number at all.

Why this matters now

The EU Pay Transparency Directive (2023/970) takes effect 7 June 2026. From that date, employers hiring into EU jurisdictions have to publish pay ranges or disclose them on request. The leaderboard above is what compliance looked like going into enforcement, which began on 7 June 2026. Some named employers are at 90%+; some are at zero. They will all be subject to the same rules.

Read the directive's RemNavi explainer at /eu-pay-transparency/, including country-specific playbooks for Germany, France, Netherlands, and Ireland.

Reproduce

# Top 50 employers ranked
curl 'https://remnavi.com/jobs_api.php?facet=salary_disclosure_by_company' | jq

# Just the corpus-level number
curl 'https://remnavi.com/jobs_api.php?facet=salary_disclosure_by_company' \
  | jq '{total: .corpus_total, disclosed: .corpus_disclosed, pct: .corpus_disclosure_pct}'

# Cross-reference with the hybrid mix and the repost rate
curl 'https://remnavi.com/jobs_api.php?facet=hybrid_mix' | jq
curl 'https://remnavi.com/repost_clusters.php?top=0' | jq '.summary'

All four endpoints are CORS-enabled and CC-BY licensed. See /api/ for the full reference.

Companion editorial

• Hybrid Transparency Score - how clearly hybrid employers disclose their in-office expectations.
• Ghost jobs - repost-cluster analysis across the corpus.
• Corrections log - appeal a result or flag a misclassification.