Pro members applied to this job 36 hours before you saw itGet Pro ›

g2i - Remote Python Senior Software Engineer, AI Training

Remote - Anywhere$208k - $416k4d ago

Remote Senior WW Senior Software Engineer Principal Python TypeScript JavaScript Claude Cursor Loom Mentoring

Requirements

• Senior, Staff or Principal-level engineer (or equivalent experience) • Strong background in TypeScript/JavaScript or Python • Hands-on experience with at least one of OpenAI Codex, Claude Code or Cursor • Deep familiarity with modern AI-assisted dev workflows • Able to evaluate code without executing it or reviewing every line • Strong written and spoken English (B2 or above). You'll be writing detailed feedback and recording short video explanations, so this is a hard requirement • Comfortable giving direct, opinionated feedback • High bar for what good engineering looks like • Prior exposure to prompt design or evaluation workflows • Experience mentoring senior engineers or defining engineering standards • ENGAGEMENT DETAILS • Rate: $100-$200/hour depending on experience and location • Hours: 10-20 hours/week, flexible • Duration: ongoing. Projects run from about two weeks to a few months each, and we offer new ones to evaluators who do well • Start: as soon as you clear the take-home and a project has an open seat • Process: one take-home evaluation exercise with a recorded Loom walkthrough. No interview

Responsibilities

• Evaluate AI-generated coding interactions end to end • Judge whether outputs are useful, correct at a high level, and aligned with how a strong engineer would think • Assess the quality of explanations and reasoning, not just the code • Distinguish between levels of response quality (what makes something a 2 vs a 4) • Give clear, opinionated feedback in writing on what worked, what didn't, and what felt off or misleading • Help define what great looks like when working with tools like Cursor, Codex and Claude Code • WHAT WE MEAN BY "TASTE" • We're looking for engineers who can answer questions like: • Does this feel like something a strong engineer would actually say? • Is this explanation helpful, or just technically correct? • Is the model guiding the user well, or just dumping output? • Would this interaction build or erode trust? • You should be comfortable making subjective but rigorous judgments, and explaining them clearly.