The micro1 AI interview: what it's actually like, and how to prepare

October 30, 2026 · Vouched

Most people meet micro1 the same way: they apply for a role, and instead of a recruiter, they get a link to an interview with an AI. No human calls first. For a lot of qualified people, that interview is the whole ballgame. So here is what it's actually like, gathered from micro1's own guidance and from candidates who have sat it and compared notes in places like r/micro1_ai.

What the interview is

The interviewer is called Zara. She is not a set of pre-recorded questions you talk into a void. She is a live, conversational AI who appears as a video avatar, speaks to you, listens to your answers, and asks follow-up questions based on what you just said. Her questions also appear as text on screen while she speaks.

Sessions run about 20 to 40 minutes, roughly seven minutes per skill being tested. The direction of the conversation adapts: answer a question cleanly and the follow-ups go deeper; stumble on the basics and she steps back to check whether the foundation is there. Technical roles can add an exercise afterwards (a coding task for engineers, a data exercise for annotation roles), which candidates report runs with screen sharing.

The session is recorded, and your answers are scored from the transcript. A human recruiter reviews the report before anything moves. You get your result straight away, and if you don't pass, you can request written feedback from your dashboard.

The rule that shapes everything: there is no retake

Read this part twice. For a given role, the real interview happens once. An interview you have submitted, or one that ran out of time, cannot be reset and taken again. (If you simply never sit it inside the window, candidates report micro1 grants a further 48 hours while the role stays open. Missing the appointment is recoverable. A bad sitting is not.)

That is why the mock matters. Every role offers a free practice interview, in the same interface, that does not count. Candidates on Reddit keep saying the same thing about it, in almost the same words: do the mock first. It is the only rehearsal you get, and it costs you nothing but about twenty minutes.

If you don't pass, the honest path is the one micro1 itself lays out: request the feedback, read it properly, and apply to a neighbouring role that needs the same skill. Skills you have already passed are carried over, so a later interview can be considerably shorter.

What candidates keep reporting

A few patterns come up again and again in the community threads:

• Freezes are the most common technical problem. Zara stalling, failing to respond, or sitting in a "reconnecting" state while the timer runs is the single most-reported frustration. Sit the interview on the most stable connection you have, on a desktop, not a phone.
• She can fixate on a keyword and push into detail you weren't expecting. Candidates who did well describe staying calm, answering the question that was actually asked, and asking her to repeat or clarify when needed. That is allowed.
• Her encouragement is not a grade. Zara sounds encouraging by default. A warm response mid-interview tells you nothing about your score; the result at the end is the result.
• The wait afterwards is the real test of patience. Passing puts you in a certified pool. It is not a job offer. Candidates describe sitting in "Hiring Manager Reviewing" for up to a month, and plenty end at "Not Selected" despite passing. Budget for the wait, and keep the rest of your search alive while you're in it.

How to prepare

None of this is about gaming the interview. It is about not wasting your one sitting.

• Only claim skills you can defend in depth. The questions are built from your introduction and the skills you selected. A padded skills list doesn't make you look broader. It gives Zara twenty extra minutes of follow-ups you can't support. One role you can go deep on beats five you can skim.
• Prepare three real examples. A situation from your actual work, what you decided, what happened, and a number where you have one. Every follow-up will draw on these, and concrete specifics score better than fluent generalities.
• Write a two-sentence introduction: your field, your years, the work you've held, one specialism. Say it out loud until it lands in under thirty seconds. The opening minutes steer the rest of the interview.
• Think out loud, and don't go silent. You are scored on how clearly you explain your reasoning, not on AI jargon. Long silences can be read as the end of your answer, so narrate: "Let me break that down" buys you thinking time. Short pauses are fine. There's a normal beat while she processes.
• Say so when you don't know. A plain "I haven't done that, but here's how I'd approach it" holds up better under follow-ups than a bluff. She will follow up.
• Set up like it's proctored. The session is recorded and a human reviews the report afterwards. Candidates report that monitoring runs throughout, and that tab-switching or screen overlays can count against you even when you weren't doing anything wrong. So sit it in a quiet room, webcam and microphone tested, one screen, other tabs closed, AI assistants and overlay tools (grammar checkers included) turned off.
• Do the mock. Same interface, doesn't count, and it's where you find out your microphone is bad, not in the real sitting.

Passing gets you certified and into the matching pool, where micro1 pairs certified experts with client projects as they open. That can take time, and nobody honest will promise you a placement date. But the interview itself rewards preparation, and preparation is the one part of this process entirely in your hands.

One take. Make it a true one.

Vouched

Browse the checked roles: every micro1 role on our board carries its referral link and the date we checked it: vouchedhq.ca/roles