What the work actually is

You will spend most of your time doing one of three things. First, authoring realistic backend tasks — an ASP.NET Core endpoint with a broken model-binding contract, an EF Core query that silently N+1s, a service with a deadlock lurking in `.Result` — together with a reference solution and tests that fail before and pass after. Second, reviewing model-generated C# side by side and deciding which output a competent .NET reviewer would merge, with written reasoning that survives a second reader. Third, error-hunting: reading code that compiles, runs, and looks fine, and locating the place where an `async void`, a mis-scoped `IServiceProvider`, or a swallowed `TaskCanceledException` will bite in production.

The grading is where people underestimate the job. Models produce C# that is syntactically clean and structurally wrong — a repository injected as a singleton over a scoped DbContext, `ConfigureAwait` cargo-culted into an ASP.NET Core app, LINQ that quietly materialises before filtering. You are being paid for the judgment that separates "unfamiliar style" from "defect," and for writing that distinction down clearly.

What the screen looks for

micro1's screening is AI-led and follows up on whatever you say. It probes for hands-on production .NET rather than surface familiarity: specific framework versions you have shipped on, how you actually diagnosed a real concurrency or memory issue, what you would reject in a pull request and why. Vague seniority claims get drilled into immediately. The second thing it tests is whether you can hold a consistent standard — given two flawed solutions, can you rank them and explain the ranking without falling back on taste.

Logistics

  • Fully remote, asynchronous, task-queue based; no standups
  • Typical commitment 10–20 hrs/week, with some projects offering up to full-time
  • Hourly, invoiced against reviewed work; volume fluctuates by project phase
  • Written English at a level where your review comments are usable without editing
  • Own machine with a working .NET SDK and a Git workflow you are fluent in