Customer Success Engineer (LatAm)

Category: Engineering Employment type: FULL_TIME Grade: Mid-level Description: About the role Customer Success Engineer (LatAm) 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. 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. Judge generated code and software engineering agents. Read their debugging traces. Responsibilities Run and reproduce candidate code outputs in a sandboxed environment for Customer Success Engineer (LatAm) assignments. Grade customer success 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. Role details Track: Code review & evaluation Work model: Remote · Independent specialist contractor Compensation: $35000-$50000 year Eligible from: US 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. What you should bring Strong day-job engineering experience — you can read, run, and debug unfamiliar code for Customer Success Engineer (LatAm) 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. Role signals 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. Useful experience 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.