Getting Matched to AI Training Projects After You Pass

You’ve created your account, built your profile, passed an assessment, and got through the AI interview. The question everyone asks at this point is the same one: what happens now, and what actually decides whether you get the role?

There’s no single formula, and any guide that claims otherwise is guessing. But the platforms themselves, and the recruiters working on them, have said a fair amount on the record about what does and doesn’t matter. Here’s what we know, sourced directly from Mercor’s own guidance and from a micro1 recruiter’s answers in a public Q&A session.

Your profile is the biggest lever you control

Before you’re ever matched, an automated check runs on every application: Mercor calls this Application Fit. It compares your profile against what a role needs and returns one of three outcomes. Most applications are simply allowed through. Some come back with a warning that your profile looks like a weaker match, though you can still apply. A small number are blocked outright. A block only affects that one listing. It doesn’t touch your standing on any other application, and there’s no appeal process to file, because nothing else is affected.

Mercor is direct about what improves your match score, and it’s worth taking literally rather than treating as vague encouragement:

  • Complete your employment history, skills, languages, and even hobbies. All of it gets read.
  • Upload a résumé that reflects your most recent work, not an older version.
  • Add specific tools, certifications and project experience rather than generic descriptions.
  • Write in detail. The system reads the text on your profile for signal, so terse entries give it less to match against.

A micro1 recruiter, answering questions publicly, described essentially the same priority from the hiring side: the biggest factor is how closely your actual experience matches what a specific role needs, and how clearly you can demonstrate that depth. Vetted skills and interview history matter less than most applicants assume. One candidate with 226 certified skills was told, plainly, that skill count alone doesn’t determine selection: fit for the specific opportunity does.

What happens after the interview: Hiring Manager Review

On micro1, once you clear the AI interview (Zara), your application moves to a stage called Hiring Manager Review. This means you’ve met the interview criteria and your application is now being looked at more closely for that particular role.

Two things are worth knowing before you start refreshing your dashboard every hour:

It can legitimately take up to 30 days. A long wait at this stage isn’t a bad sign by itself. Individual applications can stay under review while a project’s staffing needs continue to evolve, even after the initial screening is done. Separately, moving from a completed interview into an "Under Review" status typically updates within about 48 hours, so that earlier step shouldn’t leave you wondering for long.

The AI interview isn’t the sole decision-maker. micro1’s recruiters have access to your full interview transcript and recording, and combine that with human judgement when reviewing your application. You’re not simply being scored by an algorithm and rejected sight unseen.

"Did Not Qualify" and "Not Selected" mean different things

These two statuses look similar but describe opposite situations, and mixing them up leads people to fix the wrong thing.

Did Not Qualify means you didn’t meet the interview criteria for that role. This is the status where there’s something concrete to learn from, and micro1’s Talent Dashboard now has a feature built specifically for it: a "Request Detailed Feedback" button, which gives you a personalised breakdown of where you fell short and what to work on. If you’ve been marked Did Not Qualify, request it. It’s designed to replace guessing with a specific answer.

Not Selected, by contrast, means the opposite of a weak interview: you met the criteria and were considered seriously, but a client chose a different candidate. micro1 staff have confirmed this deliberately doesn’t come with personalised feedback, because there usually isn’t anything to fix on your end. Location, exact project requirements, and how many people the role could take can all decide this outcome without reflecting on your interview at all. Don’t read a Not Selected outcome as evidence that your technique needs work.

If you keep reaching Hiring Manager Review but never get picked

If this is happening to you repeatedly, the advice from micro1’s own recruiting side is specific, and it isn’t "take more interviews." It’s the opposite: be more selective about which roles you apply to, and make sure the experience most relevant to that particular role is genuinely easy to spot, on your CV, your profile, and in the examples you gave during the interview. Reaching this stage repeatedly is itself a positive sign that you’re clearing the bar. What tends to move the needle from there is sharpening the match, not adding volume.

Already working on a project? It doesn’t automatically help or hurt you

If you’re currently active on one project and considering applying to another, don’t assume either way. A micro1 recruiter has confirmed that being active on one project doesn’t automatically improve or damage your chances on a different one; it depends entirely on that specific project’s own requirements. Some projects expect exclusivity or set availability limits; others don’t. If you’re unsure, ask your project lead directly rather than guessing from a forum post, including this one.

Non-traditional backgrounds aren’t a disadvantage

If you’re a career-switcher, a non-native English speaker, or you studied something with no obvious link to tech or AI, the advice from the platforms is consistent: don’t try to hide the gap, and don’t assume it counts against you by default. What matters is whether you can demonstrate the underlying skills a role actually needs: research, reasoning, attention to detail, and the ability to explain your thinking clearly. A strong domain background from an unrelated field is often a genuine asset for specialised roles, particularly ones with a subject-matter angle, rather than something to downplay.

If you’ve got a background like this, our CV and profile tips page covers how to make transferable experience easy for a recruiter to spot.

Applied Clinical Judgement earns a referral fee if you’re placed through the links on this page. That doesn’t affect your pay, your application, or the platform’s decision. We’re an independent referral partner, not Mercor, micro1, Turing or AfterQuery staff.

Frequently asked questions

Not by itself. Selection is driven by fit for a particular role, not by the raw number of interviews or applications. Applying to multiple roles where your experience genuinely matches is sensible; indiscriminate volume is not a substitute for fit.

Not by itself. Recruiters have said directly that selection comes down to fit for a specific role, not the number of interviews or certified skills on your profile. Applying to fewer, closely-matched roles tends to work better than applying broadly.

I’ve been in Hiring Manager Review for weeks. Should I worry?

Not automatically. This stage can take up to 30 days on micro1 while a project’s needs are finalised. A long wait here isn’t the same as a rejection.

What’s the real difference between "Did Not Qualify" and "Not Selected"?

Did Not Qualify means the interview criteria weren’t met, and you can request detailed feedback on what to improve. Not Selected means you met the criteria and interviewed well, but a client chose someone else for reasons unrelated to your performance, and no personalised feedback is available for that outcome.

Can I request feedback if I wasn’t selected, even though I passed the interview?

No. On micro1, detailed feedback is only available for Did Not Qualify results. A Not Selected outcome doesn’t come with one, since there typically isn’t a technique issue to point to.

Will being active on one project stop me getting matched to another?

Not automatically. It depends on that specific project’s requirements. Check with your project lead if you’re unsure before assuming it will count against you.