Junior Software Engineer

$150–200/hr

rate as listed

Workload: ~15h/week
Engagement: Project-based
Location: Worldwide
Field: STEM and Coding

Evaluate AI-generated code, develop coding problems, and review model reasoning across debugging, architecture, and system design. This is a remote contractor role for junior software engineers, with recent experience at a top technology company preferred.

The work

You will assess AI-generated code for correctness, implementation quality, and design. Day-to-day assignments may include identifying defects, comparing possible solutions, reviewing architecture or debugging reasoning, and writing detailed technical feedback that can be used to improve model performance.

Problem creation

You will also create challenging engineering problems, reference solutions, and test cases. The work calls for problems with clear requirements, defensible expected behavior, and tests that distinguish robust implementations from code that only handles obvious examples.

Screening

The platform is likely to verify your software engineering background through specific projects, responsibilities, and dates. Expect follow-up questions on how you evaluate code, construct tests, diagnose failures, assess design tradeoffs, and explain technical decisions in writing. At least one year of software engineering experience at a top technology company is preferred, with at least part of that experience within the past 3 years. Being based in an English-speaking country is also preferred.

Logistics

This is a remote contractor role. The listing does not state a typical weekly workload, working hours, or whether assignments are completed asynchronously, so candidates should confirm scheduling and availability expectations during the process.

Pay band: $150–200/hr

What they look for

System Design
Code Review
Debugging
Algorithms
Data Structures
Software Architecture

Included with this listing

Interview prep — 10 questions

Matched to what this platform's screening actually measures. Answer each out loud in 60–90 seconds: claim → concrete example → implication.

What it tests: This checks whether the preferred employment history is recent, verifiable, and grounded in direct engineering work rather than team-level claims.
A strong answer: Give the employer, dates, product or system context, and your individual ownership. Explain one concrete contribution with its technical constraints, implementation choices, and observable result.
Where people lose it: Candidates lose credibility when they name a company but omit dates, describe only what the team built, or cannot separate their own code from a shared project.

Summary, eligibility guidance and screening preparation are prepared by Sidequest from the platform's posting. Check the source listing before applying.

STEM AND CODING on Sidequest

What stem and coding AI work pays

Rates by specialty, the platforms hiring, and every open role in this field.