• Companies
  • News
By technology
  • Python16k
  • AWS11.2k
  • Kubernetes8.1k
  • Docker7.8k
  • C++5.4k
  • PostgreSQL5.2k
  • SQL4.7k
By category
  • Backend Developer11.3k
  • DevOps Engineer3.3k
  • Machine Learning Engineer3.2k
  • Full Stack Developer3k
  • Data Engineer2.7k
  • Embedded Engineer2.2k
  • Frontend Developer839
By city
  • San Francisco, CA6k
  • New York, NY5.4k
  • Seattle, WA1.3k
  • Washington, DC1.2k
  • Toronto, ON1.1k
  • Boston, MA969
  • Austin, TX944
Work mode
  • On-site21.2k
  • Remote9.6k
  • Hybrid6.8k
Job type
  • Full-time36.3k
  • Contract536
  • Part-time484
  • Freelance210
  • internship4
  • seasonal1
Experience
  • Entry level
  • Mid level
  • Senior
  • Staff+
  • Engineering management

The job board for developers. Find your next role at companies that value great engineering.

© 2023-2026 . All rights reserved.

Logos provided by Logo.dev
All jobs

Problem Design Engineer

idlexperts · United States

Extracted from the posting

Base
$83,200 – $83,200
Remote
Remote, 0-25 hours per week, fully async
Stack
AWS, Azure, C, C++ (company stack)

Part-time code quality reviewer for AI training problems drawn from real production repositories. Reviewers assess whether problems are fair and technically sound, check test quality, and write 2-3 sentence justifications per decision. Work is fully async, 1-4 hours per problem.

What We’re Building

We create high-quality coding problems for training AI models — drawn from real production repositories, not synthetic puzzles. Your role is to ensure these problems are fair, clear, and technically sound.


The Role


Part-Time Code Quality Reviewer | Remote | $40/hr | 0-25 hrs/week

We’re looking for engineers who can trace the intent behind a code change, understand what changes were made and why, and express that clearly in natural language.

This is judgment work, not mechanical testing. You'll make philosophical decisions about fairness and clarity in technical contexts.


What You'll Actually Do

  • Review code changes across unfamiliar repositories and tech stacks
  • Assess problem fairness: Could a skilled engineer solve this with only the given context?
  • Evaluate test quality: Do tests properly validate the intended solution?
  • Write clear justifications for your assessments (2-3 sentences per decision)
  • Flag coherence issues: Inconsistent artifacts, unclear requirements, missing context

Time commitment: 1-4 hours per problem, fully async — work whenever fits your schedule.


Who Should Apply


Ideal candidates:

  • PhD students in CS/computational fields seeking long-term flexible income
  • Open source contributors who care deeply about code quality
  • Undergrad with at least 1 year in CS, ECE, Computational Biology, or related technical programs
  • Professional engineers seeking intellectually interesting part-time work


You'll thrive if you:

  • Have strong software engineering fundamentals
  • Can work independently with minimal supervision
  • Write clearly and precisely
  • Enjoy making judgment calls in ambiguous situations
  • Stay focused during 1-3 hour review sessions


Requirements

  • 1+ years of software engineering experience (internships, research projects, or professional work)
  • Fluent English; strong writing is a must
  • Responsive, independent, and attentive to detail
  • 0–25 hours per week, flexible


Compensation & Growth

  • $40/hour for all review work
  • Performance-based advancement: Top contributors can receive promotions and bonuses
  • Long-term engagement: We're building a scalable team, not a temporary workforce


Application Process

  1. 15-minute async video interview — answer 4 questions about your technical background and work style
  2. Sample problem review — demonstrate your assessment skills on a real coding problem
  3. Onboarding — join our active problem design engineering community and start reviewing


FAQ


Q: Is this suitable for PhD students?
Yes — many of our top contributors are PhD students. The work is fully async and fits around research schedules.


Q: Do I need to be available during specific hours?
No. Work whenever you want. Some problem design engineers work weekends, others weekday evenings.


Q: What if I'm not familiar with the programming language in a problem?
That's expected. You're assessing problem fairness and clarity, not implementing solutions. Familiarity with general software engineering principles is what matters.


Q: How quickly can I start?
If you pass the video interview and sample review, you can start within 1-2 weeks.


Q: Is this a path to full-time employment?
This is a long-term contract role, not a pipeline to full-time positions. We value contributors who excel at this specific type of work.


About idlexperts

idlexperts is the quality assurance division of Idler (YC S25), where we ensure coding problems meet research-grade standards for AI training. Our mission is to build the most reliable QA system for AI coding benchmarks.

Company stack

This posting doesn’t list technologies. These are the ones idlexperts uses across its other roles.

AWSAzureCC++GCPGoJavaJavaScript
idlexperts
idlexperts
Website

Job details

TypePart-time
Work ModeRemote
LevelMid Level
LocationUnited States
Salary$83,200 - $83,200
PostedNov 06, 2026
Apply Now