What the real interview was like

1. Account setup and general onboarding.
2. A project screener with written evaluation tasks.
3. A course described as paid training.

• Detailed written evaluations that needed careful answers.

• Self-paced, with no interviewer.
• Took about four times the advertised 75 minutes.

• →Allow far more time than the advertised screener length.

Onboarding failed, with no reason given.

1. Identity check with both sides of a government ID.
2. A native-language qualification test.
3. Project-specific assessments.

• Native language proficiency.
• Spotting audio quality problems and following the guidelines closely.

• Demanding but fair for anyone who studies the instructions.

• →Study each project's instructions before its assessment.
• →Practise spotting audio quality issues.
• →Write clear explanations in simple words.

Passed and went on to steady weekly work.

1. Enrolled in the project.
2. Repeated unpaid evaluation rounds.
3. Surprise video and audio recording assessments.

• Recorded video and audio submissions.

• Felt like a loop of tests with no path to paid tasks.
• The recordings raised privacy worries.

• →Ask before starting whether recordings are required and how they are used.

Never reached paid work.

1. Signed up, then chose location, languages and specialism.
2. Identity and phone verification with a photo ID.
3. Uploaded a resume and picked areas of expertise.
4. A screening exam; no video interview for this track.
5. Guided training modules, then placed in a team with a lead.

• A screening exam for the content reviewer track.
• Training modules on the tools and task guidelines.

• No AI or live interview for this role, only a written screening.
• Onboarding was long and demanding, more than simple clicking.

• →Have your ID ready before verification.
• →Read each task's guidelines closely.
• →Set aside several hours for onboarding.

Passed, joined a team and received a small onboarding payment.

1. Removed from the German version of a project for not being fluent enough.
2. Passed the screening for the English version of the same project.
3. Stayed blocked by the old German restriction.
4. A multilingual exam retake was required.

• A project screening in English.
• A multilingual language exam, retaken under pressure.

• Support replies were polite but generic.

• →A failed language project can carry over as a block on related projects.
• →Keep a written record when a qualification seems wrongly blocked.

Failed the multilingual retake and could not keep working.

1. Signed up.
2. Identity and phone verification.
3. Nine separate coding screenings, one per language, over about a month.

• Screenings in Python, Java, Go, Dart, C++, C#, JavaScript, Swift and Verilog.

• Unpaid, self-paced screenings with no live interviewer.
• Took a lot of time across many languages.

• →Passing a screening does not guarantee paid work.

Passed all nine, but had no paid tasks when the review was posted.