What the work actually is

You are handed a workflow brief — set up a protected branch and demonstrate a failed merge recovery, triage a stale issue backlog, open a pull request that resolves a conflict across three commits, configure a review requirement — and you complete it inside a real GitHub account while your screen records. The recording is only half the deliverable. Afterwards you write the realistic prompt a user might have asked to arrive at that task, a rubric that says precisely what a correct model answer must contain and what would make it wrong, and a written walkthrough naming the specific GitHub features and menu paths used. Some shifts are pure authoring; others are review passes over another contributor's task output, checking that the rubric actually discriminates between a good and a bad response.

What the screen is looking for

micro1's screening is AI-led and pushes on specifics. Expect to be asked not whether you know Git but what you type when a rebase goes wrong mid-conflict, how `git revert` on a merge commit differs from `git reset --hard`, or how a required status check interacts with an admin override. The second thing measured is whether you can decompose your own expertise: many strong engineers can do a workflow flawlessly and cannot narrate why they chose that path, and narration is the product here. Prior human-data work — annotation, RLHF, preference ranking, model evaluation — is a preference rather than a gate, but candidates who have written a rubric before tend to clear the screen faster because they already understand that a rubric is a scoring instrument, not a description.

Logistics

  • Fully remote, contractor engagement, invoiced hourly against tasks completed and accepted.
  • Largely asynchronous — you pick up briefs from a queue rather than sitting in meetings, though some projects have a synchronous onboarding call and periodic calibration sessions.
  • You need your own working GitHub account and the ability to create and delete repositories freely; you must be comfortable recording your screen, so a clean desktop and no confidential client work visible during capture.
  • Volume fluctuates with customer demand. Treat it as supplementary contract income unless a project manager tells you otherwise, and expect rate to vary by task complexity within the observed band.