Open Source Contributor

$60–120/hr

rate as listed

Workload: 15+ hrs/week
Engagement: Project-based
Location: Worldwide
Field: STEM and Coding

Create and validate complex technical tasks that test how AI systems reason, write code, and use tools across real-world workflows. This contractor role is aimed at programmers with practical Python ability and substantial, publicly verifiable open-source or original project work.

The work

You will create, solve, review, and validate technical tasks drawn from software engineering, machine learning, science, hardware, or engineering workflows. Day-to-day work can include building reproducible environments, writing reference solutions and tests, defining objective acceptance criteria, reviewing AI-generated code or technical outputs, and explaining model failures precisely.

What micro1 screens for

Practical proficiency with Python is required, along with strong programming ability and meaningful public evidence of technical work. The AI interview includes technical and integrity checks, so expect follow-up questions about specific contributions, implementation choices, debugging decisions, tests, performance work, infrastructure, simulation, or data processing. Maintainer work, merged contributions, substantial original repositories, and public research code are stronger evidence than forks, tutorial-only projects, superficial documentation edits, contribution counts, or AI-generated repositories alone.

Logistics

This is a global, fully remote contractor role with a flexible schedule and a commitment of at least 15 hours per week. The listing does not state that work is fully asynchronous, although tasks appear suited to independent execution. Compensation is output-based and depends on tasks meeting project specifications and quality requirements.

Pay band: $60–120/hr

What they look for

Python3
JAVA
Rust
Basics C++
Typescript
GoLang

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 your claimed work can be tied to specific commits, pull requests, design decisions, and project outcomes rather than repository popularity or contribution counts.
A strong answer: Identify one verifiable project, give its public URL or profile path, distinguish your work from collaborators' work, and describe a technically substantial implementation with concrete artifacts that a reviewer can inspect.
Where people lose it: Candidates lose points by naming a well-known repository without identifying their own merged work, or by relying on forks, tutorial projects, minor documentation edits, or raw commit totals.

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.