AI Trainer Guide Browse jobs

micro1 role

Open Source Contributor (GitHub) at micro1

Software engineers with a public open-source track record create, solve and review coding problems spanning front-end plus back-end systems, and help translate full builds between programming languages. They explore unfamiliar repositories, reproduce bugs, write tests, and judge AI-generated patches. Candidates should be ready to discuss their own repositories and pull requests.

Apply on micro1

Referral link. If micro1 hires you through this link and you meet its conditions, we may be paid a referral fee.

What you would do

  • Explore unfamiliar repositories and build or fix front-end plus back-end components
  • Reproduce software issues and trace their root causes
  • Write end-to-end, unit, integration and regression tests for the code
  • Judge AI-generated patches for correctness, security and maintainability

What the listing asks for

  • A GitHub profile that is public or can otherwise be verified
  • Real ownership of, or contributions to, open-source repositories
  • Strong software engineering background in systems, tooling, full-stack, back-end or front-end work
  • Experience with multiple programming languages
  • Can read and change codebases you have not seen before

Suits professionals who are working engineers with real open-source contributions they can discuss in detail.

The listing as micro1 posted it

This is micro1's public listing for the role, read October 29, 2026, with dashes and placeholder links cleaned up. The listing is micro1's text; the summary above and everything below it is ours.

Pay: $100-$150/hour

Location: Global, fully remote

Job Type: Contractor (~15 hours per week)

Schedule: Flexible - you choose the hours and days you work, including weekends if needed

We are looking for highly skilled Open-Source Software Engineers to contribute to an AI training project involving software development, repository exploration, debugging, system architecture, and code evaluation.

The work involves creating, solving, reviewing, and validating challenging software-engineering tasks across front-end and back-end systems and helping with translating full coding builds from one particular language into another.

We are particularly interested in engineers who own or maintain open-source repositories or have made meaningful contributions to established projects. Contributions should demonstrate real engineering ability, not only documentation updates, dependency bumps, formatting changes, or minor typo corrections.

Candidates should be prepared to discuss specific repositories, pull requests, issues, and code they personally authored.

What You’ll Work On

  • Explore and understand unfamiliar software repositories.
  • Implement, modify, and debug front-end and back-end components.
  • Trace data and execution across interfaces, services, libraries, APIs, databases, and external dependencies.
  • Reproduce software issues and identify their underlying causes.
  • Implement solutions that fit an existing project’s architecture and contribution standards.
  • Write unit, integration, regression, and end-to-end tests.
  • Review AI-generated patches for correctness, completeness, security, and maintainability.

Required Qualifications

  • A public or otherwise verifiable GitHub profile.
  • Meaningful ownership of or contributions to one or more open-source repositories.
  • Strong software-engineering experience across front-end, back-end, full-stack, systems, developer tooling, infrastructure, or another substantial technical area.
  • Experience with multiple programming languages.
  • Ability to understand and modify unfamiliar codebases.

Relevant languages may include TypeScript, JavaScript, Python, Java, Go, Rust, C++, C#, Ruby, PHP, or other languages used in substantial open-source projects.

Process

  • Apply to the role and complete the screening questions.
  • Complete an AI interview of approximately 30 minutes.
  • Complete the hiring manager review.

Compensation Structure

Compensation is output-based. Experts are paid per task that meets the project specifications. The time required to complete each task may vary depending on the expert’s experience and workflow.

Minimum submission requirements apply. Experts must submit a minimum number of tasks per week.

Start Timeline & Availability

We typically fill roles within 48 hours and are looking for experts who are ready to begin immediately. If selected, you will be expected to start your first tasks within 24-48 hours of completing onboarding.

Apply for this role on micro1

Referral link. We may be paid a referral fee.

Pay and terms

The listing states $100 to $150 per hour. That is micro1's listed rate for the project. It is not a promise of earnings, and the listing does not guarantee a number of hours. The same listing also says pay is output-based, paid per task that meets the project specifications, so what you earn per hour depends on how fast you complete accepted tasks.

micro1 engages experts as contractors. Its help library says payments are made in USD twice a month and that contracts and payroll run through Deel. Payments cannot be processed until identity verification there is complete. Read our micro1 review for what workers say about project availability and support.

Before you apply

Engineering listings usually ask for years of professional experience, and some ask for a public code history such as open-source commits. Have your profile or repositories ready to link.

Applying starts with an AI interview, then certification, then matching to projects by recruiters. micro1 says certification does not guarantee a project, so treat this as flexible work and not as a job offer. The how to become an AI trainer guide walks through each step.

Apply on micro1

Referral link. We may be paid a referral fee.

People also ask

What is an open source contributor?

In micro1's Open Source Contributor (GitHub) listing, it means an engineer who owns or maintains open-source repositories, or has made meaningful contributions to established projects. The listing says contributions should show real engineering skill, so documentation updates, dependency bumps, formatting changes and typo fixes alone do not count. It requires a public or verifiable GitHub profile and readiness to discuss your own pull requests.

Do open source contributors get paid?

At micro1, this contractor role lists $100 to $150 per hour, though compensation is output-based: experts are paid per task that meets the project specifications, and a minimum number of tasks per week applies. The listing says about 15 hours a week on a flexible schedule. Listed pay is not a guarantee of income, and micro1 offers no guaranteed hours.

How do you put open source contributions on a resume?

This page does not give resume advice. What the micro1 listing says is that it wants a public or otherwise verifiable GitHub profile and contributions that show real engineering ability, not only documentation updates, dependency bumps or typo fixes. Candidates should be ready to discuss repositories, pull requests and issues they personally authored. Process details are in the micro1 review.

How much does the Open Source Contributor (GitHub) role at micro1 pay?

The listing states $100 to $150 per hour. That is micro1's listed rate for the project, not a promise of earnings, and hours are not guaranteed. The listing also says pay is output-based, paid per accepted task, so your hourly earnings depend on how quickly you complete tasks. Check the listing itself for the current figure.

Is the Open Source Contributor (GitHub) role remote?

Yes. The listing describes it as remote work. On where you can be based, it says: remote, worldwide. Read the eligibility line on the listing before you apply.

How do I apply for the Open Source Contributor (GitHub) role?

Open the listing on micro1's site and apply there. Applying starts with an AI interview, followed by certification and matching to projects by recruiters. micro1 says certification does not guarantee a project. Our how to become an AI trainer guide covers each step.

Is this listing still open?

We read micro1's public listing on October 29, 2026. Roles close without notice, so confirm on the listing itself. If it has closed, the other software engineering roles on this site are linked below.

Related roles at micro1

More remote software engineer jobs

Related roles in other fields

All remote software engineer jobs · Every open micro1 role · Also browse careers at micro1, remote data scientist and ML engineer jobs, remote engineering and CAD jobs

Related guides

Sources and method

  • micro1 public job listing for this role, read October 29, 2026. The summary, task and requirement lines are our paraphrase of that listing.
  • The questions under People also ask: Google's related questions for this kind of role in the United States, as reported by Ahrefs, pulled October 29, 2026. Answers are ours, written from the listing and from our own sourced micro1 pages.
  • micro1 help library and expert guide for payment timing and the hiring steps, read 17 October 2026.

Listings change without notice. If this page is out of date, tell us.

Apply on micro1

Referral link: we may be paid if micro1 hires you.