Fountain Live Translations helps applicants apply to jobs even when the Opening is not initially created in their preferred language.
This helps reduce manual efforts by Fountain Administrators when creating openings because the opening can be created just once in the Administrators' preferred language rather than needing to be duplicated multiple times in the languages that need to be supported. This feature also increases the potential applicant pool for jobs where language is not a factor.
Add Live Translations to an Opening
Follow the steps below to add the Live Translations feature to an opening.
On the Openings screen, click Add Opening.
Select a Location and Position and name the Opening.
Click Continue.
On the next Opening Details screen, enter in relevant details.
In the Alternative Languages box, click to select all languages you want the application to be able to be translated into.
Click Continue.
Fill in the Application Form fields as usual, click Continue.
Choose Create new workflow or Clone existing workflow.
Build or adjust the workflow in your preferred language.
Important Note:
You can add Live Translations to an existing Opening by clicking the 3 dots button to the left of the Opening on the Openings screen and clicking Edit Job Details.
Configure Custom Terminology
Custom Terminology lets you upload a terminology file that enforces specific translations for domain-specific terms across all dynamic translations in Fountain.
When a term in your file is encountered during translation, Fountain uses your specified translation instead of the default machine translation. This is particularly useful for job titles, equipment names, and industry-specific vocabulary that are frequently mistranslated by generic translation engines.
Once uploaded, the terminology file applies automatically to all dynamic translations across job descriptions, questions, and message templates. A single file covers all language directions — you do not need to maintain separate files per language pair.
Prepare the Terminology File
The terminology file must be a CSV formatted as follows:
Use language codes as column headers (for example,
en,es,fr)Each row contains a translation pairing — provide one word or phrase per row in each language
Each term can be at most 100 characters long
The file must be at most 10MB
A single file covers all language directions — you do not need to maintain separate files per language pair.
Example file structure:
en | fr | es | de |
Hello | Bonjour | Hola | Hallo |
Upload the Terminology File
Click your company logo in the bottom left corner, then click Settings.
Under Company Settings, click Translation Settings.
Under Custom Terminologies, click Download Sample File to download a pre-formatted CSV template, or click choose file to upload your completed file. You can also drag and drop your file into the upload area.
Once uploaded, the terminology file takes effect immediately across all dynamic translations in your account.
To replace the terminology file, upload a new CSV file by clicking Replace on the existing file. The new file replaces the existing one instantly with no downtime or manual cleanup required.
Applicant Experience
Once Live Translations are enabled within an Opening, your applicants will see the change language dropdown in the top right corner of the initial application screen.
If the applicant is using a different language for their internet browser, and that language has been selected via the Alternative Languages box during Opening creation, they will see a message at the top of their screen asking if they would like to switch the application to that language.
Recruiter Review of Applicant Profile
If an applicant has changed the language via the language dropdown, the chosen language is visible on the Applicant Table in the Application Local column.
When reviewing the Applicant's profile, their answers to Data Collection questions will be in their native language. To change the answers to English, click View in English.
Feature Limitations
Below is a list of current feature limitations.
The only stage types that will be translated in full are Data Collection, Video Recording, and Multi-stage.
Stage titles and descriptions for any stage type will be translated but the content within other stage types, such as W-4 or I-9, will NOT be translated.
Option Banks are not supported.
Job Descriptions must be under 10,240 characters.
Custom Terminology applies to dynamic translations only. Static UI elements and system-generated text are not affected by the terminology file.






