What the work actually is

Thousands of people join Mercor each week to interview for client-posted roles. When something breaks — an interview won't load, an offer won't accept, a payment doesn't land, a profile won't verify — they write in, and you are the person who answers. Day to day that means working a support queue in a tool like Zendesk or Intercom, reproducing reported issues yourself before escalating, writing tickets engineering can act on without a follow-up thread, and closing the loop with the user. A meaningful share of contacts are first impressions of the company, so tone matters: informal and warm, but precise, and written in near-native English.

The operations half is what separates this from a pure ticket-closing job. You are expected to notice that forty tickets this week share one root cause, document it, and take it to product and engineering with a proposal — a help-centre article, a copy change, a validation fix — rather than answering it forty more times next week. Building and maintaining talent-facing documentation is an explicit responsibility, as is monitoring whether the workflows you put in place actually reduced volume.

What the screen looks for

Mercor screens with an AI-led interview. Expect verifiable specifics: which support platform you used and what you did inside it, ticket volumes you personally handled, a bug you reproduced and how, a recurring issue you got fixed at the source. Follow-ups probe depth — if you say you "worked with engineering," you will be asked what was in the ticket. Written English is assessed directly, and so is judgment about when to escalate versus when to resolve, and when a manual fix is acceptable versus when it is a symptom of something that needs a product change.

Logistics and pay

  • This is full-time employment with Mercor India, not contract or per-task work — unlike most listings on this board.
  • Support coverage means real working hours against a live queue; expect shift structure and some overlap with US-based engineering and product teams.
  • Familiarity with SaaS and marketplace products is assumed; you should be comfortable in browser dev tools, console errors, and reproducing issues across devices.
  • The pay figure shown on the source listing is a platform data artifact, not an hourly rate. Treat compensation as a salaried India-based package to be confirmed directly with the recruiter — nothing here is a guarantee.