Software Developers: Share Your AI Coding Sessions

$500/task

rate as listed

Workload: ~15h/week
Engagement: Project-based
Location: Location not stated
Field: STEM and Coding

Use OpenCode to complete feature work on a software project you are already building, with each coding session recorded for AI research. The work is remote and flexible, using provided open-weight and Gemini models in one chat per task.

The work

You will work on your own verifiable side project, startup or LLM-powered feature through OpenCode, a terminal-based coding assistant. Each recorded session covers one real development task in one chat, using the provided open-weight and Gemini models. You may choose a model for each task and switch models when that reflects your normal workflow.

What the screening covers

The platform is likely to verify that your project is active, substantive and genuinely yours to develop. Expect questions about recent commits, current architecture, your regular use of tools such as Cursor, Claude Code, Codex or Cline, and how you assess AI-generated code before accepting it. Terminal fluency and practical git use on Mac or Linux are central, while experience with agentic or LLM-integrated features is a plus.

Logistics

This is remote work with a flexible schedule and an immediate start. A session typically involves about 50 turns and 2 to 3 hours of active work, and the full interaction is recorded. Because the research observes normal development behavior, candidates need a project that can be worked on safely in a recorded environment.

Pay band: $500/task

What they look for

Active development of a verifiable software project
Regular use of AI coding assistants
Terminal proficiency on Mac or Linux
Practical git workflow
Ability to evaluate and test AI-generated code
Experience with agentic or LLM-integrated features

Included with this listing

Interview prep — 10 questions

Matched to what this platform's screening actually measures. Answer each out loud in 60–90 seconds: claim → concrete example → implication.

What it tests: This tests whether you have a real, verifiable project with enough ongoing feature work to support recorded coding sessions.
A strong answer: Describe the product, users, architecture and your ownership of the code, then cite recent commits, releases, issues or a repository that can be verified. Identify a concrete feature you are currently implementing rather than discussing only future plans.
Where people lose it: Candidates lose points by presenting a tutorial repository, dormant project or vague idea with no recent development evidence.

Summary, eligibility guidance and screening preparation are prepared by Sidequest from the platform's posting. Check the source listing before applying.

STEM AND CODING on Sidequest

What stem and coding AI work pays

Rates by specialty, the platforms hiring, and every open role in this field.