What the real interview was like

1. An AI interview in English.
2. An AI interview in Spanish.

• Spoken answers in Spanish, with the interviewer remarking on word choice along the way.

• The English interview felt complete and comfortable.
• The Spanish one kept suggesting other words and sounded defensive when challenged.

• →In Spanish, expect comments on your vocabulary. Keep your rhythm and carry on.
• →If you can choose, think about which language shows you at your best.

Not stated.

1. One AI interview with Zara for a role in a language other than English.

• Questions built around English technical terms, even though the role was not in English.

• Natural and respectful in tone.
• Interrupted the candidate and could not handle many of their questions.

• →Learn the English technical terms for your field, even for a job in another language.

Not stated.

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. Applied through a job listing.
2. Several exam rounds back to back, about four hours in total.
3. Failed one exam, which ended the application.

• Rank items on scales from moderate to highest.
• Judge how well search results meet a need, on a meets-style scale.

• No interviewer: written exams.
• The ratings felt subjective and the criteria unclear.

• →Expect several hours of unpaid exams.
• →Learn the rating scale definitions in the guidelines before you start.

Failed one exam and was dropped.

1. Unsolicited outreach from a recruiter.
2. Automated replies said to take the tests before any role or pay details.
3. A Dutch proficiency test, failed twice.
4. Passed on the third attempt.

• A Dutch language proficiency test, which the candidate felt had grammar mistakes of its own.

• Automated replies only, with no role or pay details before testing.

• →Ask for pay and role details before investing time in tests.

Passed on the third attempt, then chose not to continue.

1. Accepted after about three weeks.
2. Learning materials, then a qualification exam with a seven-day window.
3. Part one: timed rating tasks.
4. Part two: tasks needing a phone to check an app and video links.

• Rate ads and results on a set rating scale.
• Check an app and video links on a mobile phone.

• Per-task timers were not explained beforehand.
• Support took four days to reply.

• →Start early in the exam window in case access fails.
• →Have a phone ready for the second part.
• →Watch for per-task time limits.

The exam closed early with no result.

1. A microphone check by saying a short greeting to the AI.
2. An AI interview including a pronunciation assessment.

• Pronunciation in a tonal language.

• Judged tones accurately.
• The microphone check gave no clear sign that audio was captured.

• →Test your microphone separately before the interview.

Not stated.

1. One AI interview, available in French and English.

• Questions built on specific examples from the CV.

• Fluent in both languages.
• The questions felt well designed and relevant.

• →Know the examples on your CV well, since the questions build on them.

Not stated.

1. Invited to projects, though links often failed.
2. A French assessment covering speaking and writing.
3. Early encouragement, then an email saying they did not qualify.

• Spoken French.
• Written French.

• Mixed messages: early encouragement, then a rejection.

• →Passing the language test does not guarantee a project place.

Told they did not qualify for the project.