What the work actually looks like

You are handed a scenario — a wiring diagram, a hydraulic schematic, a PLC ladder segment, a fault code with symptom history — and asked to do in writing what you normally do on a callout. That means stating what the symptom rules in and out, naming the measurement or test you would take next and why, and following the fault pathway to a root cause rather than a parts swap. A second stream of work is evaluation: reading a model's attempt at the same diagnosis and marking where its reasoning went wrong, which is usually not a factual error but a skipped isolation step, a misread interlock, or a recommendation that violates NFPA 70E, NFPA 79, ASME A17.1, or an OSHA lockout requirement. Tasks are scoped individually and your written trace matters more than your conclusion.

What the screen is looking for

micro1 runs an AI-led interview before any task work. It is testing whether your field experience survives follow-up questioning: name the equipment families you have actually serviced, the control platforms you have programmed or troubleshot, the codes you have been held to on a job site. Expect the screener to push on one diagnosis until you reach the level of detail a technician would recognise — component, terminal, expected reading, actual reading. Generalities about "strong troubleshooting skills" do not survive that. It also checks whether you can write: the deliverable is prose, and prose that a reviewer cannot follow has no training value.

Logistics

  • Fully remote and asynchronous; contractor engagement, not employment.
  • No minimum hours, but reviewers who take fewer than roughly 10 hours a week tend to cycle off project queues.
  • Work is delivered through a browser-based task platform — you need a reliable machine and connection, not shop tools.
  • Observed rates for this role run $60–110/hr, typically banded by specialty depth and code fluency. Rates are what the platform has posted, not a guarantee of what you will be offered.
  • No prior AI or annotation experience expected; domain depth is the hiring criterion.