What the work involves

You will be given prompts and scenarios drawn from real technology-management situations: standing up a limited-scope initiative, chasing a vendor who has missed an SLA, resequencing a plan after a resource cut, or writing an executive update that has to land with both engineers and a CFO. Depending on the task queue, you may author the reference response yourself, critique a model's attempt against your own professional standards, or rank several candidate outputs and explain in writing why one is stronger. The written justification usually matters more than the score — reviewers want to see the reasoning a competent manager would apply.

Typical deliverables include project plans with defensible timelines and resource assumptions, vendor oversight artifacts (SLA definitions, performance summaries, escalation paths), risk registers with realistic mitigations, and stakeholder-facing status reports at multiple levels of abstraction. Expect a fair amount of red-teaming as well: identifying where a model produces plausible-sounding but operationally useless output — invented SLA metrics, timelines that ignore procurement lead times, conflict-resolution advice that no experienced manager would give.

What the platform screens for

  • Verifiable ownership. micro1's screen leans on specifics: which initiatives you ran, over what timeframe, with what vendors, and what you personally decided versus inherited.
  • Depth under follow-up. Expect the AI interviewer to push on a detail you mention — a negotiation, a missed milestone, a de-scoping decision — and to keep pushing.
  • Evaluation judgment. Can you say clearly why one plan or report is better than another, in terms a non-expert reviewer can audit?
  • Writing quality. Much of the output is prose. Vague or padded writing is a common disqualifier.

No AI or ML background is required. Domain fluency plus disciplined writing is the bar.

Logistics

Fully remote and asynchronous. Work is drawn from a task queue with per-batch deadlines rather than fixed shifts, so hours are flexible; contributors commonly commit 10–20 hours per week, and volume fluctuates with client demand. Pay is hourly within the observed $70–130 band — rates are set per project and per contributor and are not guaranteed. Engagements are contractor arrangements, sometimes renewed across multiple task cycles.