What the work actually is

This is not slide-polishing for a marketing team. You are given technical presentation material — system architecture walkthroughs, post-incident reviews, platform migration proposals, engineering roadmaps — and asked to reconstruct it so a technically literate executive audience can follow the argument. That means deciding what belongs on a slide versus in an appendix, choosing whether a service dependency is better shown as a sequence diagram or a layered block diagram, and rewriting text that is technically accurate but analytically incoherent. Some tasks are creation from a brief; others are evaluation, where you compare model-generated decks against a reference and write out why one is stronger. Your written reasoning is often the deliverable that matters most — the model learns from the justification, not just the corrected artifact.

What the platform screens for

micro1's screening is AI-led and follow-up heavy. It probes whether your software engineering background is real and recent enough that you can spot a wrong architecture diagram, not merely an ugly one. Expect to be asked about specific systems you've built or presented, then pushed on details — throughput numbers, failure modes, why you chose one datastore over another. The second thing screened is presentation judgment under constraint: what you cut, and why. Candidates who can articulate a principle ("one claim per slide, evidence directly beneath it") and then apply it to a hypothetical outperform candidates who describe general design taste. PowerPoint fluency is explicitly named in the listing and is checked concretely — masters, layouts, native charts, diagramming at speed.

Logistics

  • Contractor engagement, fully asynchronous, no standing meetings expected.
  • Location-gated to the US, UK, or Canada.
  • Hours are flexible and task-based; most contributors take a defined batch and commit to a turnaround window rather than fixed shifts.
  • Volume fluctuates with the customer project — treat this as supplementary work rather than a full-time replacement unless the platform tells you otherwise.
  • Pay of $150–350/hr reflects observed rates on this listing; placement within the band tracks seniority and how specialized your architecture domain is. It is not guaranteed.

No prior AI or annotation experience is required. What is required is that you have genuinely done the engineering, and have genuinely had to explain it to people who control budgets.