Open Source Maintainer Expert

$150/hr

rate as listed

Workload: 5–20 hrs/week
Engagement: Project-based
Location: Worldwide
Field: STEM and Coding

Review real engineering tasks using the standards you apply to pull requests on established open source projects. This remote role is intended for maintainers, core contributors and regular reviewers with a substantial public GitHub record.

The work

You will assess code changes for correctness, design quality and maintainability. Each review involves identifying bugs, security concerns and missed edge cases, then writing specific feedback about what works, what needs revision and why. The goal is to apply a consistent review standard similar to the one you use on projects you maintain.

What AfterQuery screens for

The platform looks for a verifiable role as a maintainer, core contributor or regular reviewer on an open source project with 1,000+ GitHub stars. Candidates should have at least three years of public GitHub activity, substantial merged work in established repositories, a record of reviewing other contributors' pull requests and strong written English. Experience maintaining a widely used library, framework or developer tool, reviewing across multiple languages or ecosystems, or working professionally as a software engineer is preferred.

Logistics

The project is fully remote and flexible, with an expected commitment of 5 to 20 hours per week. A review typically takes about 30 minutes. The listing does not specify whether work is formally asynchronous, so candidates should confirm turnaround and scheduling expectations during onboarding. Include your GitHub profile when applying.

Pay band: $150/hr

What they look for

Open source maintenance or regular pull request review on a project with 1,000+ GitHub stars
Substantial merged contributions in established repositories
At least three years of public GitHub activity
Code review for correctness, design, security and maintainability
Clear, specific written feedback in English
Consistent evaluation judgment across different implementations

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 verifies that your involvement meets the project's scale and responsibility requirements rather than consisting of occasional contributions.
A strong answer: Name the repository, describe your formal or practical role, state how long you have held it and point to visible evidence such as merged pull requests, review threads or maintainer permissions.
Where people lose it: Candidates lose points by naming a popular repository but showing only isolated commits, issue comments or pull requests without evidence of recurring review 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.