What the work involves

You write original mathematics problems at or near research difficulty, produce complete solutions with proofs that survive scrutiny, and review other contributors' submissions for correctness, ambiguity, and unintended shortcuts. A typical batch might ask for problems in a named area — real analysis, measure theory, algebraic topology, PDEs, combinatorics, number theory — with a required difficulty ceiling and an explicit rubric for what counts as a valid solution. You will also grade model outputs: reading a model's attempt at a proof, deciding whether it is correct, and pinpointing precisely where the argument breaks rather than simply marking it wrong.

The reviewing half of the job is where most contributors are separated from each other. Catching that a submitted proof quietly assumes measurability, or that a problem has a two-line trick solution that defeats its intended purpose, is the skill being paid for. Written justification matters as much as the verdict — annotations are read by researchers and by other reviewers, and vague feedback gets rejected.

What the platform screens for

micro1 runs an AI-led interview before any human touchpoint. Expect to state your degree, institution, and advisor or thesis area, then defend a specific claim of depth under follow-up questioning — naming a subfield is not enough, you will be asked to work through or explain something in it. Screens commonly include a live proof or error-detection prompt with no reference materials, and probe whether you can articulate why an argument fails rather than just that it does. LaTeX fluency is assumed. Publications, competition history (Putnam, IMO), or teaching at the proof-based level all help but do not substitute for performance in the screen.

Logistics

  • Fully remote, contractor engagement, asynchronous with no fixed shifts
  • Batch-based volume — availability fluctuates with client demand, so treat this as supplemental rather than guaranteed
  • Most contributors commit 10–20 hours per week; some projects request more during ramp-up
  • Pay observed at $80–90/hr, varying by specialization and whether the task is authoring or review; rates are set per project and are not guaranteed
  • Occasional synchronous calibration calls with project leads, usually scheduled around US or European hours