What the work actually involves

You'll be handed workflow briefs that describe something a producer would plausibly do in FL Studio — sidechain a pad to a kick without Fruity Limiter, bounce a Patcher chain to audio and reroute it in the Mixer, fix a mistimed vocal with Newtone, set up a send with Fruity Reeverb 2 on a return track, clean up a session that's grown to forty unlabeled channels. You complete the task in a real FL Studio session while screen recording, then write up what you did: which tool, which menu path, which right-click option, why that route and not another. From there you produce a prompt that would elicit the same work from an AI, and a rubric that says precisely what a correct answer must contain and what counts as a near-miss. A portion of the work is the reverse: reading someone else's output or another contributor's submission and scoring it against the rubric.

The documentation is the deliverable, not the music. A workflow that sounds great but is written up as "added reverb and it sat better" is unusable. A rubric that says "good mix" is unusable. What the customer needs is granularity — Channel Rack versus Playlist versus Mixer routing, the difference between a pattern clip and an audio clip, what happens to automation when you consolidate, where FL's behaviour diverges from Ableton or Logic conventions that a model might have absorbed elsewhere.

What the screen looks for

micro1 runs an AI-led interview before any human sees your file. Expect it to push past "I've used FL Studio for years" into specifics: version and edition, signal flow questions, how you'd handle a named routing or automation problem, what you do when a stock plugin behaves unexpectedly. The screen is also checking that you can articulate process out loud in real time, since that's essentially the job. Vague or hedged answers on concrete mechanics are the main failure mode — the questions are designed so that someone who has only watched tutorials runs out of detail by the second follow-up.

Logistics

  • Fully remote, contractor engagement, asynchronous — tasks are claimed and delivered on your own schedule against deadlines.
  • Observed rates run $30–100/hr, varying with depth of FL Studio expertise, task type, and whether you're producing workflows or reviewing others'. Rates are as observed, not guaranteed.
  • You supply your own licensed FL Studio installation and a machine that can screen record cleanly with audio.
  • Volume fluctuates with customer demand; most contributors treat this as part-time supplementary work rather than a full load.