What the work actually involves

You build scenarios drawn from delivery situations you have personally facilitated: a sprint planning session where the product owner keeps adding scope mid-meeting, a retrospective where one voice dominates and the rest of the team goes quiet, a stakeholder who escalates around the team to a director, a chronically overcommitted sprint that keeps carrying stories. Each scenario ships with a reference answer that does not just name the intervention but explains why it is the right move for that team at that moment — and what you would have done instead if the team were newer, more senior, distributed across time zones, or already low on trust.

The grading half is where most of the judgment sits. Models are fluent in Scrum Guide language, so the failure mode is rarely a wrong term — it is advice that is textbook correct and operationally harmful. "Escalate to the manager," "enforce the timebox," "the team should self-organize" can all be technically defensible and still wreck a team's psychological safety. Part of your job is flagging exactly that, in writing, with the reasoning made explicit.

What the screen looks for

  • Real facilitation history, not framework recitation. Expect follow-ups asking what you actually said in the room, and what happened afterward.
  • Comfort with ambiguity. Strong contributors say when a scenario has more than one defensible answer and specify what would tip the decision.
  • Written reasoning. Everything you produce is read asynchronously by a reviewer who cannot ask you a clarifying question, so your prose has to carry the argument alone.
  • Certification is a plus, not a gate. CSM, PSM, or SAFe helps; two years of real delivery facilitation is the actual requirement.

Logistics

Fully remote, fully async, no standing meetings. You set your hours each week with a floor of roughly 10. Pay has been observed in the $70–110/hr range depending on task complexity and review history, paid weekly via Stripe — as reported, not guaranteed. Work is ongoing and batch-based, so volume varies week to week.