What the work involves

You receive batches of recording tasks through micro1's contributor portal. A batch might ask you to read scripted sentences at a natural pace, respond conversationally to open prompts, record the same utterance at different distances from the mic, or produce speech with specific characteristics — hesitations, overlapping background noise, phone-call conditions, or a particular regional accent. Each task specifies audio format, sample rate, ambient noise ceiling, and how much clipping or room echo is acceptable.

Day to day, the loop is: read the spec, do a test take, check your levels, record, listen back, re-record anything that fails, then submit with the required metadata (device, environment, dialect region). Some batches add a review layer where you rate other contributors' clips for intelligibility, spec compliance, and transcript accuracy. Rejected clips usually fail on preventable things — a fan running, a plosive spike, a misread word — so self-QC is most of the skill.

What the platform screens for

  • Native or near-native US English with a describable regional accent, plus clear articulation under a live mic.
  • A usable recording environment: a consistently quiet room, a decent USB or XLR mic, and headphones for monitoring. Laptop built-in mics rarely pass.
  • Literal script fidelity — reading exactly what is written, including awkward phrasing, without silently correcting it.
  • Basic audio hygiene: setting gain, spotting clipping, recognizing hum, room reverb, and sibilance, and knowing what a WAV at 48 kHz / 16-bit actually is.
  • Reliability across batches. Work arrives in waves; the contributors who stay active are the ones who deliver a full batch on the stated turnaround.

Logistics

Fully remote and asynchronous — you record whenever your space is quiet, which for many contributors means early mornings or late evenings. Batches typically carry deadlines of a few days rather than fixed shifts. Volume fluctuates with client demand, so treat this as flexible supplemental income rather than a steady weekly load. Pay is stated as observed on the platform, varies by task type and locale requirements, and is not guaranteed; some batches pay per approved clip rather than hourly.