In order to make sure everyone who works on paid tasks with us is able to deliver the standard of work we require, we have to test our editors at sign-up. It’s just common sense – if we didn’t do this, anyone would be able to register and work on tasks for a language that they don’t understand. Most of the jobs you’ll be doing go straight to our customers, too - it’s a great responsibility on your part.
There are two steps to becoming a paid editor with us: verification tasks and training tasks.
These are the tasks that you’ll do when you first sign up. These are designed to clear up two things for us – that you have an understanding of the language you’ve signed up for, and that you’re not a robot or using any artificial translation tools.
Don’t worry too much about polishing these tasks – just correct the errors and move on. These tasks are graded automatically on a pass/fail metric, and once you’ve passed you won’t ever have to do them again for that language pair.
The training tasks are the core of the sign-up process. They are texts specifically selected and designed to evaluate your competence as an editor.
What do I need to do? It’s simple – just complete ten training tasks. There’s no need to complete more than ten, but you’re welcome to continue practising if you’d like. Once you’re done, a random selection of these tasks will be graded by one of our evaluators.
What are you looking for and how can I prepare? Here we’re looking at a number of factors to determine whether we’ll give you access to paid tasks. Take a look at the list below and the corresponding links to resources on how to succeed in your evaluations.
- The first thing that we’re looking for, of course, is whether you’ve produced a good translation. We’ve got a detailed guide on what this means, which you can read here.
- Are the editions in line with the language guidelines?
- Has the editor correctly post-edited the text, bearing in mind the instructions and register?
We never accept any other proof of language ability – you can read more about why here.