cursor

Software Engineer, RL Data

Listed by employer · Checked

Posted within 60 days ·

  • onsite
  • FullTime
  • Engineering
  • San Francisco
Work arrangement
onsite
Employment
FullTime
Stated compensation
Not specified
Apply on company website ↗
01 / A QUICK CHECK BEFORE YOU APPLY

Does the location policy fit?

Choose where you would work from. We’ll compare it with the posting’s stated requirements.

Choose the country you will work from. You can change this anytime.

Country and sponsorship changes take effect when you click Check eligibility.

Choose a country to check geographic compatibility. The source requirements are available below.

Source: ashbyChecked Original posting ↗

Requirements

1 with evidence8 unclear or unstated
Remote policy
onsite
“Provider workplace type: onsite”
From employer posting metadata
Employment type
FullTime
9 fields not stated in this posting
Employer sponsorship
Not specified
Geographic scope
Not specified
Degree requirement
Not specified
Security clearance
Not mentioned
Timezone / hours
Not specified
Citizenship requirement
Not mentioned
Minimum experience (years)
Not specified
Work authorization
Not specified
Compensation
Not specified

These details were not stated in the tracked posting. Confirm with the employer.

READ IT IN THE EMPLOYER’S OWN WORDS

Original job description

Reading view uses normalized posting text so exact evidence excerpts can be highlighted.

Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth-seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code. Software Engineer, RL Data About the Role
Read full descriptionShow less description
The data behind a model shapes it more than almost anything else. On the RL Data team at SpaceXAI, you decide what that data is for our agents: which problems they practice, what world they practice in, and how they're judged. You'll take a weakness, like an agent that gives up on hard bugs or misuses a calendar API, and turn it into training data that fixes it, then show the next model is measurably better. You form hypotheses about why data is helping or misleading the model, build the systems to test them, run ablations, and read the rollouts to find the bug, shortcut or mismatch behind a result. Every flaw you catch, or miss, shows up in what the next Grok models learn. What you’ll work on Turning a capability gap into thousands of verifiable tasks — for example, planting subtle bugs deep in a real project's dependencies for the agent to root-cause. Building environments that behave like production: real codebases with their real dependencies, and simulations of apps like email, calendar, and docs that match the real ones down to search, errors, and pagination. Designing graders for open-ended work that separate good solutions from bad without penalizing valid alternatives or rewarding shortcuts. Building automated checks that catch reward hacking, leaked answers, broken environments, and paths the real product wouldn't allow, before data reaches training. Scaling from a thousand hand-checked tasks to millions, with filters and judges you can trust in place of a person reading each one You may be a fit if You have strong software engineering fundamentals, and you've built non-trivial systems in Python: data pipelines, test or eval infrastructure, sandboxes, or backend services. You have taste for what makes an environment trustworthy: faithful enough that skills transfer, strict enough that shortcuts fail, and simple enough to debug when a result looks wrong. You are careful and systematic — understanding both aggregate metrics and close reading of raw outputs. You enjoy turning messy, open-ended problems into repeatable, high-quality data production systems. RL or ML experience is a plus but not required. We welcome strong engineers who want to do research on what makes models better. Applying If there appears to be a fit, we'll reach out to schedule 2-3 short technicals. After, we'll schedule an onsite in our office, where you'll work on a small project, discuss ideas, and meet the team.
Original formatting and links

Our mission is to automate coding. The first step in our journey is to build the best tool for professional programmers, using a combination of inventive research, design, and engineering. Our organization is very flat, and our team is small and talent dense. We particularly like people who are truth-seeking, passionate, and creative. We enjoy spirited debate, crazy ideas, and shipping code.

Software Engineer, RL Data

About the Role

The data behind a model shapes it more than almost anything else. On the RL Data team at SpaceXAI, you decide what that data is for our agents: which problems they practice, what world they practice in, and how they're judged. You'll take a weakness, like an agent that gives up on hard bugs or misuses a calendar API, and turn it into training data that fixes it, then show the next model is measurably better.

You form hypotheses about why data is helping or misleading the model, build the systems to test them, run ablations, and read the rollouts to find the bug, shortcut or mismatch behind a result. Every flaw you catch, or miss, shows up in what the next Grok models learn.

What you’ll work on

  • Turning a capability gap into thousands of verifiable tasks — for example, planting subtle bugs deep in a real project's dependencies for the agent to root-cause.

  • Building environments that behave like production: real codebases with their real dependencies, and simulations of apps like email, calendar, and docs that match the real ones down to search, errors, and pagination.

  • Designing graders for open-ended work that separate good solutions from bad without penalizing valid alternatives or rewarding shortcuts.

  • Building automated checks that catch reward hacking, leaked answers, broken environments, and paths the real product wouldn't allow, before data reaches training.

  • Scaling from a thousand hand-checked tasks to millions, with filters and judges you can trust in place of a person reading each one

You may be a fit if

  • You have strong software engineering fundamentals, and you've built non-trivial systems in Python: data pipelines, test or eval infrastructure, sandboxes, or backend services.

  • You have taste for what makes an environment trustworthy: faithful enough that skills transfer, strict enough that shortcuts fail, and simple enough to debug when a result looks wrong.

  • You are careful and systematic — understanding both aggregate metrics and close reading of raw outputs.

  • You enjoy turning messy, open-ended problems into repeatable, high-quality data production systems.

  • RL or ML experience is a plus but not required. We welcome strong engineers who want to do research on what makes models better.

Applying

If there appears to be a fit, we'll reach out to schedule 2-3 short technicals. After, we'll schedule an onsite in our office, where you'll work on a small project, discuss ideas, and meet the team.

Similar roles

All cursor jobs →

Matched by role category. Review each posting’s requirements before applying.

THE JOB ELIGIBILITY CHECKER

Check a job