Skip to content

Judgment Labs

Product engineer, Agent

Location
San Francisco, CA, US
Arrangement
On-site
Employment type
Full-time
Posted
13 August 2026 (about a month ago)

Checked 21 days agoApplications go to the employer, never to RoleSprint

About this role

PRODUCT ENGINEER - AGENTS JOB DESCRIPTION

THE ROLE

Judgment is the learning infrastructure for AI agents. Agents in production don't improve from prompts alone. They improve from experience: the tasks they attempt, the mistakes they make, the edge cases they hit. Here's how it works:

1. We ingest everything your agents do in production: traces, tool calls, decisions, outcomes

2. Judgment turns that raw experience into structured signals: failure modes, behaviors, rubrics, evals

3. Teams close the loop, shipping agent improvements validated against real production evidence

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 WILL ACCOMPLISH

- 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 YOU'LL BRING

- 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

Work location

  • San Francisco, CA, US

Related jobs

Ready to make a decision?

This role is either worth your time or it isn’t.

Analyze the posting against your experience, see the gaps clearly, and build the right materials only if the opportunity makes sense.

Nothing is submitted automatically. You choose what happens next.

About this listing

Published on Ashby under the board identifier Judgmentlabs, which is the name the employer’s own job board carries. RoleSprint has not verified the company’s registered or trading name, so it is shown exactly as published rather than tidied up.

RoleSprint is not the employer and not a recruiter. Applications are made on the employer’s own site and never reach us; what RoleSprint does is help you decide whether a role is worth your time and prepare for it if it is.

Published 13 August 2026, last checked 21 days ago. A posting stops being advertised here 90 days after the employer published it, and one the employer takes down is marked closed rather than quietly removed.

More searches like this one

Browse all current openings

No credit card requiredStart free