What the work involves
You're contributing the reasoning behind dispatch, not just the outcome. Day to day that means working through emergency intake scenarios delivered over radio, phone, and chat channels — triaging the request, assigning a priority, selecting a response configuration, and writing down why. Much of the value comes from the annotations: the caller cue you keyed on, the question you asked next, the point at which you'd upgrade or downgrade a response, and the protocol card or determinant code that governs the call.
You'll also review AI-generated dispatch dialogue and decisions. Typical tasks include flagging where a model skips a chief-complaint clarifier, mishandles a caller who is hysterical or third-party, over-dispatches on a low-acuity complaint, or produces a CAD narrative that wouldn't survive QA review. Some engagements ask experts to help define what "correct" looks like — rubric drafting, protocol-adherence checklists, edge-case libraries — and to join knowledge-sharing calls where dispatchers reconcile differences between agencies and protocol systems.
What the screen looks for
micro1's screening is AI-led and conversational, with follow-ups that go deeper when you give a specific answer. Expect to be asked which protocol system you worked under (MPDS, Criteria Based Dispatch, agency-specific), your call volume and console configuration, and how you handled concrete multi-call situations. Vague "I stay calm under pressure" answers stall out; naming determinant codes, pre-arrival instruction sequences, or a specific misroute you caught moves you forward. Written clarity is assessed directly — most of your output is text.
Logistics
- Contractor engagement, fully remote, no live emergency traffic and no shift work.
- Largely asynchronous task batches with occasional scheduled calibration or knowledge-sharing sessions.
- Part-time is normal; many experts commit 10–20 hours weekly around an existing dispatch schedule.
- Observed pay band of $30–55/hr reflects reported rates and varies by project scope and depth of protocol experience — it is not a guarantee.
- Formal dispatcher certification is preferred but not required for this engagement; demonstrable operational experience is what's evaluated.