Remote Control System Review Engineer — Testing & Debugging

AuraOne, Inc.; United States; Remote; USD 83,000 - 131,000; Full time

Job summary

AuraOne, Inc. is seeking a Control System Engineer on a remote, contractor track to evaluate production code, reproduce failures, and write minimal tests that reveal edge-case bugs.

You will grade model outputs for correctness, document failure modes, and provide written rationales to guide the modeling team. Requires strong debugging, test-writing, and clear technical communication with at least 10 hours/week availability.

Qualifications

• Strong day-job engineering experience to read, run, and debug unfamiliar code.
• Comfort writing concise unit tests that capture a single failure mode.
• Familiarity with a testing framework (pytest, Jest, JUnit, Go test, RSpec, etc.).
• Clear written reasoning to convince a senior engineer.
• Reliable async availability for at least 10 hours per week.
• Prior code-review or technical-interview-grading experience is a plus.

Responsibilities

• Run and reproduce candidate code outputs in a sandboxed environment for Control System Engineer assignments.
• Grade control system engineer engineering review solutions for correctness, style, and edge-case handling.
• Write minimal failing tests that demonstrate the bug a model output missed.
• Compare paired solutions and rank them with a written rationale tied to the rubric.
• Tag failure modes (compile error, runtime crash, off-by-one, security issue) with severity scores.
• Document recurring code-generation failures so the modeling team can target them.
• Calibrate against gold-standard reviews to keep inter-rater agreement above target.

Skills

Code review

Debugging

Unit testing

Software engineering judgment

Control System Engineer engineering 1

Tools

pytest

Jest

JUnit

Go test

RSpec

Job description

AuraOne, Inc. is seeking a Control System Engineer on a remote, contractor track to evaluate production code, reproduce failures, and write minimal tests that reveal edge-case bugs.

You will grade model outputs for correctness, document failure modes, and provide written rationales to guide the modeling team. Requires strong debugging, test-writing, and clear technical communication with at least 10 hours/week availability.