Open Source GitHub Maintainer

What you'll do

You review code patches that an LLM wrote for the repository you already maintain, and decide whether you would merge them. That is the whole premise: the customer wants the judgment of the person who knows the codebase best, applied to machine-written contributions, with a written justification for each assessment.

In practice it is the same work as triaging pull requests from strangers, except the stranger is a model and your reasoning is the product. You also peer-review assessments from other maintainers on the project, so your justifications need to hold up to someone who knows a different codebase.

The listing names C, C++, Java, TypeScript, Rust, Go and Python, which suggests repositories across most mainstream ecosystems rather than one stack.

Who qualifies

• Clear, public open source contributions, visible on a GitHub or GitLab profile; this one is stated as a requirement
• Senior software engineering experience
• Maintaining an open source repository and reviewing outside contributions are preferred, and given the task, they are the real qualification
• The ability to explain a review decision in writing, briefly and convincingly

No degree, years of experience or location requirement is stated, and no AI experience is needed.

What it pays

micro1 advertises $150–300/hour, but the ad is explicit that pay is output-based: you are paid per task that meets the project specifications, and the time a task takes depends on you. The hourly band is therefore an equivalent, not a wage. A maintainer who can assess a patch against a familiar codebase quickly will sit at the top; one who has to read unfamiliar corners of the repo for each patch will not.

There is also a minimum weekly submission count (the number is not published) and an expectation of about 15 hours a week with "constant activity", on any schedule you like.

How hiring works

The ad lays out a short funnel: an application with screening questions, an AI interview of about ten minutes, then a hiring manager review. micro1 says it typically fills these roles within 48 hours and expects you to start your first tasks within 24 to 48 hours of finishing onboarding, so apply when you actually have the time free.

Worth knowing

Good:

• One of the highest stated bands on micro1's board
• Open globally, with a flexible schedule
• Work that uses knowledge you already have and nobody else does
• A fast, short hiring process

Less good:

• Per-task pay with a minimum weekly quota; the hourly figure is not guaranteed
• Only relevant if you maintain a real repository; strong engineers without one are unlikely to fit
• About 15 hours a week of sustained activity is expected
• The customer is not named, and the ad does not say whether patches or reviews touch your project's public history
• Contractor engagement: no benefits, your own tax to manage

About this listing

Posted by micro1 on its own jobs portal on 25 September 2026 and read the next day. The band, the per-task compensation, the 15-hour commitment, the global eligibility and the hiring steps are micro1's own text. For GitHub work that does not require maintaining a project, micro1's GitHub Specialist listing records workflows in the GitHub interface at $90–175/hour. See micro1.