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.
Quick answer
How does the MVP decide whether a job is English-language?
For the May 2026 launch, the public site only publishes jobs where the pipeline has detected_language set to en. This keeps the rule simple and auditable, but it is not the same as a verified no-local-language-required promise.
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.
Public job publishing is restricted to authorized ATS feeds, partner marketplace channels, or written-permission sources. The site does not commercially copy third-party aggregator HTML pages when there is no explicit API term or licensing basis to do so.
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.
Apply links stay redirect-only in this phase. Candidates always land on the original employer ATS page, and source attribution is appended only when the underlying source or employer setup supports it.
Known limitation: some listings in Spain, Italy, France, and other non-English-first markets include English boilerplate while still requiring a local language. Other jobs can be false negatives when local titles, mixed-language descriptions, or sparse ATS data hide otherwise English-friendly roles. The post-launch enrichment roadmap adds language confidence scoring, skill and title normalization, and candidate feedback loops before promoting stronger labels such as "Verified English-only."
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 opt-in email follow-up.
Do you copy jobs from aggregator pages if they have tracking links on them?
No. A tracking parameter can show attribution, but it does not by itself prove a syndication license. Aggregator sources need API terms or direct written permission before they are published commercially.
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. Employers who want to syndicate directly can use the post a job page.