The work
You will spend your time doing what you already do in a data room, but with the reasoning made explicit. Tasks typically involve reading a contract or excerpt, flagging the provisions that would matter to a buyer or seller — change-of-control, anti-assignment, termination for convenience, exclusivity, MFN, indemnification caps and baskets, auto-renewal and notice mechanics — and then writing a short, defensible rationale for why each issue is material or merely boilerplate. Other tasks ask you to grade or correct an AI-generated diligence summary: was the consent trigger caught, was the severity rating right, did the model confuse a permitted-assignment carve-out with a hard consent requirement?
Severity calibration is the core skill. The customer cares less about whether you can spot a clause than whether you can say, in two or three sentences, how it changes deal economics or closing mechanics in a specific transaction posture — stock purchase versus asset deal, a target with 400 customer contracts, a lease with a landlord consent right on the critical path. Commercial leases and SaaS agreements come up regularly.
What the screen measures
micro1 runs an AI-led interview before human review. Expect it to probe verifiable specifics: where you practiced, deal sizes, how many diligence matters you staffed or managed, what your data-room workflow looked like. Follow-up questions get more granular than the first question suggests, so vague answers about "reviewing contracts" tend to end the conversation. The screen also tests evaluation judgment — you may be given a clause and asked to rank its severity, or shown a flawed summary and asked what is wrong with it. JD and active bar membership (or jurisdictional equivalent) are checked.
Logistics
- Fully remote, contractor engagement, asynchronous task queues
- Flexible hours; most contributors commit 10–20 hrs/week, some more when project volume allows
- Observed pay band $90–100/hr, not guaranteed — rates vary by project and assessed depth
- No AI or machine-learning background required; onboarding covers the annotation conventions