Software Engineer - Open Source Contributions
Micro1 • Remote
Education
Not stated
Type
Per task
Pay Rate
$50–$100/task
Actively Hiring
37 openings
Apply opens Micro1 in a new tab.
Apply Now → ⚡ Boost your chances - Optimize your resume with Rezi.aiAbout this role
From the Micro1 listing
Role Title: Software Engineer — Open Source Contributions
Role Type: Contractor
Location: Remote micro1 is engaging Software Engineer — Open Source Contributions experts to participate in an impactful customer project focused on high-quality, open source software development. In this role, you'll apply your expertise to help train next-generation AI systems. Your work will shape how models learn, reason, and perform through high-quality, real-world input. No prior experience in AI is required — your domain knowledge is what matters.
Scope of Work
- Develop, implement, and refine new features within existing open source codebases using Python3, Java, Rust, C++, and Typescript.
- Analyze and resolve complex bugs, ensuring robust and maintainable solutions that align with project standards.
- Refactor and optimize legacy code to enhance performance, readability, and scalability.
- Contribute to code validation processes, focusing on accuracy, output consistency, and best coding practices.
- Utilize advanced algorithms and competitive programming techniques to conceptualize and deliver efficient solutions for intricate problems.
- Collaborate remotely with other contributors to review proposed changes and maintain project documentation.
- Deliver clear, concise technical write-ups to articulate solution design and implementation details.
Preferred Qualifications
- Expert-level proficiency in at least two of the following: Python, C++, Java, Rust, Typescript, Go, or C#.
- Extensive experience in open source contributions, particularly in feature development, bug fixing, and codebase refactoring.
- Demonstrated expertise in competitive programming and complex coding problem analysis.
- Strong analytical skills to interpret multifaceted problem constraints and identify multiple solution pathways.
- Exceptional written and verbal communication skills for clear, precise technical documentation and peer collaboration.
- Meticulous attention to detail in code review, validation, and maintenance.
- Comfort working independently in a remote, collaborative environment with a commitment to producing high-quality, well-documented code under project deadlines.
Compensation Structure
Compensation is output-based; experts are paid per task that meets the project specifications. The time required to complete work may vary depending on the expert’s experience and workflow. Minimum submission requirements apply. Experts must submit a minimum of tasks per week.
Start Timeline & Availability
We typically fill roles within 48 hours and are looking for experts ready to jump in right away. If selected, we expect you to start your first tasks within 24–48 hours of completing onboarding.
Requirements
- Python3
- JAVA
- Rust
- Algorithms
- Basics C++
- Typescript
- bug fixing
How long hiring takes
Across the AI training platforms we refer candidates to, the median gap between referral and hire is about 30 days. It varies by platform and role, so treat it as a rough guide for this one.
Interview Prep
This listing calls for these tools directly. Prep for the technical screen:
Key responsibilities
- Develop, implement, and refine new features within existing open source codebases using Python3, Java, Rust, C++, and Typescript.
- Analyze and resolve complex bugs, ensuring robust and maintainable solutions that align with project standards.
- Refactor and optimize legacy code to enhance performance, readability, and scalability.
- Contribute to code validation processes, focusing on accuracy, output consistency, and best coding practices.
Why this role
Compensation is output-based; experts are paid per task that meets the project specifications. The time required to complete work may vary depending on the expert’s experience and workflow. Minimum submission requirements apply. Experts must submit a minimum of tasks per week.
Skills and categories
Explore other opportunities in related specializations:
Related jobs
Browse All Jobs from Micro1
Discover more opportunities on Micro1 that match your skills and interests.
View All Micro1 Jobs →Verified Reviews
Community Reviews
Share your experience with Micro1
Help other candidates make better decisions by leaving a review.
Sign in to leave a reviewLeave your review
Common questions
What does the Micro1 application process look like?
Expect a screening interview with Zara, Micro1's AI recruiter. Prepare for it like a real video call: good lighting, clear audio, verbal answers to technical questions. A human manager reviews the recording afterward, and some roles add a short skills assessment on top.
Can I apply to Micro1 from outside the US or UK?
Yes. Micro1 accepts applicants from most countries worldwide, unlike DataAnnotation or Outlier, both of which cap access to a handful of English-speaking countries. Most roles still require strong written and spoken English.
What does task-based AI training work look like?
Practical, hands-on data work: recording short videos, categorizing images, rating text responses, or analyzing data. Tasks are designed to be short and distinct, typically 5 to 60 minutes each.
What does asynchronous AI training work mean in practice?
No set hours, no check-ins, no meetings. You log in when you want, pick up an available task, complete it, and submit; nobody is waiting on you in real time. That's different from remote employment, where you're expected online during business hours. The tradeoff: you're competing with others for available tasks, so an empty queue means there's simply nothing to do until more work is released.
What does Software Engineering work look like for a Software Engineer - Open Source Contributions?
Tasks here are scoped to Software Engineering, not generic labeling. As a Software Engineer - Open Source Contributions, expect to draw on real domain judgment (evaluating outputs, correcting errors, or providing expert reasoning specific to Software Engineering) rather than following a one-size-fits-all rubric. If you don't have hands-on Software Engineering background, this is likely not the right listing to start with.
What specific skills does this listing call for?
Python3, JAVA, Rust, and Algorithms are named directly in the listing. If you don't have hands-on experience with these, expect the screening process to test for them directly rather than accepting adjacent experience as a substitute.
What does the 'openings' count on this listing mean?
It's Micro1's live count of how many candidates it's still trying to place for this specific role, 37 right now, not a countdown on your individual application. A higher number signals more active demand; it doesn't lower the bar for acceptance.
How much does this specific role pay?
This listing is posted at $50–$100/task, a per-task rate. The range reflects experience level and negotiated terms, not a placeholder, so where you land in it depends on your background and the assessment. Pay can change between when we last checked the listing and when you apply, so confirm the current number on the platform's own application page before committing time.
How does per-task pay translate to an hourly rate?
It doesn't directly, that's the catch. Each task has a listed price and an estimated completion time, but your actual effective rate depends on how fast you work. If a task is estimated at 20 minutes and pays $8, that is $24/hr for a fast worker and $12/hr for a slow one. Track your actual time on the first few tasks before treating the listed rate as your real hourly income.
What happens when I click Apply on this listing?
You'll be taken to Micro1's external site to complete your application there. This listing links through a referral, but the process is identical to applying directly; the link just routes you correctly. Create an account on their site and follow their onboarding steps.