Agent Systems Engineer at Clera
San Francisco, CA
$180,000–$250,000from the description
Jul 18, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
An early engineering hire on the Research team, this role centers on building and owning the core infrastructure behind agentic applications — covering multi-agent architectures, orchestration layers, behavioral and persona models, and evaluation frameworks. The work involves turning research prototypes into reliable, observable production systems, with a strong emphasis on generating actionable product insights from agent outputs. Suits an experienced distributed-systems engineer with a track record of shipping agentic LLM systems in production.
Senior level · 5+ years · San Francisco-Oakland-Berkeley, CA · Full-time
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 1,450 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 370–1,900
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $190,744 (middle half $167,095–$224,501). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The title 'Member of Technical Staff' carries no explicit seniority level, so the title states no level; the 5+ years overall and 2+ years agentic LLM requirements support a Senior band.
The role is described as hybrid/on-site in San Francisco; a London-based option is mentioned but only for candidates with 'regular San Francisco availability,' so the primary CBSA is SF.
Visa sponsorship is explicitly unavailable; candidates must be US work-authorized.
15-2051 (Data Scientists) is noted as a runner-up because the role involves ML systems, behavioral modeling, and evaluation frameworks — but the dominant day-to-day work is building production software infrastructure (distributed systems, orchestration, agent platforms), pointing to 15-1252.
'Async programming' and 'Pydantic' are called out explicitly in the Required section as part of 'Python mastery'; they are listed as separate skills because the JD treats them as distinct named capabilities.
State machines, orchestration layers, and behavioral modeling appear under the 'Nice to Have' section and are marked preferred accordingly.
Early-stage equity is mentioned but no specific figures are given, so it is not captured in the compensation fields.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): behavioral modeling.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.