Software Engineer – Backend

$30–100/hr

rate as listed

Workload: ~15 hrs/week
Engagement: Project-based
Location: Location not stated
Field: STEM and Coding

Create realistic backend feature implementation and bug-fix tasks that test how AI systems reason about production code. Build deterministic verifiers that accept reasonable valid solutions while rejecting incorrect or incomplete submissions.

The work

You will design challenging, realistic coding tasks based on backend engineering work, including feature implementation, bug fixes, debugging, performance improvements and refactoring. For each task, you will implement deterministic verification that recognizes multiple reasonable solutions while rejecting code that fails the stated requirements, tests or operational constraints.

What the platform screens for

The screening focuses on evidence that you have built scalable services and APIs, diagnosed bugs and bottlenecks, written automated tests and reviewed production code. Strong backend experience is expected in Java, Node.js, Go, Rust, Typescript, Python, C++ or similar. No prior AI experience is required, but you should be prepared to explain technical decisions and complete the interview and assessment without outside assistance.

Working arrangement

This is a remote contractor role at approximately 15 hours per week. Hours and days are flexible, including weekends, but the project has minimum weekly submission requirements and expects selected contributors to begin their first tasks within 24 to 48 hours after onboarding.

Compensation

Compensation is output-based, with payment tied to tasks that meet project specifications rather than time spent. The time needed for each accepted task will depend on its complexity and your workflow.

Pay band: $30–100/hr

What they look for

Python3
JAVA
Rust
Algorithms
Basics C++
Typescript
bug fixing
feature implementation
codebase refactoring
performance optimization

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 tests whether your backend experience includes concrete ownership of architecture, operational constraints and production outcomes rather than isolated endpoint implementation.
A strong answer: Describe the service's purpose, traffic or workload profile, your personal contribution, the main design decisions and a measurable reliability, latency or throughput result. Separate your work clearly from the broader team's work.
Where people lose it: Candidates lose points by calling a system scalable without giving its workload, failure modes, architecture or evidence that it operated under the claimed conditions.

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.