$10–14/hr · micro1
You play PC games while capturing synchronized gameplay video, input data, and engine telemetry, annotating scenarios and reporting quality assurance findings.
What you would do
- Record gameplay sessions with per-frame synchronized video and keyboard-mouse telemetry capture
- Collect engine-level signals and in-game events according to project data specifications
- Annotate gameplay scenarios and decisions with accuracy, context, and relevant metadata
- Identify and document gameplay anomalies, bugs, technical glitches, and data collection problems
- Provide regular progress updates and actionable feedback to product and technical teams
Who they want
- Demonstrated expertise in PC gaming with track record in competitive or professional gaming settings
- Experience with gameplay recording tools, telemetry capture systems, or similar technical setups
- Prior experience with game testing, bug reporting, or content evaluation
- Excellent written and verbal communication with emphasis on clarity and proactive updates
- Deep understanding of diverse gaming styles, mechanics, and competitive environments
Main skills
What the interview asks about
1.Telemetry data fidelity
The quality of your captured data directly determines what the AI can learn; gaps or misaligned timestamps make entire sessions unusable.
For example: “Your recording setup has a 3-frame lag between the video and input telemetry in a fast-paced combat sequence. How would you identify and correct this before submission?”
2.Annotation granularity and consistency
If your annotations are too vague, AI systems can't learn the patterns; if they're inconsistent, the system gets confused by conflicting labels.
For example: “You're annotating a 10-minute gameplay segment with 50 decision points. What level of detail do you include and how do you maintain consistency across all decisions?”
3.Bug discovery and documentation
A well-documented anomaly - reproducing steps, video clip, telemetry snapshot - enables engineers to fix it; vague reports waste time.
For example: “During gameplay you notice the character clips through terrain during a specific ability combo. Walk through how you'd capture and report this to the technical team.”
4.Game mechanic mastery and meta knowledge
Your understanding of game systems tells you when behavior is a bug versus intended interaction, and when gameplay is unusual but valid.
For example: “The game exhibits a counterintuitive AI behavior. How do you distinguish between a bug you should report and intended emergent gameplay you should just annotate?”
5.Session reliability and consistency
Missing a session or inconsistent participation breaks training data continuity; the project depends on your steady daily engagement.
For example: “You're scheduled for 3-hour gaming session tomorrow but your internet becomes unstable mid-session. What's your procedure for saving data and notifying the team?”
A task you may get
Record and annotate a 15-minute gameplay segment in a fast-paced PC title, identifying 10-15 key decisions or events, documenting any anomalies, and providing telemetry metadata.
How to prepare
- Test your recording setup end-to-end to confirm video-telemetry synchronization
- Play through the target game titles to understand mechanics and identify common decision patterns
- Collect examples of bugs or anomalies you've encountered and how you'd document them
- Review any telemetry formats or annotation templates from the project brief
The facts
- Pay
- $10–14/hr
- Open to
- Bangladesh, Hong Kong, India, Indonesia, Japan, Kazakhstan, Kyrgyzstan, Malaysia, Pakistan, Philippines, Singapore, Sri Lanka, Taiwan, Thailand, Uzbekistan, Vietnam, Austria, Belarus, Belgium, Denmark, France, Germany, Greece, Italy, Netherlands, Portugal, Russia, Spain, Switzerland, United Kingdom, Argentina, Brazil, Chile, Colombia, Mexico, Peru, Algeria, Bahrain, Egypt, Iraq, Jordan, Kuwait, Lebanon, Libya, Morocco, Oman, Palestine, Qatar, Saudi Arabia, Tunisia, United Arab Emirates, United States, Canada, Nigeria, Kenya, South Africa, Ghana, Ethiopia
- Field
- Other
- Role type
- Robotics
- Posted
- 8/1/2026
- Places left
- 100
We wrote this page from the public micro1 listing. It may be out of date, so read the full posting before you apply.