If you've spent years maintaining an open source repository — reviewing pull requests, fixing bugs, writing documentation — that unpaid labour may now have a market value you didn't expect. A company called micro1 is hiring open source GitHub maintainers to evaluate code patches written by large language models, and they're paying for it.
The role is part-time, remote, and explicitly does not require any background in artificial intelligence. What it requires is something thousands of developers already have: a public track record of real contributions to real code.
What Exactly Is This Open Source GitHub Maintainer Role?
According to the job description, micro1 is engaging Senior Software Engineers as contractors to support a customer's project. The work involves reviewing code patches generated by an LLM for repositories the applicant maintains, then providing a professional assessment of each patch.
In plain terms: an AI writes code. You — the person who actually knows that codebase — judge whether it's correct, safe, and worth merging. Your feedback then helps train the model to do better next time.
The commitment is roughly 15 hours a week. The location is fully remote. The title is contractor, not full-time employee.
Why AI Companies Are Suddenly Hunting for GitHub Maintainers
Large language models have become remarkably good at generating code that looks right. The problem is that "looks right" and "is right" are very different things in production software.
Models struggle with the kind of judgment that comes from deep familiarity with a specific codebase — understanding why a particular function was written a certain way, which edge cases matter, and what could break downstream. That knowledge lives in the heads of maintainers, not in training data.
So AI companies are now paying to access it directly. The logic is straightforward: if you want a model to write better code, you need people who can tell the difference between good code and plausible code.
The Eligibility Bar: Your GitHub Profile Is the Resume
The job posting is unusually direct about qualifications. Applicants must have clear open source contributions and profiles to showcase them — specifically on GitHub or GitLab.
This is a meaningful shift in how hiring works. Instead of a traditional resume, your commit history, merged pull requests, issue discussions, and code reviews become the primary evidence of your competence. For maintainers who have spent years building that record, it's a credential that finally has a commercial use case.
Notably, the posting says no prior AI experience is required. The company is not looking for machine learning engineers. It's looking for people who understand software deeply enough to catch what a model gets wrong.
Who This Actually Affects — and Who It Doesn't
This role is not for beginners. The posting targets Senior Software Engineers, and the emphasis on maintaining repositories suggests they want people with sustained responsibility for a codebase, not occasional contributors.
If you've contributed a few bug fixes to a popular project, that likely won't clear the bar. If you've been the person merging PRs, cutting releases, and deciding what gets into main for years — that's the profile being sought.
For that group, the appeal is obvious: flexible hours, remote work, and pay for expertise they've already built. For everyone else, it's a signal about where the value in software careers may be heading.
What micro1 Has Said — and What Remains Unclear
micro1 describes itself as engaging expert engineers to help train next-generation AI systems, with the stated goal of shaping how models learn, reason, and perform through high-quality real-world input.
What the posting does not specify: the exact pay rate, the duration of the contract, which repositories or languages are involved, or how the evaluation work is structured day to day. Those details would typically emerge during the application process.
It's also worth noting that this is a contractor arrangement, not employment. That distinction matters for benefits, job security, and tax treatment depending on where you live.
The Bigger Pattern: Domain Experts as AI Trainers
This role is part of a broader trend. Over the past two years, AI companies have quietly built a shadow workforce of doctors, lawyers, mathematicians, and now senior engineers — all paid to evaluate and correct model outputs in their areas of expertise.
The reasoning is consistent across domains: models need human judgment to improve, and the best judgment comes from people with real-world experience, not from people who study AI as a subject.
For open source maintainers specifically, this is a notable development. Their work has long been described as undervalued and underfunded. Now, at least in this narrow case, the same skills are being treated as a paid commodity.
Risks and the Balanced View
There are reasons for caution. Contractor roles in AI training have drawn criticism for inconsistent pay, unclear long-term prospects, and the risk of being used to automate the very work the contractor does.
There's also a philosophical tension worth naming: maintainers are being paid to help train models that may eventually reduce demand for certain kinds of software work. Whether that's a fair trade is a question each person has to answer for themselves.
And practically speaking, a 15-hour-a-week contract is not a career. It's a supplement — useful, but not a replacement for a full-time role.
What Maintainers Should Do If They're Interested
If you have a strong GitHub or GitLab profile and want to explore this, the first step is making sure your contributions are visible and well-documented. Pin your most significant repositories. Ensure your commit history reflects sustained involvement, not just a burst of activity.
Before applying, it's worth clarifying the pay rate, contract length, and whether the work involves repositories you actually maintain or unfamiliar codebases. Those details determine whether the role is genuinely a good fit.
And if you're earlier in your career, treat this as a signal rather than an opportunity. The path to roles like this runs through years of real contribution to real projects.
What Could Happen Next
If this model works, expect more of it. AI companies need domain experts across every field where models are deployed, and software engineering is one of the highest-value domains.
It's plausible that within a few years, "AI evaluation" becomes a recognised side income for experienced developers — similar to how technical writing or conference speaking supplements many careers today.
Whether that's a healthy development or a warning sign depends on your perspective. Either way, it's happening.
Our Take
This story is small on its surface — one company, one contract role — but it captures something larger about how AI is reshaping knowledge work. The skills that made someone a good maintainer (deep codebase knowledge, judgment, patience with detail) are exactly the skills AI companies now need to buy.
For maintainers, that's a rare moment of leverage. For the rest of us, it's a reminder that expertise built in public, over years, is increasingly the kind of asset that gets noticed — and paid for.
Frequently Asked Questions
What is the open source GitHub maintainer role at micro1?
It's a part-time contractor position where experienced maintainers review code patches generated by large language models and provide professional assessments. The work is remote, roughly 15 hours a week, and requires no prior AI experience.
Do I need AI experience to apply?
No. The job posting explicitly states that no prior AI experience is required. What matters is your domain knowledge as a software engineer and your track record of open source contributions.
What qualifications are required?
Applicants must be Senior Software Engineers with clear, verifiable open source contributions on platforms like GitHub or GitLab. The role targets people who maintain repositories, not occasional contributors.
Is this a full-time job?
No. It's a contractor role at approximately 15 hours per week. It's best understood as a supplement to other work rather than a full-time position.
