Quick answer
What counts as an English-speaking job on this site?
The product is designed to surface jobs that are accessible to English-speaking candidates in Germany, then support that discovery with clearer context around language, role family, and relocation friction. That does not mean every source listing explicitly says "no German required," so the job detail page and surrounding context matter.
Job sourcing and freshness
Live jobs are kept discoverable through the main job routes, feeds, and sitemaps. Expired jobs are removed from the indexing path so the site stays aligned with current openings and avoids stale rich-result signals.
Editorial pages and reports exist to interpret the market around those jobs, not to replace the detail pages that search engines should treat as the source of truth for a specific opening.
Common methodology questions
Do you mark every listing as visa-sponsored or no-German-required?
No. Those are high-intent interpretations and should only be used when they are supported by source data or careful editorial review.
Why do some pages focus on workflows instead of only listings?
Because the product is designed around the full job-search journey in Germany: discovery, relocation planning, tools, and optional concierge support.
Where can I see the reporting layer?
The reporting layer lives in the reports section, which will grow into recurring market snapshots and sourcing-backed explainers over time.
If you want the editorial guardrails behind this approach, see the editorial policy.