What the work involves
You'll spend most of your time inside Airtable doing the kind of build you'd do for a real team: setting up a base for a product roadmap, an ops intake queue, or a content calendar; linking tables and configuring lookups and rollups; adding views, forms, and interfaces; wiring automations that move records between states or push notifications out. The difference from client work is that every step gets recorded and written up. Tasks typically ask you to complete a workflow, then document the exact sequence — which field type, which view filter, which trigger and action — precisely enough that someone else could reproduce it without guessing.
A second stream of work is review. You'll be handed workflows or instructions produced by a model or another contributor and asked whether they reflect how Airtable actually behaves: does that automation trigger fire on that condition, is a linked record the right choice over a single select, would a practitioner really structure the base that way. Honest "this is technically possible but nobody does it" judgments are more valuable here than polite approval.
What the screen looks for
micro1 runs an AI-led interview. It probes for hands-on specificity: the names of field types and trigger conditions, how you handle many-to-many relationships, where Airtable's limits bite (record caps, automation run limits, interface permissions). It also tests whether you can narrate a build as a sequence of discrete, verifiable steps rather than a summary. No AI or machine learning background is expected — the domain knowledge is the qualification.
Logistics
- Remote, contractor engagement, asynchronous task queues rather than fixed shifts.
- Volume varies with customer demand; contributors commonly report part-time loads of 10–20 hours a week.
- Observed pay band is $30–100/hr, set by demonstrated depth rather than title; nothing is guaranteed.
- You need your own Airtable access — a free or paid workspace where you can build freely.