← All roles

Agentic Native Software Engineer

Earlier-career or category-specialist who has spent the last 18 months in agentic systems and thinks natively in tools, plans, and reflection loops. Brings agent-first instincts to product surfaces.

Indicative comp$150K – $220K base (US, mid–senior)

Ranges are indicative US base salary at senior level. Actual offers depend on company stage, equity, and candidate strength.

What this role actually owns

  • Design product surfaces around what the agent can do, not what an existing UI looks like.
  • Implement the loop — planning, tool use, reflection, escalation.
  • Make tool calls feel like first-class UI, not debug output.
  • Iterate fast on prompt and tool design with eval feedback.
  • Push back when the team is bolting an agent onto a workflow that doesn't need one.

What we screen for

  • 3+ years engineering, with the last year focused on agentic systems.
  • Has shipped an app where the agent is the primary interaction model.
  • Strong product instincts — can explain why a particular UI choice helped or hurt.
  • Comfortable iterating prompts, tools, and UX in tandem.
  • Bonus: has open-sourced an agent or tool that other engineers use.

Sample job description

A starting point you can paste into your ATS and adjust. The exact wording matters less than the rubric — the bullets above are what we'll calibrate against during search.

Agentic Native Software Engineer

Builds applications where the agent is the product, not a feature — the kind of software that doesn't make sense in a pre-agent world.

You'll own:

  • Design product surfaces around what the agent can do, not what an existing UI looks like.
  • Implement the loop — planning, tool use, reflection, escalation.
  • Make tool calls feel like first-class UI, not debug output.
  • Iterate fast on prompt and tool design with eval feedback.

We're looking for:

  • 3+ years engineering, with the last year focused on agentic systems.
  • Has shipped an app where the agent is the primary interaction model.
  • Strong product instincts — can explain why a particular UI choice helped or hurt.
  • Comfortable iterating prompts, tools, and UX in tandem.
  • Bonus: has open-sourced an agent or tool that other engineers use.