What the work involves

You start from a chart, not a blank page. Most contributors pull information-rich visualizations from their own field — survival curves with confidence bands, multi-axis financial time series, stress-strain plots, remote-sensing time series, SPC charts — and then write questions that cannot be answered by glancing at the graphic. The target is multi-step quantitative reasoning: read two series at a specified x-value, adjust for a log scale or a unit mismatch, compute a rate of change or a ratio, compare against an annotated threshold. Each task ships with a single defensible answer and a written derivation that names the axes, units, legend entries, time window, and any statistical features you relied on.

  • Select or construct charts that reward careful reading rather than pattern-matching
  • Write prompts that are unambiguous, self-contained, and objectively scorable
  • Provide the answer plus a step-by-step calculation trace a reviewer can check line by line
  • Revise against reviewer feedback on ambiguity, hidden assumptions, or unsupported inference
  • Occasionally review peer tasks for correctness and terminology precision

What the screen looks for

micro1's process is AI-led: a conversational interview that probes your stated background, then presses on specifics. Expect follow-ups that test whether you actually work with the chart types you claim — what a confidence interval on a forecast fan chart does and does not permit you to conclude, why a secondary axis invites misreading, how you'd phrase a question so a log scale can't be misread as linear. The other half of the assessment is authoring judgment: can you tell a genuinely hard question from a merely fiddly one, and can you spot when your own "correct answer" depends on an assumption you never stated. Written English clarity is scored directly, since your explanations become training signal.

Logistics

Remote, contractor, invoiced hourly at an observed $25–50/hr depending on domain scarcity and credential depth — bands are what contributors have reported, not a guarantee. Work is asynchronous with periodic coordinator check-ins; most people commit 10–20 hours weekly, though some projects request more during ramp-up. Volume is project-dependent and can pause between client phases, so treat this as supplemental rather than a full replacement for existing work.