Language pair pages
Each pair or role has its own page covering document types and the test process.
A translation agency depends on a network of freelance linguists and a small team of project managers, and both are hard to recruit. A recruitment website for translation agencies lists each opening by language pair or role, takes a short application form and routes it to the person who will test the candidate.
A translation agency recruits in two different markets. One is freelance linguists, who may work from a dozen countries and need a clear answer about language pair, document types and the test process. The other is in-house project managers, who want to see the client mix and how projects are run day to day.
Both groups judge the page within seconds. A linguist wants to know whether the agency handles their language pair and their subject areas. A project manager wants to know which tools the team uses and how work is divided between desks. A generic careers page answers neither question.
So the site should list each language pair as its own opening, explain the test process in plain steps and name the translation tools the team uses, such as memoQ or Trados Studio. Those details filter out poor fits before anyone spends time on them.
The first release should cover one page for each language pair or in-house role, a short application form with CV upload and routing rules that send each application to the coordinator who runs the test. Those three parts let the agency take on new linguists without a shared mailbox acting as the candidate list.
A searchable skills database, automated test delivery and a payments portal for linguists can wait. Each one adds personal data and system links, and each is easier to design after the first intake of applicants has shown what the agency actually needs to store.
A freelance translator working from Spanish into English finds the Spanish to English page through a search result. The page explains the document types covered, the test process and how work is offered. The application asks for a CV, the tools the translator uses and a short sample of recent work, which takes about ten minutes.
On submission the translator gets a reference number and a message confirming the test window. The application goes to the coordinator for that pair, who sends the test document and a deadline. Results return to the same record, so the agency can compare candidates for one pair without rereading every CV.
Each pair or role has its own page covering document types and the test process.
A CV, a language list and a few answers take about ten minutes to complete.
Each application reaches the coordinator for its language pair.
Successful applicants receive the test with a clear deadline and a return route.
Candidates receive standard notes at each stage, written once and edited when needed.
Freelance linguists are usually independent contractors, so the site should describe the working relationship accurately and avoid promises about hours or volume. If the agency pays people outside the United States, tax forms and payment rules differ by country, and the application should say which documents will be requested later.
Linguists who handle confidential or export-controlled material may need to sign a non-disclosure agreement or pass a check that the client requires. The site should say that such checks exist. Applicants in the European Union fall under GDPR, so retention and consent wording should be agreed with the agency's own advisers before launch.
The main cost drivers are the number of language pages, the depth of the application and the systems that must receive each applicant. A small site with a handful of pairs and one routing rule costs less than one with dozens of pairs and an onboarding portal. Pricing starts at $300 and rises to $2,200 for larger scopes, and we confirm the final figure in writing.
The timeline depends on the list of language pairs and on the test process, and both need approval before design begins. Agreeing them in one session keeps the work moving, while late changes to the test rules push the build back a step.
To keep scope under control, we fix the first set of pairs and roles at the start and treat new ones as separate additions.
Track applications per language pair, the share that pass the test and the days from application to test invitation. Those figures come from the coordinator's records, so the agency can compare them with its current process before launch.
Quality is the more useful measure. Ask coordinators to rate each pass honestly, and watch whether the linguists who join keep taking work after their first few jobs. A rising count of applications means little if the pass rate falls to nearly zero.
Yes. Freelance language pairs and in-house roles sit in separate sections, each with its own application. Linguists see only the freelance listings, and project managers see the in-house roles, so nobody scrolls past openings that do not apply to them.
A general expression of interest form captures the language pair, the subject areas and availability. The coordinator reviews those records and uses them when a new pair is added. The form makes no promise of work.
Only if the agency decides so. Many teams use a short test for each language pair, and the site explains the test and its deadline before the application starts. We set the test rules with your coordinators during scoping.
It keeps what the application needs: contact details, the CV, language pairs and test results. The agency sets retention periods and any consent wording with its advisers, and applicants can be told how long their details are held. Long-term storage of unsuccessful applications should be a deliberate choice, not a default.
Send us your language pairs and open roles, and we will return a written scope and price once the free scoping call is complete.