Turing's screening is longer than most AI-training platforms. There's usually a proctored assessment and then one or more interviews, and you may wait weeks between steps. The good news: Turing publishes a fair amount about how it works. Here's what it says, and how to get through it.
What Turing's screening actually is
Turing's help centre describes the same broad stages for most roles:
- Profile. You create an account, upload an English résumé and confirm your education, skills and languages.
- Application. You apply to a specific role and fill in a short form.
- Initial screening. Depending on the role, this is a screening call or an assessment.
- Interviews. Technical or role-specific rounds. Turing says an interview is typically required for every role.
- Final evaluation. A last interview or panel, then reference checks.
- Offer and onboarding.
The exact mix depends on the role and the client. A coding trainer role and a finance expert role won't test the same things. Third-party reviews describe AI-led interviews and coding tests on some roles. Turing doesn't publish one fixed format, so read each listing.
The assessment is proctored
Turing's help centre is clear about this:
- Screen: you share your entire screen. Sharing one window or tab can pause the recording.
- Camera and mic: both on. Virtual cameras and audio devices, such as OBS or an iPhone used as a webcam, get your attempt invalidated.
- Pauses: if you stop screen sharing, audio or video more than four times, you're disqualified from that test automatically. You then can't retake it for 90 days.
- Browser: Chrome 74 or later, Edge 79 or later, or the latest Firefox. Not incognito. VPN, ad blockers and extensions off.
ID comes later
ID verification happens at onboarding, after you're selected. Turing accepts a driver's licence or passport, and digital versions of national IDs aren't accepted. The name on your ID has to match your profile.
How to prepare
Setup checklist
- One computer, one screen, built-in or USB webcam and mic.
- Chrome, normal window, extensions and VPN off.
- Close Zoom, Teams, Slack calls and anything else that can grab your camera.
- Grant camera, mic and screen permissions in your system settings before you start, then refresh.
- Plug in your laptop. A sleep or battery warning can kill the screen share.
- Block out more time than the test says. Leaving halfway isn't an option.
Before the interviews
- Read the listing line by line. Turing scores you against the role's requirements. Note every skill named and prepare one example for each.
- Fix your profile first. Turing's help centre says an up-to-date profile is what the matching engine uses to find you roles. Make the profile and your résumé tell the same story.
- Prepare three work stories. A hard problem you solved, a mistake you caught, and a time you followed a strict process. For a trainer role, one should be about judging quality: reviewing code, checking a report, marking work.
How to answer
- Think out loud. Say what you're checking and why. Interviewers can't score reasoning they don't hear.
- Be concrete. "I reviewed pull requests for a payments team. Most bugs I caught were edge cases in currency rounding." Real details from your own work make you believable.
- Read every task instruction twice. Assessments often hide the key rule in one line. Answer what was asked, not what you expected.
- Say when you don't know. Then explain how you'd find out. Bluffing gets caught in the follow-up.
- Don't use AI tools. Turing's offboarding policy treats AI-generated work, or using AI to solve or explain tasks, as grounds for removal, non-payment and a permanent ban.
Common reasons people fail
- Proctoring breaks. Four pauses and you're out for 90 days. Most are avoidable with setup.
- A thin profile. If your profile doesn't show the skills the role needs, you may never be shortlisted.
- Over-claiming. Listing ten languages or tools you can't discuss in depth.
- Short answers with no reasoning. Especially in role-specific rounds.
- Giving up on timing. People assume silence means rejection after a week. Turing's timelines are longer than that.
What happens after
Turing says reviews take anywhere from 48 hours to six weeks after you finish every step. Its rough guide: one to two weeks for early-career roles, two to three for mid-level, three to four or more for senior or specialised ones.
- Check your status on your dashboard: Pending Review, In Review, Shortlisted, then Selected for Job.
- Turing contacts only the people who move forward. If six weeks pass with no word, it says that usually means you weren't selected.
- It doesn't give individual feedback on rejections.
- Not being picked for one role doesn't remove you. Turing says its matching team keeps looking for other roles that fit your profile.
If you're selected, onboarding covers terms, ID verification, tax and payment details. Once onboarded, Turing says you don't need to redo ID checks when you move between projects.
If you've passed and nothing comes, read passed the interview but no projects.
The catch
Turing is thorough, and thorough is slow. You can do everything right and still hear nothing for six weeks, with no feedback either way. Projects can also end or change with client demand, and Turing says extensions aren't guaranteed. Apply to a second platform while you wait.
More on the company, including the kinds of roles it hires for, is on our Turing page.
Some Apply links are referral links: we get a bonus if you're hired, it costs you nothing and the application is the same.