$50–60/hr · Mercor · Part time, 10 hours a week
A technical interviewer who vets specialized engineers for an AI lab across GPU, ML-compiler, and security domains.
What you would do
- Run structured 20-minute technical interviews with shortlisted expert candidates using provided assessment rubric
- Probe candidates on technical depth, communication clarity, and fit for AI model evaluation work
- Verify work authorization, availability commitments, and exclusivity requirements
- Identify and document red flags, inconsistencies, or concerns during the interview
- Assign candidate tier decisions (advance/hold/pass) and write concise summaries for the hiring team
Who they want
- Prior experience recruiting, interviewing, or technically vetting specialists
- Comfort assessing and asking probing questions to senior-level engineers
- Strong communication skills; ability to run warm, professional conversations while staying on schedule
- Consistent weekday business-hours availability for approximately 10 hours per week
- Fully remote, fully independent; reliable scheduling and follow-through
Main skills
What the interview asks about
1.Technical assessment depth
Surface-level questions miss expertise gaps; your probes must distinguish depth from familiarity.
For example: “You're interviewing a candidate claiming GPU kernel optimization expertise. What sequence of questions would you ask in 5 minutes to assess whether they've actually shipped optimized kernels versus merely read about them?”
2.Structured interview facilitation
Consistent timing and rubric across all candidates prevents bias while generating comparable evaluation data.
For example: “You have 20 minutes with a particularly talkative candidate who's giving long technical answers. How do you stay on schedule, cover all rubric dimensions, and still feel you've fairly assessed them?”
3.Red-flag identification
Spotting warning signs during interviews prevents wasting recruiting resources on unsuitable candidates.
For example: “During an interview, a candidate gives vague answers about past employment, changes their story twice, and admits they've never actually used the primary tooling for the role. At what point do you surface this as a hard pass?”
4.Authorization and exclusivity confirmation
Hiring delays or visa complications sink projects; verifying eligibility upfront is essential.
For example: “You're interviewing an excellent candidate, but when you ask about work authorization, they say 'probably OK but I'd need to check my visa.' How do you handle this without derailing the interview or making a hiring decision on uncertainty?”
5.Written summary quality
Your 3-minute summary is the only record the hiring team sees; it must be evidence-based and actionable.
For example: “You've just passed a candidate 'advance' tier. Write a 4-5 sentence summary that explains their strengths, addresses a borderline weakness, and tells the team what to explore in the next round.”
A task you may get
Conduct a practice technical interview with a peer or colleague on a GPU, ML-compiler, or security topic; record your assessment tier decision and written summary.
How to prepare
- Review the provided assessment rubric and candidate pool to understand domain expertise they're vetting for
- Prepare 2-3 examples of how you've conducted technical interviews or hiring assessments in past roles
- Draft 5-7 technical probes for each domain (GPU, ML compiler, security) that can reveal depth in 4-5 minutes
- Outline how you've handled red flags or tough calls (visa issues, conflicting stories, poor communication) in past interviewing
The facts
- Pay
- $50–60/hr
- Hours
- Part time, 10 hours a week
- Where
- Remote · US Remote
- Open to
- USA
- Field
- Software Engineering
- Posted
- 8/25/2026
- Places left
- 2
We wrote this page from the public Mercor listing. It may be out of date, so read the full posting before you apply.