You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Applied Intuition

Senior Software Engineer - AI Developer Productivity

  • Office
  • 6+ years

Salary

$195,000 - 265,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company builds the digital infrastructure that gives intelligence to moving machines, a field it calls physical AI. Founded in 2017 and valued at $15 billion, it is based in Silicon Valley.

Its tools and infrastructure, operating systems, and autonomy products serve the automotive, defense, trucking, construction, mining, and agriculture industries. Eighteen of the top 20 global automakers and the United States military and its allies use its solutions.

Headquarters are in Sunnyvale, California. Offices are in Washington, D.C.; San Diego; Ft. Walton Beach, Florida; Ann Arbor, Michigan; London; Stuttgart; Munich; Stockholm; Bangalore; Seoul; and Tokyo.

The AI Developer Productivity team keeps the company's engineers moving quickly and with confidence. As the company grows and AI changes how software gets written, developer speed matters more, and this role affects both short-term and long-term goals.

The team is rebuilding the software development lifecycle to capture the productivity gains of AI coding while keeping quality, scalability, and reliability intact. The work covers code review bots, agents that work with engineers in Slack, and orchestration systems for long-running work across the codebase. The company encourages engineers to own technical and product decisions, talk directly with users for feedback, and help shape a thoughtful, dynamic team culture.

Responsibilities

  • Build and improve the agent tools engineers use daily, including design and code review bots, agentic production testing systems, and coding agent harnesses.
  • Design shared agent building blocks for the whole company, such as permissioning systems, sandbox infrastructure, harness integrations, and agent orchestration frameworks.
  • Work with all engineering teams to improve code quality, testability, and release processes.
  • Take ownership of your own areas of expertise and shape product decisions from your first day.
  • Set best practices and standards that give developers a clear, well-supported path to follow.

Requirements

  • Bachelor's degree in Computer Science, Software Engineering, or an equivalent field.
  • 5+ years building high-quality software products and tools, with a focus on quality, reliability, and developer ergonomics in technically demanding domains.
  • You own products from the underlying infrastructure up to engagement metrics.
  • Hands-on experience building with LLMs and agents, including tool use, agent harnesses, context management, and evals, and a clear sense of where they break down.
  • You care deeply about code quality, set an example with your own work, and raise the quality bar across an organization.
  • You take a first-principles approach, have strong fundamentals, and build reliable core systems rather than demos.
  • You are driven, take initiative, and work well in a fast-moving environment.
  • Experience building agent infrastructure such as sandboxes, agent runtimes, orchestration systems, or coding agent extensions.
  • Experience with isolation and virtualization technologies (containers, Firecracker, gVisor, Kata Containers) and Kubernetes at scale.
  • Experience with identity, authorization, and credential systems such as OAuth, workload identity, and secrets management.
  • Experience with retrieval, knowledge management, or memory systems for LLMs.
  • Experience with build and CI at monorepo scale, such as Bazel, remote caching and execution, or Buildkite.
  • Experience in automotive, autonomy, robotics, or related industries.
  • Experience deploying software on public clouds (e.g. AWS, GCP) or on-premise clusters.
  • Deep knowledge of Linux and the software ecosystem around it.
  • You are encouraged to apply even if your experience does not match every qualification in the posting, as you may suit this role or another one.

Conditions

Full-time employees are expected to work from the office 5 days a week, though occasional remote work and flexible hours for family needs are allowed.

The in-office expectation does not apply to contractor positions.

Reasonable accommodations are available to US-based applicants who are disabled veterans or have disabilities or medical conditions, and you need not disclose your condition to ask for one.

Where you’d work

From the office, 4 or more days a week in the office

About the company

Applied Intuition

Office in Sunnyvale, United States

Also hiring in United States, Stuttgart, Germany, FL, United States and 1 more place

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 22 checks run
  • 0 red flags

Still hiring?

14 checks

No red flags

How crowded?

8 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment
Tech stack
  • AWS
  • Kubernetes
  • Linux
  • LLMs
Seniority
Senior
Type
Full-time
Specialty
Backend
Region
United States
Pay period
Annual
Show 6 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Senior
Experience
5+ years
Tech stack
  • AWS
  • Kubernetes
  • Linux
  • LLMs

Location

Work model
Office
Region
United States
Office
  • Sunnyvale, United States
Days in the office
4 or more days

Compensation

Salary
$195,000 - 265,000 / year
Pay period
Annual

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason