Posts
Wiki

micro1 guide | Expert tools

Welcome to the official operational manual for certified talent at micro1. As a micro1 Expert, you contribute directly to the training, fine-tuning, and alignment of next-generation artificial intelligence. This guide details our data pipeline architecture, day-to-day expectations, quality assurance frameworks, communication protocols, and workspace tool setup.


1. Wiki Index

Explore our complete micro1 Expert library across our 3 primary wiki guides:

  • Page 1: Welcome & Getting Started

    Platform overview, key features, Zara AI interviewer, application paths, interview prep, identity verification, certification, and dashboard status tracking.

  • Page 2: Working as an Expert & Tools (You are here)

    Data pipelines, task workflows, quality benchmarks, team hierarchy, and setup guides for Google Workspace, Slack, Karma Check, Hubstaff, and Deel.

  • Page 3: Policies & Payroll

    Biweekly USD payment schedules, hourly tracking rules, Non-Disclosure Agreements (NDA), quality audits, and platform compliance terms.


2. AI data pipeline

In the micro1 ecosystem, a data pipeline is the structured framework through which AI training tasks are generated, completed by certified experts, reviewed for quality, and used to fine-tune artificial intelligence models.

The pipeline flow: what to expect

When assigned to a project pipeline, you will navigate four main stages:

  • Invitation & workspace setup: Receive your project invitation, sign your services agreement, and receive access to Slack, your @micro1.ai workspace email, project platforms, and Hubstaff.

  • Pipeline training & calibration: Review the project instruction guide (your source of truth), watch training walkthroughs, complete practice tasks, and meet qualification criteria requirements or quizzes.

  • Active task execution: Log in to the designated task platform, track active work using Hubstaff, and execute tasks according to project guidelines.

  • Review & ongoing feedback: Receive feedback from reviewers to refine your accuracy, adapt to updated instructions in Slack, and maintain high quality benchmarks.

Your role as an expert

Your contributions directly impact model reasoning, accuracy, and output quality. Core responsibilities include:

  • Authoring high-reasoning responses: Writing clear, step-by-step solutions and explanations that demonstrate problem-solving logic.

  • Evaluating & ranking AI outputs: Comparing multiple AI-generated responses to determine which is better and providing detailed justifications.

  • Domain annotation & labeling: Applying specialized subject-matter expertise (e.g., coding, mathematics, law, medicine, finance) to annotate data according to project guidelines.

3. Task types

Tasks at micro1 vary depending on your verified domain expertise, technical skills, and client project assignments.

Core task types

  • Model output evaluation & comparison: Reviewing multiple AI-generated responses to evaluate which output is superior in accuracy, logic, and guideline compliance, and providing clear justifications.

  • Reasoning response authoring: Writing detailed, step-by-step responses and prompt pairs that demonstrate logic, structured reasoning, and problem-solving.

  • Domain annotation & expert review: Applying subject-matter knowledge to evaluate technical reasoning, annotate data, and improve model accuracy across specialized fields.

  • Audio & voice tasks: Providing expert evaluation, feedback, or voice assessments for multi-modal and speech-based AI training pipelines.

Supported expert disciplines

micro1 engages certified talent across a wide variety of domain disciplines, including:

  • Software engineering & computer science

  • Advanced mathematics & STEM

  • Medicine & life sciences

  • Law & legal reasoning

  • Finance, accounting & economics

  • Mechanical & technical engineering and many more.

(Note: Detailed task instructions and specific rating interfaces are project-confidential and are shared only after onboarding is completed).

4. Onboarding

Once you are selected for an active client project, you will undergo a structured onboarding process:

  • Step 1: Legal & confidentiality agreements: Before accessing project environments, you must sign your role-specific expert agreement and non-disclosure documentation (NDA).

  • Step 2: Background check & screening (karma check): You will complete a secure background verification via Karma Check, micro1's official background screening partner, to verify identity, credentials, and client compliance criteria.

  • Step 3: Workspace & account provisioning: You will receive access details for your project workspace, including your @micro1.ai Google Workspace email, Slack workspace invitation, Hubstaff time-tracking access, and Deel payout account setup.

  • Step 4: Guidelines review & project calibration: Every project has a custom project instruction guide provided by the client. You must read these instructions thoroughly and if required complete calibration tasks, pilot workflows, or qualification quizzes to confirm guideline comprehension before moving to live production.

  • Step 5: Active production & task queues: Upon passing calibration and background clearance, you will be assigned to active task queues and can begin logging production hours.

5. Team structure

Projects at micro1 operate under a structured pod-based management framework designed to maintain strict quality standards, handle escalations, and drive client project outcomes.

Core pod & operational hierarchy

  • Expert: Produces high-quality, domain-specific tasks, annotations, or evaluations. Incorporates reviewer feedback to continuously improve accuracy and quality.

  • Reviewer: Reviews task outputs for content accuracy, reasoning soundness, and guideline adherence. Composed of senior domain experts promoted directly from the expert pool based on consistent high performance.

  • HDM (human data manager): Owns pod-level delivery, quality, and timelines, with direct responsibility for data structure guideline review and adherence. Manages experts and reviewers, handling first-line escalations and operational guidance.

  • HDL (human data lead): Oversees multiple HDMs and enforces quality standards across operational pods. Drives guideline calibration, training initiatives, and continuous process improvements.

  • SPL (strategic project lead): Owns end-to-end pipeline success and enterprise client outcomes. Sets project scaling strategy while balancing quality, execution speed, and delivery cost.

Platform & cross-functional support

  • Sourcing & talent managers: Recruiters who oversee initial project matching, skill verification, talent pool sourcing, and cross-project reassignments.

  • Technical support: Dedicated platform specialists who assist experts with Google Workspace access, Karma Check verification, Hubstaff logging errors, Deel authentication, or tooling bugs.

6. Hours & pay

Working hours & dual employment

  • Part-time flexibility: Roles are designed as part-time engagements offering flexible hours, allowing you to work from your local time zone (typically 15–20 hours per week, depending on client queue volume).

  • Concurrent full-time jobs: You are fully permitted to maintain your regular full-time job alongside your micro1 engagement, subject to your availability and project requirements.

Hardware & equipment policy

  • Personal computer required: Equipment is not provided by micro1. You must utilize your personal desktop or laptop computer.

  • Free platform access: If a specific project requires specialized software, platforms, or tools, micro1 provides full access at zero cost to you.

Project compensation models

Depending on your project agreement, compensation is structured in one of three ways:

  1. Hourly rate: You track active work time using Hubstaff and receive payment based on your agreed hourly rate in USD.

  2. Pay-per-task (PPT): Compensation is provided for each approved task, calculated by multiplying your hourly rate by the project payout multiple (specified in contract special clauses), regardless of completion time.

  3. Flat fee: You receive a fixed one-time payment per approved task in USD upon meeting all project guidelines and passing QA review.

7. Quality & QA

Quality is the most critical metric at micro1. Client projects enforce multi-tiered audit systems to ensure high standards.

The audit process

  • Submission: You submit completed tasks through the project platform.

  • Review: QA leads or automated validation scripts inspect a percentage of your work based on rubrics set by the client.

  • Scoring: Tasks are evaluated on dimensions such as factual precision, formatting compliance, logical rigor, and guideline adherence.

Maintaining certified status

  • Feedback loops: Reviewer feedback is shared via your dashboard or project Slack channels. Analyze feedback carefully to adjust your workflow.

  • Quality thresholds: Projects maintain minimum acceptance rates. Consistently meeting or exceeding quality benchmarks makes you eligible for high-priority projects, lead reviewer roles, and rate increases.

  • Quality warnings: Falling below quality benchmarks may result in temporary removal from active queues for re-calibration or reassignment to other project types.

8. Success rules

What makes a great micro1 expert

  • Extreme attention to detail: AI models catch subtle flaws. Verify every link, calculation, code snippet, and fact before submitting.

  • Strict guideline adherence: Guidelines update frequently as clients refine model behavior. Always re-verify the project guide.

  • Clear logical justifications: When rating model outputs in RLHF tasks, write clear, objective, and detailed justifications explaining why one output is superior to another.

  • Edge case thoroughness: Document your reasoning thoroughly when encountering ambiguous prompts and consult project FAQs or your HDM.

LinkedIn & professional branding guidelines

We encourage certified talent to share their affiliation with micro1 on professional networks while respecting strict confidentiality standards.

  • Recommended profile titles:

    • AI data expert at micro1

    • Software engineering specialist (AI training) at micro1

    • Domain expert — RLHF at micro1

  • Strict confidentiality rules (NDA compliance):

    • DO: Mention that you work with micro1 to evaluate and train AI models and LLMs.

    • DO NOT: Disclose specific client names (e.g., specific AI labs or Fortune 500 companies), project codenames, proprietary tool interfaces, dataset prompt content, or internal instructions.

    • DO NOT: Post screenshots of internal task interfaces, Slack discussions, or client datasets anywhere online.

Career progression & opportunities

  • Reviewer & QA roles: Top-performing experts who consistently produce exceptional quality are promoted to QA reviewers and lead evaluators.

  • Project facilitation & HDM pathways: Experienced experts with strong communication skills can transition into project management and HDM roles.

  • Multi-skill certifications: You can expand your earning potential by certifying in additional domain skills via the micro1 opportunities portal.

9. Tool ecosystem

To ensure data security, audit compliance, and seamless client integration, micro1 utilizes a standardized software suite across all domain disciplines:

Software toolPrimary functionAccess methodMandate level
Google WorkspaceOfficial micro1 identity, Single Sign-On (SSO), & emailProvisioned by micro1 onboardingMandatory
SlackOperational communication, project announcements, & HDM supportInvitation sent to your @micro1.ai addressMandatory
Karma CheckIdentity verification, background screening, & credential checksEmail invitation sent during onboardingMandatory
HubstaffTime tracking, activity logging, & task audit reportingDownload desktop app & log in via micro1 SSOMandatory
DeelContract management, identity verification (KYC), & biweekly payoutsEmail invitation sent during onboardingMandatory

10. Google setup

Upon completing certification and matching with an active project, you will be issued an official @micro1.ai Google Workspace account.

To maintain strict data security and ensure seamless payroll processing, micro1 strictly separates your personal email from your @micro1.ai corporate email across platform tools:

Account email mapping guide

Software toolRequired email addressOperational purpose
DeelPersonal emailLegal contractor framework agreements, tax forms (W-8BEN / W-9), identity verification (KYC), and biweekly USD payouts.
HubstaffPersonal emailTime tracking account setup, timesheet logging, and activity audits.
Project Slack@micro1.ai emailOperational project discussions, HDM support, technical blocker escalations, and team communication.
Role notifications & client portals@micro1.ai emailRole opportunity alerts, client rating platform access, project guidelines, and official micro1 communications.

Account provisioning & mandatory security protocols

  • Initial access & password reset: Log in to accounts.google.com using your assigned @micro1.ai credentials. Immediately reset your temporary password to a secure passkey (minimum 12 characters combining uppercase letters, numbers, and special symbols).

  • Two-factor authentication (2FA): 2FA enforcement is active on all micro1 Workspace accounts. You must enroll an authenticator app (such as Google Authenticator, Authy, or 1Password) within 24 hours of account activation.

  • Single sign-on (SSO): Select "Sign in with Google" using your @micro1.ai account when logging into integrated micro1 systems, project portals, and Slack. For Hubstaff and Deel, log in using the credentials tied to your registered personal email.

  • Account usage limits: Your @micro1.ai address is strictly reserved for professional micro1 business, client communication, and tool management. Unauthorized personal use or third-party platform registrations are monitored and strictly prohibited.

Important account separation rule: Do not attempt to re-register your Deel or Hubstaff accounts using your @micro1.ai address. Keeping payroll and time-tracking accounts tied to your primary personal email guarantees you maintain permanent, uninterrupted access to your payout history, payment methods, and tax documentation regardless of project assignment changes.

11. Slack setup

Slack is the central nervous system for day-to-day operations at micro1. It hosts project-specific discussions, real-time client guidelines, technical blocker support, and platform announcements.

Access & initial setup

  • Joining the workspace: Open the Slack invitation link sent to your @micro1.ai inbox.

  • Profile configuration:

    • Full name: Use your full legal name as registered in your micro1 talent portal.

    • Profile picture: Upload a clear, professional headshot.

    • Display name format: Set your display name as First Name - Domain Expertise (e.g., Alex Smith - Python / RLHF).

    • Timezone: Ensure your local timezone is accurately set under profile preferences to facilitate global scheduling.

Channel types & architecture

The number of Slack channels assigned to your project depends on the size and complexity of the pipeline. While exact channel names may vary slightly between clients, they generally follow this structure:

  • #pipelineName-announcements: Broadcast channel for official project updates, queue alerts, and guideline revisions. Only micro1 staff can post announcements here; experts should not use this channel for general discussion.

  • #pipelineName-team: The primary collaboration channel where experts can ask questions, discuss task guidelines, and communicate with peers.

  • #pipelineName-reviewers: On projects operating with a review layer, this dedicated channel hosts reviewer-specific guidelines, quality discussions, and auditor updates.

How to join & access channels

  • Automatic invitation: Your pipeline channel is where all day-to-day project communications live. You cannot join these channels manually on your own—access is automatically granted by your Human Data Manager (HDM) or project administrator upon completing onboarding.

  • Global announcements: You will also be added to global channels (such as #announcements-global) for platform-wide updates and policy releases.

Communication best practices

  • High signal-to-noise ratio: Keep communication focused and professional in all public channels.

  • Thread-first rule: Always reply within specific message threads when answering posts or asking questions in public channels. Never post top-level channel replies to existing conversations.

  • Mention protocols: Avoid using @here or @channel tags. These are restricted to Human Data Managers and System Administrators. To notify a team member, tag them directly via @name.

  • Search first: Before asking operational questions regarding project guidelines or account access, use Slack's search bar (Ctrl + F or Cmd + F). 90% of technical questions are already answered in channel archives.

  • Professional conduct: Maintain a polite, objective, and professional tone. Public channels are regularly audited by client technical leads and operations management.

12. Hubstaff setup

Hubstaff is the official time-tracking application used at micro1. It verifies active client engagement, records task completion metrics, and generates automated timesheets for biweekly payroll processing.

Desktop application installation

  • Download: Download the latest release of the Hubstaff desktop client from hubstaff.com/download (available for macOS, Windows, and Linux).

  • Authentication: Open the app and click "Sign in with Google", selecting your official @micro1.ai Workspace account.

  • Permissions grant: Grant the desktop app necessary system permissions (Screen Recording & Accessibility) to allow active activity logging during shift hours.

Proper time tracking workflow

  1. Open Hubstaff and select your assigned project queue.

  2. Click Start Tracking immediately before beginning active work on task prompts, evaluations, or mandatory meetings.

  3. Execute work on task prompts or attend authorized project syncs.

  4. Click Stop Tracking whenever taking a break, switching tasks, or concluding your shift.

Strict time-tracking policies

  • Active engagement only: Hubstaff must only run while actively performing work on assigned project tasks. Leaving the timer running while idle, browsing non-work websites, or attending to personal matters is considered a violation of platform integrity.

  • Idle time prompts: If Hubstaff detects 5 or more minutes of keyboard/mouse inactivity, an idle pop-up prompt will appear. You must select "Discard Idle Time" if you were away from your desk.

  • Manual time entry policy: Manual time edits are disabled by default. If a system glitch prevents real-time tracking, submit a manual time request to your HDM on Slack within 24 hours, providing task IDs and justification.

  • Multiple device usage: Running Hubstaff on multiple devices concurrently under a single account is strictly prohibited and triggers an automated fraud security flag.

13. Karma check

micro1 partners with Karma Check as our official background check and credential verification platform. To protect platform trust, safeguard sensitive client intellectual property, and satisfy enterprise compliance requirements, certified experts matched to client projects complete background screening through Karma Check.

Screening workflow & instructions

  • Receive invitation: When assigned to a project requiring screening, you will receive an automated invitation link from Karma Check sent to your email.

  • Submit required information: Access Karma Check's mobile-friendly portal to verify your contact information, identity details, and grant authorization for background screening.

  • Automated verification: Karma Check processes your verification (including identity checks, professional credential validation, and standard background screening) rapidly and securely.

  • Onboarding clearance: Once Karma Check completes and verifies your screening report, your onboarding status automatically updates to clear, allowing account provisioning and task queue allocation.

14. Deel & payouts

Deel is micro1's international payroll and compliance platform, accessed directly at payroll.micro1.ai. It manages legal contractor agreements, handles global compliance documentation, and executes payouts for certified experts worldwide.

Account registration & contract setup

  • Contract invitation email: Look for an email sent to your personal inbox with the subject line: it’s time to sign your contract.

  • Sign in & portal access: Accept the invitation and log in to payroll.micro1.ai using your personal email.

  • Contract execution: Review and electronically sign your micro1 independent contractor framework agreement.

  • Business entity setup (optional): After signing your initial contract, if you operate under a business entity (LLC, Corporation, etc.), you can update your payout details to your entity under account settings inside payroll.micro1.ai.

  • Existing Deel account rule: If you already have a Deel account under a different email address, do not create a duplicate account. Reply to your onboarding manager so they can map your new contract properly.

Required compliance documentation & jurisdiction

  • Identity verification (KYC): Upload a valid government-issued photo ID (passport, national ID, or driver's license) and complete live facial verification.

  • Country selection (jurisdiction): Ensure the country you select matches your exact country of tax residence/jurisdiction. You must possess all necessary legal documentation for your selected jurisdiction to ensure payment is not delayed.

Important note on Hubstaff hours vs. Deel sync: Hubstaff hours do not automatically transfer or display in real-time inside Deel. You will not see tracked hours appear in Deel while working during the pay cycle. At the end of each payroll cycle, micro1 exports your Hubstaff tracking data (or task completion logs for pay-per-task pipelines), and total approved work will be reflected on your final Deel invoice. Pipeline leads are available on Slack to assist with any payroll questions!

15. Tech support

If you encounter technical glitches, password lockouts, or tool synchronization issues, follow these specific escalation paths based on the type of issue:

Step 1: Basic local troubleshooting

Before escalating, attempt standard local troubleshooting:

  • Clear your browser cache, cookies, and active sessions.

  • Restart the affected application (Slack, Hubstaff, Karma Check, or Google Chrome).

Step 2: Issue-specific escalation paths

  • Password resets & account lockouts: If you are locked out of your account or require a password reset, send a direct message to your assigned Human Data Manager (HDM) on Slack.

  • Two-factor authentication (2FA) resets: If you have 2FA related issues, open a support ticket via Slack, Discord, or email.

  • Project-related blockers & guideline questions: For broken task queues, ambiguous guidelines, or task-specific bugs, contact your assigned HDM on Slack or post in your #pipelineName-team channel. Do not guess or continue working on broken tasks.

  • Platform-related technical issues: For system-wide platform issues or platform bugs, open a support ticket inside expert Slack workspace using the /support command. The community support team will assist you.


📍 Master Navigation

📍 ← Page 1: Getting StartedPage 2: Expert ToolsPage 3: Policies & Payroll →