What the work involves

Mercor runs AI-led interviews at volume — thousands of new users each week, applying to roles, sitting interviews, accepting offers, and getting paid. When any of that breaks, it lands in your queue. Day to day you are reading support tickets, trying to reproduce what the user described, and deciding what kind of problem it actually is: a genuine system defect, a model edge case (a transcription failure, a hallucinated interview follow-up, a scoring anomaly), or UX friction where the product works as built but the user couldn't tell. You resolve what you can through configuration, prompt refinement, or a clear explanation, and escalate the rest with enough evidence that an engineer can act without re-doing your work.

The debugging is real, not scripted. Expect browser devtools and network inspection, log and telemetry searches, and SQL against production data to establish what happened to a specific account at a specific time. Beyond individual tickets, you're expected to notice patterns — the same failure appearing across a cohort, a payout issue that spikes after a release — and put them in front of engineering and product leadership. Documentation and runbooks are part of the job, not an afterthought: the goal is that the second occurrence of any issue takes a fraction of the time the first one did.

What the screen looks for

  • Demonstrated web debugging, evidenced by a CS or software engineering degree, startup experience building on React/Node/Next.js/Flask, or 2–5 years supporting applications like these.
  • Hands-on familiarity with LLM behavior — you've built with or poked at models, agents, or prompt chains, and can talk about failure modes rather than describe them from reading.
  • Native-level written English with the specific register this team uses: warm and informal, but precise. Vague reassurance is treated as a defect.
  • Triage judgment — knowing what to escalate, what to fix, and what to explain.

Logistics and pay

Remote from India. This is a six-day-a-week role with substantial overlap with Pacific Time, which in practice means an evening-into-night schedule from IST. Be honest with yourself about that before applying; it is the most common reason candidates who pass the technical screen withdraw. The band shown on this page is reproduced as it appeared on the platform — the hourly framing looks like a listing artifact for what Mercor describes as a full-time salaried position, so treat compensation as a question to settle directly with their recruiting team rather than as an observed rate.