What the work involves
You will be assigned one of two tracks. Authoring means producing original questions in your own subdomain: a precisely stated problem, a difficulty rating (Medium for intro undergraduate, Hard for advanced undergraduate, Expert for post-graduate and beyond), one correct answer, nine distractors that are individually defensible until you reason carefully, a markdown Chain-of-Thought solution, and one to five references from peer-reviewed or university sources. Verification means auditing pre-written items for accuracy, ambiguity, missing premises, and solvability — editing where needed and documenting exactly what you changed and why.
The hard part is rarely the computer science. It is writing a question that is fully self-contained (no implicit assumptions about compiler version, memory model, or scheduling policy), and then generating nine wrong answers that reflect genuine expert failure modes rather than arithmetic noise. Domains in scope include GPU kernel engineering, formal methods and automated reasoning, computer architecture, distributed systems, DevOps and SRE, data engineering and databases, cloud infrastructure, OS and kernel internals, ML engineering, web and API development, embedded systems, graphics and game development, and mobile engineering.
What the platform screens for
Mercor's screen is résumé parsing plus an AI-led interview. Expect it to test:
- Verifiable specifics — named institutions, advisors, papers, systems you shipped, teams you were on.
- Depth under follow-up — a claimed specialty will be probed two or three layers past the textbook answer, often into edge cases and failure modes.
- Evaluation judgment — whether you can distinguish a question that tests reasoning from one that tests recall, and whether you can articulate why an item is ambiguous.
- Calibration — realistic difficulty ratings, and honesty about the boundary of your expertise.
Credentials favored: PhD or doctoral candidate in CS, EE, or an adjacent field; a Master's with unusual depth in one subdomain is also considered. Publications, senior engineering experience at a well-known infrastructure or ML organization, or a competitive programming record all help.
Logistics
Fully remote, fully asynchronous, no fixed hours or meetings. Expected commitment is 10+ hours per week; work arrives in task batches and throughput varies with your domain's demand. Pay is hourly at the observed band above — bands on this platform reflect what candidates have reported for comparable work and are not a guarantee. Written English quality matters as much as technical accuracy, since your solution text is part of the deliverable.
