Company
ChipAgents
Annual salary
$180k – $350k/yr
Location
San Jose, CA
Listed
37d ago
- Experience:
- 5 to 15 years
- Workplace:
- 5 days in-office in San Jose, CA (relocation support available)
- Equity:
- Competitive equity
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in San Jose, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are hiring Software Engineers to improve the performance, reliability, and efficiency of AI agents for hardware applications. You’ll identify failure modes, design and run evaluations, develop new agent capabilities, and turn successful experiments into production software. You’ll join a sizable, rapidly growing team of software engineers, researchers, hardware experts, customers, and founding and field teams, working across customer discovery, evaluation design, applied research, product development, and deployment for a broad range of hardware-engineering problems.
What you'll do
- Finding where AI agents fail, then designing and running evaluations to improve their performance, reliability and efficiency
- Building new agent capabilities, including tool interfaces, context management, memory and multi-step or multi-agent orchestration
- Digging into traces and experiment results to find bottlenecks, and telling real improvements apart from benchmark noise
- Working with customers and domain experts to understand what they need, then shipping and maintaining fixes from start to finish (within about 3 months)
- Turning successful experiments into well-built, maintainable production software
What you need
- Strong software engineering skills, particularly in Python and TypeScript.
- Familiarity with modern language models, agent systems, and common ML workflows.
- Strong communication skills, customer judgment, and the ability to identify the crux of ambiguous technical problems.
- Self-directed and ambitious, with strong ownership, creativity, and product judgment.
- Strong commitment to customer and business outcomes.
Nice to have
- Interest in EDA, RTL, or hardware-software systems.
Why ChipAgents
Own the software layer that turns ML research into scalable products at the intersection of AI and semiconductors.
Join a fast-growing team working alongside industry veterans, real customers, and real production scale, not a role siloed from product impact.
Shape your own scope across research collaboration, engineering, and customer-facing work based on your strengths and interests.
Common questions
How do I apply for the Software Engineer, Agent Harness & Evaluation (US) role at ChipAgents? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this ChipAgents role pay? +
The listing gives $180k – $350k/yr.
Is this role remote? +
The listing gives the location as San Jose, CA. 5 days in-office in San Jose, CA (relocation support available).
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →