judgmentlabs

Member of Technical Staff, Agents

Listed by employer · Checked

Older posting · still listed ·

  • 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 ↗
This is an older posting.

The employer’s posting date is more than 60 days ago. It remained listed at our last successful check; it may be a long-running or evergreen opening. Confirm availability on the original posting before applying.

Browse jobs posted in the past 60 days →

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.

About Judgment Judgment Labs is building the infrastructure for continual learning in long-horizon AI agents. We turn long agent trajectories into clean, structured data for evals, labeling, rubric generation, context engineering, and RL workflows. Instead of only showing teams what happened, Judgment helps decide what matters, what should be learned from, and how that learning should flow back into the agent.
Read full descriptionShow less description
We’ve raised $32M across two rounds led by Lightspeed. The Role You'll build the product experiences that make this loop legible, and you'll build the agents that run it. This is not a role where you implement specs handed down. You'll own problems end-to-end: talking to customers, defining what to build, building it, and iterating until it's great. What You’ll Do Judgment Agent: Shape how the Judgment Agent runs large-scale investigations: parallel investigators working across thousands of production traces, each covering a different dimension (failure modes, tool errors, regressions, drift), merging results into one answer. Verification: Build the platform for verifying agent changes: hosted simulated environments for stateful agent evals, trajectory replay against changed agents, and monitors for unintended behavior changes. Agent investigation interfaces: Design how engineers understand what their agents did and why. Long traces, tool calls, decisions, failures. What does debugging look like when the "program" is a reasoning loop? How do you make a thousand-step trajectory legible in minutes? Swarm UX: A hundred parallel investigations is useless if engineers can't follow them. Design how humans watch a swarm work, redirect investigators that go down the wrong path, and consume findings without reading a hundred reports. The improvement loop: Build the workflows that turn production trajectories into datasets, judges, and regression checks, so the path from "found a problem" to "verified a fix" feels like one motion. The platform underneath: Workspaces, roles, permissions, billing, usage, and limits for teams running many agents across many environments. Judgment everywhere agents are built: An SDK and terminal-first experience so Claude Code, Codex, and OpenCode sessions can summon Judgment as a subagent mid-development. What We’re Looking For Experience building and scaling end-to-end production systems, from data layer to UI. Strong technical problem-solving skills, especially in fast-changing, ambiguous environments. A builder and tinkerer's mindset with high agency - you find creative ways to overcome obstacles and ship. Hands-on experience building with LLMs or agents, or the drive to get there fast. Comfort working directly with customers to understand their needs and solve real-world problems. Excellent communication skills - clear, direct, and persuasive across technical and non-technical audiences. Reinforcement learning, post-training, agents, or machine learning fundamentals. Why Judgment? You’ll work on problems customers actually feel: Engineers talk directly to teams building production agents, see where their systems fail, and turn those failures into product and infrastructure. Small team, high ownership: You will not own a narrow slice. You’ll shape core systems early, ship quickly, and work across product, data, backend, infra, and customer environments. In person in San Francisco: We work together in person because the problems are hard, the product is moving fast, and the feedback loops matter.
Original formatting and links

About Judgment

Judgment Labs is building the infrastructure for continual learning in long-horizon AI agents.

We turn long agent trajectories into clean, structured data for evals, labeling, rubric generation, context engineering, and RL workflows. Instead of only showing teams what happened, Judgment helps decide what matters, what should be learned from, and how that learning should flow back into the agent.

We’ve raised $32M across two rounds led by Lightspeed.

The Role

You'll build the product experiences that make this loop legible, and you'll build the agents that run it. This is not a role where you implement specs handed down. You'll own problems end-to-end: talking to customers, defining what to build, building it, and iterating until it's great.

What You’ll Do

  • Judgment Agent: Shape how the Judgment Agent runs large-scale investigations: parallel investigators working across thousands of production traces, each covering a different dimension (failure modes, tool errors, regressions, drift), merging results into one answer.

  • Verification: Build the platform for verifying agent changes: hosted simulated environments for stateful agent evals, trajectory replay against changed agents, and monitors for unintended behavior changes.

  • Agent investigation interfaces: Design how engineers understand what their agents did and why. Long traces, tool calls, decisions, failures. What does debugging look like when the "program" is a reasoning loop? How do you make a thousand-step trajectory legible in minutes?

  • Swarm UX: A hundred parallel investigations is useless if engineers can't follow them. Design how humans watch a swarm work, redirect investigators that go down the wrong path, and consume findings without reading a hundred reports.

  • The improvement loop: Build the workflows that turn production trajectories into datasets, judges, and regression checks, so the path from "found a problem" to "verified a fix" feels like one motion.

  • The platform underneath: Workspaces, roles, permissions, billing, usage, and limits for teams running many agents across many environments.

  • Judgment everywhere agents are built: An SDK and terminal-first experience so Claude Code, Codex, and OpenCode sessions can summon Judgment as a subagent mid-development.

What We’re Looking For

  • Experience building and scaling end-to-end production systems, from data layer to UI.

  • Strong technical problem-solving skills, especially in fast-changing, ambiguous environments.

  • A builder and tinkerer's mindset with high agency - you find creative ways to overcome obstacles and ship.

  • Hands-on experience building with LLMs or agents, or the drive to get there fast.

  • Comfort working directly with customers to understand their needs and solve real-world problems.

  • Excellent communication skills - clear, direct, and persuasive across technical and non-technical audiences.

  • Reinforcement learning, post-training, agents, or machine learning fundamentals.

Why Judgment?

  • You’ll work on problems customers actually feel: Engineers talk directly to teams building production agents, see where their systems fail, and turn those failures into product and infrastructure.

  • Small team, high ownership: You will not own a narrow slice. You’ll shape core systems early, ship quickly, and work across product, data, backend, infra, and customer environments.

  • In person in San Francisco: We work together in person because the problems are hard, the product is moving fast, and the feedback loops matter.

No similar roles found yet — browse all judgmentlabs jobs.

THE JOB ELIGIBILITY CHECKER

Check a job