What the work actually looks like

You work inside real Salesforce orgs, executing tasks the way a working admin or ops person would: converting leads, correcting account hierarchies, building a pipeline dashboard, wiring a record-triggered Flow that stamps a field or creates a follow-up task. The deliverable is rarely just the finished org state — it's the trace. You write down every click, object, field, and condition, including the moments where you backtracked because the first path didn't work. A second stream of work is review: reading someone else's workflow transcript and judging whether the steps are accurate, whether the automation would actually fire, and whether a plausible-looking answer is quietly wrong.

  • Task execution across standard objects: leads, contacts, accounts, opportunities, cases
  • Reports and dashboards, including report types, filters, groupings, and cross-object logic
  • Flow building — record-triggered, screen, scheduled — plus validation rules and basic declarative automation
  • Data hygiene work: duplicates, import mappings, field-level correctness
  • Written critique of other contributors' workflows against what Salesforce actually does

What the screen looks for

micro1's process is AI-led and conversational, and it pushes on specificity. Saying you "used Salesforce daily" gets followed by a question about which edition, which objects you owned, and what broke. Expect probes on the difference between a workflow you configured yourself and one you merely operated inside. No AI or ML background is expected or asked about — the platform is buying Salesforce judgment, plus the ability to explain it in clean written English. Communication is screened seriously here because the written artifact is the product.

Logistics

Contractor engagement, fully remote, and largely asynchronous — tasks are pulled from a queue rather than scheduled into meetings. Contributors commonly report 10–25 hours a week with flexibility on when those hours fall, though throughput and review quality scores tend to govern how much work stays available. Certifications (Administrator, Platform App Builder) help at the rate conversation but are explicitly not required; demonstrated hands-on depth carries more weight. You'll need a reliable machine, stable connection, and the discipline to document while you work rather than reconstructing steps afterward.