What the work involves
You receive batches of datasets and documents that have already been through a de-identification or transformation pipeline, and your job is to test whether the pipeline actually worked. That means sampling records, reading closely, and identifying PII that survived the process — a name left in a signature block, a date of birth reconstructable from surrounding fields, an account number partially masked, a free-text comment field that names a third party. Findings go into provided templates: what you found, where, why it qualifies as sensitive under the applicable standard, and how severe the exposure is. The value you add is qualitative judgment on the edge cases, not volume throughput.
What the platform screens for
micro1's screening is AI-led and conversational, and it pushes on specificity. Expect to be asked what regulatory frameworks you have actually worked under (GDPR, CCPA/CPRA, HIPAA, state breach-notification statutes), what review platforms you have used (Relativity, Everlaw, Reveal, Nuix), and how you have handled disagreement about whether a data element is identifying. Vague claims of "privacy experience" get probed hard. The screen also tests calibration: can you distinguish direct identifiers from quasi-identifiers, explain re-identification risk in combination, and resist both over-flagging harmless text and waving through borderline items to keep pace.
Logistics
- Remote, contractor engagement; asynchronous review work with batch-based assignment rather than fixed shifts.
- Observed rates for this listing fall in the $31–60/hr range, typically set by depth of privacy and eDiscovery background — not guaranteed, and often tied to project phase and volume.
- Volume on client-driven privacy projects is uneven: heavy weeks followed by quiet ones. Candidates who can commit meaningful hours during active batches tend to stay engaged.
- Expect confidentiality terms and, in some cases, restrictions on the device or network you review from.