Software Engineer - Open Source Contributions

$50–100/hr

rate as listed

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

Contribute features, bug fixes, refactors, validation work, and technical documentation to existing open source codebases. The project uses expert software engineering work to train AI systems, but prior AI experience is not required.

You would work inside established open source codebases, implementing features, diagnosing complex bugs, refactoring legacy components, improving performance, and validating code for accuracy and consistent output. The scope may involve Python3, Java, Rust, C++, and Typescript, along with remote code review and concise technical write-ups explaining design and implementation decisions.

The platform is likely to screen for specific, verifiable open source contributions and your ability to reason through unfamiliar code under follow-up questioning. Preferred qualifications include expert-level proficiency in at least two of Python, C++, Java, Rust, Typescript, Go, or C#, plus experience with competitive programming, complex constraints, multiple solution paths, and maintainable code changes.

This is a remote contractor role designed for independent, asynchronous work with other contributors. Compensation is output-based, accepted tasks must meet project specifications, and minimum weekly submission requirements apply, although the task count and typical weekly hours are not disclosed. Selected contributors are expected to begin their first tasks within 24–48 hours after onboarding.

Pay band: $50–100/hr

What they look for

Python3
JAVA
Rust
Algorithms
Basics C++
Typescript
bug fixing
feature implementation
codebase refactoring
performance optimization

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 checks whether your claimed experience is traceable to concrete repositories, pull requests, review discussions, and merged outcomes rather than personal projects described as open source work.
A strong answer: Identify one or two contributions with repository and pull request details, then explain the original problem, your exact ownership, reviewer feedback, tests, and the final result. Distinguish clearly between work you authored and work completed by other contributors.
Where people lose it: Candidates lose points by naming popular repositories without identifying a specific change, commit, review thread, or measurable responsibility.

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.

Software Engineer - Open Source Contributions

What they look for

Interview prep — 10 questions

Similar roles