What the work involves
You write electrical scenarios the way a service call actually unfolds: a homeowner reports flickering lights on one circuit, a panel has a double-tapped neutral, a three-phase motor trips on start. For each one you document the diagnosis path — what you'd measure first, what reading rules out what, and where the NEC article lands on the repair. Then you grade model answers against your reference: does the model chase the symptom in a sensible order, does it call for the right conductor size and OCPD, does it recognise when the job needs a permit and an inspection.
The hardest and most valued part is catching answers that read fluent and competent but are wrong in ways that matter — bonding a neutral downstream of the service disconnect, sizing off the wrong ampacity table, treating a GFCI requirement as optional, telling someone to work a panel hot. You write up why it's wrong, citing the code section or the field reality behind it.
What the platform screens for
- A verifiable licence. Journeyman or master, in a named US state or jurisdiction, with the licence number available.
- Code fluency under follow-up. Screeners ask you to reason through a specific installation and will push on why. Naming an article helps; explaining what the article is protecting against helps more.
- Field specificity. Scenarios drawn from calls you actually ran read differently from textbook problems, and screeners can tell.
- Written clarity. You'll be asked to explain diagnostic reasoning in prose. Steps in order, plain English, no shorthand only another electrician would parse.
Logistics
Fully remote, fully async — no calls, no fixed shifts. Most contributors work in blocks around their day job; the floor is 10 hours a week and volume scales up or down week to week. Pay is weekly via Stripe, with the rate inside the $50–90 band set from licence level and depth of experience. Commercial and industrial background, estimating, inspection, or apprentice-training experience all push toward the top of the band.