What the work involves

You build the reference material that teaches a model what senior PM writing actually looks like. A typical task starts with a scenario you invent — a mid-quarter scope cut, a launch readiness review, a strategy memo arguing against a loud internal favorite — and ends with a deliverable polished enough to survive an executive review. From there you write the rubric: what separates a leadership-ready artifact from a competent early draft, and where the line sits on prioritization logic, tradeoff articulation, technical accuracy, and stakeholder framing.

The other half is evaluation. You read model outputs and annotate failure modes precisely — objectives that sound decisive but commit to nothing, roadmaps with no sequencing rationale, exec updates that bury the ask, PRDs that skip the non-goals. Vague criticism is not usable output here; the value is in naming the defect and pointing to the specific sentence or section that causes it.

What the screen looks for

  • Verifiable ownership of real PM artifacts at scale — which company, which product surface, which documents you personally wrote versus reviewed.
  • Fluency with frameworks (JTBD, opportunity solution trees, RICE or similar) as working tools rather than vocabulary.
  • Writing that shifts register cleanly between engineering audiences and a VP with four minutes.
  • Calibration: whether your quality judgments hold up under follow-up questioning and stay consistent across similar cases.

Logistics

  • Remote, US-based, contractor engagement through micro1.
  • Asynchronous and task-based; most contributors work in self-scheduled blocks rather than fixed hours.
  • Volume varies with customer demand — treat it as a meaningful side engagement, not a guaranteed weekly load.
  • Pay band of $100–200/hr reflects rates observed on the platform for this role, not a guarantee; final rate depends on screening outcome and task type.