A global hiring funnel reaches people who have no company account, no HRIS record and no working language set against their name. This is how candidate surveys run in over a hundred languages and still come back as one score, inside the wider candidate experience platform.
Book a free, no-obligation product demo call with our experts.
One survey, over a hundred languages, one score
By the time someone joins, they have an account, an HRIS record and a language set against their name. A candidate has none of that. They are reachable for a few weeks, on a personal address or phone, often in a country where your working language is their second or third. An English-only survey does not fail loudly at that point. It just comes back thinner, from the people most comfortable answering in English.
Sample figures. The share worth watching is the third one: an English-only survey pushes people into it, and the candidates it loses are rarely a random sample of your funnel.
The translation layer is the same one already running on your employee surveys, which is what keeps a candidate score and an employee score comparable rather than being two separate programs that happen to share a logo.
Worth being precise about, because "multilingual" is used loosely and the parts have different scopes. The candidate experience survey itself is translated in full; the surrounding email is scoped to launch and reminder messages.
| Part | Translated | Notes |
|---|---|---|
| Stage survey questions | Yes | Each question carries a translation per language, generated when the language is added and editable under Survey Settings, Translations. |
| The 0 to 10 scale and its labels | Yes | Scale labels translate automatically and are editable per language. The candidate NPS question also carries its own customizable title per language. |
| Survey launch and reminder emails | When enabled | Local-language sending covers launch and reminder emails. Templates are not translated by default; it is switched on per account. |
| Open text answers | On reading | With translation enabled, free text exports carry a translated column, so a comment in Portuguese is readable without a separate step. |
| A language you corrected by hand | Re-generated | Updating the English re-generates every translation, so a hand-corrected language is worth re-checking after a wording change. |
The reason to run this on one platform rather than a survey tool per region is that the answers stay in one dataset.
A survey in someone’s own language still has to arrive somewhere they look. A candidate has no company inbox, so delivery runs to the personal address or number you hold for them, over the channels they already use, the same set the candidate experience survey program uses at every stage.
Multilingual candidate surveys are candidate experience surveys presented to each candidate in a language they can answer comfortably, rather than in a single company working language. In a global hiring funnel that matters more than it does for employees: a candidate has no company account and no HRIS record, and is often applying in a country where your working language is their second or third. CultureMonkey runs them on the same translation layer as its employee surveys, as part of a wider candidate experience platform.
Over a hundred. The same set your employee surveys already use, because it is the same account configuration rather than a separate candidate list. You choose which of them your account listens in, and only those appear as options.
Both, in that order. Translations are generated automatically when a language is added to the account, and updating the English re-generates them, so a program is never blocked waiting on a translation vendor. Every language can then be edited by hand under Survey Settings, Translations, and those edits stick. In practice the edits worth making are role titles, internal team names and anything with a legal meaning; general question wording usually survives machine translation intact.
No. A translated question is treated as the same question, so scores are computed across the whole cohort and language becomes another way to cut the results rather than a separate report. That is the practical argument for one platform over a survey tool per region: comparing a Spanish-speaking cohort with an English-speaking one is a filter rather than a reconciliation exercise.
Yes. Free text exports include a translated column when translation is enabled for the account, so a comment left in Portuguese or Japanese is readable without a separate step. This matters more than it sounds: the open text is where candidates explain a score, and a program that can only read comments in the languages its HR team happens to speak is quietly discarding the most useful half of the response.
Yes. Candidates have no company inbox, so delivery runs over email, WhatsApp and SMS, and the language and the channel are separate choices. Reaching someone in their own language on a channel they do not check is the same miss as reaching them on the right channel in the wrong language. The candidate experience survey program uses the same delivery at every hiring stage.
Over a hundred languages, five channels, one score across all of them.