Expertini ATS, internationally
The platform runs as a separate deployment for each language, on its own domain. Pick the one you hire in — your account, jobs and candidates are the same whichever you use.
Language affects what you read, not how anyone is assessed. The Candidate Match Score is produced by one published formula in every language, and screening reads a CV in whichever language it was written against a job description in whichever language you wrote it.
Labojumi ir laipni gaidīti. Ja kaut kas jūsu valodā izklausās nepareizi, informējiet mūs uz support@expertini.com, un mēs to salabosim.
Why a separate domain per language
Each language is served from its own host rather than a path or a cookie, so a page is never assembled from two languages and a link you share opens in the language you were reading. Every version cross-links to every other, which is what lets a search engine treat them as one product in many languages rather than as duplicates competing with each other.
Reading across languages, not just displaying them
Displaying an interface in German and understanding a German CV are different problems, and most recruitment software solves only the first. Keyword matching fails at a border — Teamleitung and team leadership share no characters — so a candidate who wrote in their own language scores zero on a competency they demonstrably have, silently. How semantic matching handles that covers the mechanism and its limits.
What is not translated, on purpose
Job categories, employment types and country names are shown in your language, but the identifiers underneath them stay constant — they are how a job published here is matched onto the country job sites, and what structured data reports to search engines. City names are not translated either: they are the addresses of hundreds of thousands of location pages. The full account of what is localised and what is not.