Principal Engineer / Professor — Technical Expert

AuraOne Human Data; United States; Remote; USD 110,000 - 255,000; Full time

Benefits offered by this job

Health insurance

Job summary

AuraOne, Inc. is seeking a Principal Engineer / Professor — Technical Expert to remotely review production code, debug traces, and evaluate AI outputs against correctness standards. Reviewers reproduce failures, write minimal tests, and explain fixes so the modeling team can target gaps.

You will grade solutions for correctness, style, and edge-case handling, document recurring failures, and calibrate against gold-standard reviews to maintain high inter-rater reliability.

Qualifications

• Strong day-job engineering experience — you can read, run, and debug unfamiliar code for Principal Engineer / Professor — Technical Expert work.
• Comfort writing concise unit tests that capture a single failure mode.
• Familiarity with a testing framework. pytest, Jest, or JUnit. Go test, RSpec, or whatever you use.
• Clear written reasoning — your review note has to convince another 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 Principal Engineer / Professor — Technical Expert assignments.
• Grade principal engineer / professor technical 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.

Job description

Principal Engineer / Professor — Technical Expert is a remote engineering review track for evaluating production code, debugging traces, and developer-facing AI outputs against real-world correctness standards. Reviewers reproduce failures, write the unit test the model should have written, and explain the fix so the modeling team can target the gap.

Why this role matters

Engineering model quality lives or dies on whether the generated code actually compiles, passes tests, and handles edge cases. AuraOne pairs experienced engineers with the modeling team to grade outputs the way a code reviewer would.

Responsibilities

• Run and reproduce candidate code outputs in a sandboxed environment for Principal Engineer / Professor — Technical Expert assignments.
• Grade principal engineer / professor technical 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.

Qualifications

• Strong day-job engineering experience — you can read, run, and debug unfamiliar code for Principal Engineer / Professor — Technical Expert work.
• Comfort writing concise unit tests that capture a single failure mode.
• Familiarity with a testing framework. pytest, Jest, or JUnit. Go test, RSpec, or whatever you use.
• Clear written reasoning — your review note has to convince another senior engineer.
• Reliable async availability for at least 10 hours per week.
• Prior code-review or technical-interview-grading experience is a plus.

Example tasks

• Reproduce a generated engineering solution to a coding task, run the test suite, and grade it.
• Write the smallest failing test that demonstrates a model's edge-case bug.
• Compare two paired solutions and rank them with a written rationale tied to the rubric.
• Triage a security issue surfaced by a model and document the patch the model should have produced.

Nice to have

• Open-source contributions or a public portfolio that demonstrates production-quality code.
• Experience with the target language's standard tooling, linters, and idiomatic style guides.
• Familiarity with security-review checklists (OWASP, CWE) and AppSec patterns.

Skills

• Code review
• Debugging
• Unit testing
• Software engineering judgment
• Principal Engineer / Professor Technical engineering review

Work model

Remote — US-eligible. Remote · Independent specialist contractor. Employment type: CONTRACTOR. Applicants must be authorized to work from US.

Compensation

$80- $185/hour