Description review

Open Source Contributor (GitHub)

micro1 · Remote · back to the listing

HR standards

78/100

solid

Title ↔ description

64/100

needs work

Reads as

Full-Stack Engineer

84% confident

How others title the same work

Large employers

  • Software Development Engineer, Influencer Management Adobe
  • Senior Software Engineer (EAA) Coinbase
  • Senior Software Engineer, Full Stack (Coinbase Advisor - Agentic Trading) Coinbase
  • Senior Software Engineer (Typescript), AI Clients: Duo CLI GitLab
  • Grafana Labs | Senior/Staff Software Engineer - AI / Agentic apps | 100% Remote (US + Canada) | Grafana Labs

Startups

  • Founding Software Engineer Aglide
  • Product Engineer (Founding team) Aglide
  • AiMi | Full Stack AI Engineer | Remote(Everywhere) | Full-time AiMi
  • Staff Software Engineer AiPrise
  • ALBERT | REMOTE ALMOST ANYWHERE IN THE WORLD | Hiring principal and distinguished ALBERT

What the listing never says

  • No section describes what the person would actually do. Scope clarity

The listing, marked up

Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.

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.

Originally posted on Himalayas

How this was produced

Highlights are found by rule, not by a model: each one is a phrase matched at a known position, and every note is a template we wrote. The two scores come from a typed-decision model (Jev) that reads the listing against the official role definition and real listings for the same role, and returns probabilities rather than prose — it never writes any of the words on this page, and never chooses what to highlight.

Deterministic penalty applied to the HR score: 8 points (from 86 before penalties). Reviewed 21 Sep 2026.