$30–40/hr · Mercor · Hourly, 40 hours a week
A music producer or audio engineer using FruitLoops Studio on Windows who contributes high-resolution UI screenshots and production workflow feedback to test the digital audio workstation.
What you would do
- Capture detailed, high-resolution screenshots of FruitLoops interface elements, menus, workflows, and features directly from your Windows PC
- Document your actual music production workflows within FruitLoops, including sequencing, mixing, effects, and export processes
- Describe specific UI elements, dialog boxes, toolbar functions, and navigation patterns within the application
- Provide feedback on which interface features are intuitive versus confusing or difficult to locate during typical production tasks
- Share observations about workflow efficiency, feature organization, and user experience challenges you encounter
Who they want
- Windows PC user with FruitLoops Studio already installed and actively used for music production, beatmaking, or audio engineering
- Access to a high-resolution display capable of capturing screenshots at 2.5+ megapixels (single high-res monitor or dual-monitor setup)
- Hands-on experience with digital audio workstation concepts, music production, sequencing, or mixing
- Ability to describe audio production workflows and interface interactions clearly and in detail
Main skills
What the interview asks about
1.DAW workflow documentation
You need to demonstrate understanding of how FruitLoops production flows work and be able to walk through realistic scenarios that would appear in screenshots.
For example: “Walk me through a typical workflow in FruitLoops when you're laying down a drum pattern and then layering synth tracks. What are the key steps, what interface elements do you interact with, and how would you screenshot the most important stages?”
2.Display resolution requirements
Screenshots must meet strict technical specs (2.5+ megapixels) for training data quality. You need to understand whether your display setup qualifies.
For example: “You have a 1920x1080 monitor on your Windows PC. The requirements mention that a single 1080p screen does not qualify, but a dual-monitor setup with two 1920x1080+ monitors does. Does your setup work, and if not, what would you need?”
3.Mixing and effects interface
FruitLoops mixing and effects sections are complex. You need real production experience to accurately describe what's happening in those UI areas.
For example: “You're capturing screenshots of your mixer in FruitLoops where you've added compression on the snare track, reverb on the vocals, and an EQ across the master bus. Describe how the mixer window displays these and what details would be important to show.”
4.Feature interaction description
Non-specialists will use your screenshots to understand FruitLoops features. Your descriptions need to be clear and precise about where things are and how they work.
For example: “You're describing how to access and configure audio export settings in FruitLoops. Walk through the menu structure, the options available, and potential confusion points where users might not find what they're looking for.”
5.Usability issue identification
Your production experience helps spot interface design problems or workflow friction that developers should address to improve the user experience.
For example: “You notice that the browser pane for loading drum samples sometimes takes several clicks to navigate to a specific folder, whereas the instrument selection works differently. Is this a usability inconsistency worth flagging, and how would you describe it?”
A task you may get
Capture three screenshots of FruitLoops showing your pattern editor, mixer, and effects chain. Write one sentence per screenshot describing what's visible.
How to prepare
- Verify your Windows display meets requirements: single high-res monitor or dual 1920x1080+ monitors, and test a full-resolution screenshot
- Open FruitLoops and walk through a complete production workflow from pattern creation through mixing to identify the key UI stages you'd capture
- Research FruitLoops terminology and feature names so you can describe interface elements and workflows accurately and consistently
- List 3-5 usability challenges or confusing UI aspects you've encountered in FruitLoops that might be worth documenting
The facts
- Pay
- $30–40/hr
- Hours
- Hourly, 40 hours a week
- Where
- Remote
- Field
- Language and Audio
- Posted
- 9/13/2026
- Places left
- 10
We wrote this page from the public Mercor listing. It may be out of date, so read the full posting before you apply.