Coding roles in AI training ask engineers to write and review code, build test cases and evaluation environments, and judge model-written code. Several micro1 postings in this group list screening questions, an AI interview (lengths given range from about 10 to 30 minutes), a technical assessment on some roles and a hiring manager review, and some ask candidates to complete these stages without outside assistance. Practise explaining your reasoning out loud.

Practice questions

These are practice questions written for this site to help you prepare. No platform has said it asks these exact questions.

  1. Review this function a model wrote. What is wrong, and how would you fix it?

    A good answer covers: Correctness first (edge cases, off-by-one, null inputs), then complexity, readability and security. Give the fixed code and a test that fails before the fix.

  2. Write test cases that would catch a wrong solution to this problem.

    A good answer covers: Normal, edge and adversarial cases, including empty input, large input and tricky boundaries, each with the expected output.

  3. How would you design a task that is hard for a coding model but has a checkable answer?

    A good answer covers: A realistic task with hidden tests, clear requirements, and a difficulty that comes from reasoning, not from vague wording.

  4. Explain the time and space complexity of your solution.

    A good answer covers: Correct big-O for both, with the reason, and a note on a faster or lighter alternative if one exists.

  5. Two model answers solve the task. How do you rank them?

    A good answer covers: Correctness and tests passing, then readability, idiomatic use of the language, performance and safety.

  6. Describe a bug you fixed that took longer than expected.

    A good answer covers: The symptom, how you narrowed it down, the root cause and what you changed to prevent it again.

  7. How do you review a pull request in an unfamiliar codebase?

    A good answer covers: Read the purpose, run the tests, check interfaces and edge cases, ask questions rather than assume.

  8. What makes a code explanation helpful for a learner?

    A good answer covers: States the idea first, walks through one example, avoids unexplained jargon, and points out the common mistake.

  9. Which languages and frameworks can you review at expert level?

    A good answer covers: An honest list, separating expert from familiar.

  10. Why should you not use an AI assistant during the screening?

    A good answer covers: Some postings explicitly ask for no outside assistance because the stages measure how you think; using one breaks the rules and the purpose.

What the platforms say about the assessment

In the 9 October 2026 data, roles in this group came from Meridial, SME Careers, micro1, Terac and xAI. Each platform runs its own process, and steps can differ by role. Below is what each platform's public pages or postings say, followed by lines quoted from current postings in this group.

Meridial

  • Meridial postings describe the work and requirements but do not describe the screening steps.
  • Postings say contractors supply their own secure computer and internet connection, and recording roles add a high-quality microphone and recording setup. Company benefits such as health insurance do not apply.
  • We could not confirm Meridial's selection steps from a public page; treat the posting itself as the guide.

Source: boards-api.greenhouse.io

SME Careers

  • Many SME Careers postings state: 'Selection process involves an AI interview, a domain-specific task, and an interview with a recruiter.'
  • Many postings also say there is no immediate project for the role, and that qualified applicants will be contacted first when relevant opportunities arise.

Sources: sme.careers, api.sme.careers

micro1

  • micro1's experts page describes four steps: apply for opportunities, take the AI interview, get onboarded, start earning.
  • Postings commonly list screening questions, then an AI interview, then in some roles a technical assessment, then a review by the hiring manager. Interview lengths stated in postings range from about 10 to 30 minutes.
  • Some postings ask you to complete the interview and assessment without outside assistance.
  • micro1's FAQ says certification does not guarantee immediate placement on a project.

Source: www.micro1.ai

Terac

  • Terac's expert docs describe signing in with LinkedIn, verifying your phone, connecting LinkedIn or adding a resume, and a short voice conversation of about 10 minutes that the docs say you can skip and take later.
  • Each opportunity then has its own steps, usually screening questions followed by the tasks themselves. Research postings describe remote video or voice interviews of 30 to 90 minutes.

Source: terac.com

xAI

  • xAI postings say role-specific details are given during the interview process. They do not describe the steps publicly.
  • Basic qualifications in postings include native proficiency for language roles and a portfolio for video and creative roles.

Source: boards-api.greenhouse.io

Quoted from current postings

"A note on the process: our interview and assessment stages are designed to see how you think, so we ask that you complete them without outside assistance."

Software Engineer - Backend, micro1

"You will participate in a remote technical interview to discuss your recent development projects."

Full-Stack Engineers: Interview on Cybersecurity and CI/CD Pipelines, terac

"Specific details and role specific information will be provided to you during the interview process."

AI Tutor - Software Engineering, xai

"Selection process involves an AI interview, a domain-specific task, and an interview with a recruiter."

SQL Team Lead, sme

"Apply to the role, filling out the screening questions"

Software Engineer - Backend, micro1

"The conversation flows as a standard technical interview, focusing on your day-to-day security routines."

Full-Stack Engineers (Cybersecurity): Feedback On CI/CD Workflows, terac

Steps were read from public pages and postings, not tested first-hand. Passing a screening does not guarantee a project, hours or pay.

Terms to know

Stump the model

A task where you write a hard question the model gets wrong and record the correct answer, often used in expert STEM and coding projects.

Process supervision

Judging each step of a model's reasoning rather than only the final answer, common in maths, science and coding work.

Golden response

A model answer written or rewritten by an expert to be the best possible reply to a prompt.

Rubric

A written list of criteria and scores used to judge a response, for example accuracy, instruction following and tone, each with clear pass or fail descriptions.

AI interview

A screening interview run by an AI system instead of a person, usually spoken or on video, with questions about your background and skills.

Sources