Project Lead, AI Model Training

We need to output HTML fragment with sections: About the role (but note the page already shows job title; we should not repeat job title as heading). The posting includes "About NewtonX" then "About The Role". We should include sections for headings present in content: About the role (maybe "About the role" heading), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections where there is real specific content. Let's parse. Content sections: - About NewtonX (company overview) – could be considered "About the role"? Actually "About NewtonX" is company description, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if applicable. We have: About NewtonX: company description. Could be placed under "About the role"? Not exactly. But maybe we treat "About the role" as the description of the role (the bullet after "About The Role"). The "About NewtonX" could be omitted? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include company overview somewhere. Could be placed under a heading like "About the company" but not in allowed list. However we could put it under "About the role" as a preamble? Might be okay. But better to include a section "About the role" containing the description of the role (the paragraphs after "About The Role"). The company overview could be placed under a heading like "About NewtonX" but not in allowed list; maybe we can omit heading and just put as

before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings if needed, but better to stick to those. We could treat "About NewtonX" as part of "About the role" section (maybe preceding). Or we could create a section "About the company" but not in list; risk. Given instruction: "Prefer a few substantive sections over many thin ones." So we can combine. Thus we can have sections: - About the role (includes company overview and role description) - Responsibilities (list of duties) - Requirements / Qualifications (maybe combine) - Benefits (list) - Pay (compensation) - Schedule (location/hybrid/remote) We need to extract specifics. Let's extract: About NewtonX paragraph: "NewtonX is a B2B insights company trusted by the world's most innovative companies to make high-stakes decisions with confidence. We combine a verified network of business professionals with AI-powered research tools to deliver research intelligence faster, more precise, and more defensible than traditional methods. Our clients include Google, Microsoft, TikTok, DoorDash, Stripe, and Coinbase. Our research has been cited by Fortune, Forbes, TechCrunch, Adweek, and the Wall Street Journal. NewtonX has raised $47M from investors including Two Sigma Ventures, Third Prime, XFund, and Citi Ventures." About The Role: paragraphs describing role: "NewtonX is turning the world’s largest verified expert network into the evaluation, post-training, and audit data that enterprises and AI labs need to deploy AI in production. We build high-quality, expert-generated datasets that train and evaluate frontier AI systems — spanning domain eval sprints, custom data solutions, model behavior audits, agentic RL environments, and domain QA-as-a-service. This business is taking off, and we are expanding our Delivery team to meet it. We are hiring a Project Lead to own client engagements end to end, from scoping through delivery, on our data operations platform. You will be the client’s point of contact and the person accountable for the operational execution and the quality outcome across a portfolio of concurrent projects — many of them complex agentic-workflow evaluations. Our commercial team wins the business. From the moment it is won, it is yours: you scope it, configure it, run it, defend its quality, and deliver it. When a client asks how it is going, you are the person who answers. When the spec turns out to be wrong at scale, you are the person who fixes it. You will be joining a small, early Delivery team, working closely with our ML Lead, annotator delivery team, commercial team, and product and engineering. Because the team is still young, you will help build and scale the delivery function itself — the playbooks, quality standards, and processes that everyone who follows you will run on — and you will have direct exposure to NewtonX’s C-level. This is a ground-floor seat in a business we expect to grow extremely quickly, with the career path that comes with it. Location: Remote (US or Canada) or Hybrid (New York City)" Then responsibilities bullet list under "In this role you will": list items: - Scope and set up every engagement - Translate the client’s need into a bounded statement of work. - Turn a training or evaluation objective into concrete task design, a defined quality bar (defect-rate and inter-annotator agreement targets), an annotator profile, and — for agentic projects — an environment and tool strategy. - Configure the project on the platform. - Stand up the multi-layer quality pipeline, task forms, grading rubrics, annotator enablement, and routing. - Author the first-draft guidelines and gold set with the ML Lead, and pressure-test them before production starts. - Most delivery failures are scoping failures; your job is to catch them here. - Run production - Own quality, throughput, and cost. - Track how each project is performing against its targets, diagnose what is drifting, and act before it reaches the client. - Manage the annotator pool on your projects. Assignment, layer access, qualification, and performance — working with the annotator delivery team to get the right experts on the right tasks. - Keep annotators aligned. Run project channels and calibration sessions, handle exceptions and escalations, and adjust configuration as the work reveals what the spec missed. - Own the client relationship - Be the client’s point of contact throughout — scoping calls, mid-project updates, quality escalations, and delivery. - Manage expectations against scope, and diagnose acceptance issues candidly when they arise. Clients trust the person who tells them early. - Grow the account from the inside. Surface expansion opportunities and new use cases to the commercial team, and act as the technical subject matter expert on calls when new work is being scoped. - Deliver and close out - Assemble and deliver batches on schedule, and own the handoff to the client. - Run client acceptance testing against agreed criteria, capture sign-off, and trigger the commercial milestone. - Run the post-mortem and feed what you learned back into guidelines, tooling, and the next scope. - Build the machine as you run it - Turn each engagement into repeatable process. Codify what works into playbooks, templates, and quality standards that the next Project Lead can run from day one. - Be the voice of delivery to product and engineering. You will be running on a platform that is still being built; what you flag gets built. Then "Who You Are": list of requirements/qualifications: - 3+ years of experience in data labeling, RLHF/SFT, or AI evaluation delivery — you have shipped real annotation or evaluation projects at a data labeling company (Scale, Surge, Mercor, Snorkel, Handshake, Centific, Labelbox, SuperAnnotate, or similar) or inside an AI lab. This is a firm requirement; we are not looking for a generalist project manager. - An operator who goes into the weeds. You are comfortable owning quality metrics, debugging a stalled queue, and rewriting a rubric that is not holding up in production. - Client-facing and credible. You can run a scoping call with a technical buyer, deliver bad news without losing the room, and translate operational mechanics into terms a client cares about. - Analytically rigorous. Data analysis skills using SQL or Python are a strong plus. - A builder. Processes here are young and some are still manual. You want to stand things up rather than inherit a finished machine. - Exceptional at holding many threads. You will run several concurrent projects with different clients, quality bars, and annotator pools. - Adaptable and resilient. Specs change, clients change their minds, and no two weeks look the same. You roll with it and find the new angle. - Discreet. This role handles annotator personal data and client-confidential information under strict data-security and confidentiality standards; all work stays within approved systems. - Valid US or Canadian work authorization required. Visa sponsorship is not available for this role. Then "What We Offer": benefits list: - Competitive compensation: $150-240K total on target compensation + participation in our company stock buying program - Massive impact: the chance to help build a new business unit from the ground up with direct C-level influence at an extremely fast-growing late-stage startup - Fast-track career growth toward operational and commercial leadership - Excellent medical, dental, and vision insurance - 401k match with immediate vesting - Health savings/flexible savings account, and pre-tax commuter benefits - Paid time off: vacation, holidays, sick, and parental leave - A diverse, collaborative, and positive culture where we invest in and celebrate each other’s success (happy hours, team projects, and retreats) Then EEO statement (remove). Location: Remote (US or Canada) or Hybrid (New York City) – this could be Schedule? Actually schedule refers to work schedule; location is separate. But we have Schedule heading allowed; we could put location under Schedule? Might be okay to put location under Schedule or maybe we omit Schedule if not specified. The posting does not specify work hours/schedule; only location. So we should not create Schedule section unless posting states it. It does not state schedule/hours. So we omit Schedule. Pay section: we have compensation details: "Competitive compensation: $150-240K total on target compensation + participation in our company stock buying program". That's pay. Benefits section: list of benefits. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We need to decide which sections to include: - About the role (maybe combine company overview and role description). Could be two paragraphs: first about NewtonX, second about the role. - Responsibilities: list of duties (the bullet list). We'll need to flatten into

  • items. Each top-level bullet maybe a
  • containing sub-items? Could nest
    inside
    • . That's fine. - Requirements/Qualifications: we can combine into one section "Requirements" (or "Qualifications"). Use
      • . - Benefits:
        • . - Pay: maybe a

          with compensation details. We should not include empty sections. Let's craft. HTML:

          About the role

          NewtonX is a B2B insights company trusted by the world's most innovative companies to make high-stakes decisions with confidence. We combine a verified network of business professionals with AI-powered research tools to deliver research intelligence faster, more precise, and more defensible than traditional methods. Our clients include Google, Microsoft, TikTok, DoorDash, Stripe, and Coinbase. Our research has been cited by Fortune, Forbes, TechCrunch, Adweek, and the Wall Street Journal. NewtonX has raised $47M from investors including Two Sigma Ventures, Third Prime, XFund, and Citi Ventures.

          NewtonX is turning the world’s largest verified expert network into the evaluation, post-training, and audit data that enterprises and AI labs need to deploy AI in production. We build high-quality, expert-generated datasets that train and evaluate frontier AI systems — spanning domain eval sprints, custom data solutions, model behavior audits, agent