Back to jobs

Applied AI Engineer, Agent Systems

San Francisco · San Francisco, California, United States

Actively hiring, first seen by us 3 days ago
Pay
$215,000–235,000/year — pay source
Compensation & logistics Salary range is $215k-235k per year, with meaningful early-stage equity Standard benefits
Read the full posting
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting

What you’ll work on

Full posting
  • Build client context layer and retrieval, measured for real usefulness

  • Build the product's agent systems as versioned, testable skill and instruction files

  • Build scheduled and event-driven agent work that is durable, idempotent, and observable

  • Own one insight pipeline rendering to chat, email, PDF, and API

  • Ensure client-set policies execute reliably, safe to re-run, and only after approvals

From the employer’s posting
Client context layer and retrieval. Built and measured, not just assumed to work.
The product's agent systems — skill and instruction files as versioned, testable, reviewable artifacts
the scheduled/event-driven work built on them, durable, idempotent, and observable
One insight pipeline rendering to chat, email, PDF, and API.
you own making sure it executes reliably every time: safe to re-run, fully trackable, and only after the approvals and deployment steps the client has set up.

About The Electric Plant

is building a new category of plant and tree intelligence.

In the employer’s words · Read in context · Company website ↗

Apply at The Electric Plant

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
5
Last seen by us
Nov 22, 2026
Employer says posted
Sep 14, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 3

Similar jobs usually come down between day 1 and day 15.

From 1,371 similar postings that came down. Coming down is not always a hire.

The Electric Plant is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About The Electric Plant Co.

The Electric Plant Co. is building a new category of plant and tree intelligence. Our IoT hardware measures the electrical signals in plants and trees, paired with environmental data, and our foundation model, Bombadil, decodes those signals into real-time insights about plant health, growth, and stress. We're a small, fast-moving company in San Francisco working at the intersection of biology, hardware, AI, and IoT. Bombadil can decode a plant’s physiological responses to stress — the layer that turns that into something a grower acts on doesn't exist yet, and that's what this role builds.

The Role

You'll build the application layer that sits between our foundation model and the people who use it: the client's context layer, insight and policy cards, learning loops, agents, and scheduled work. You'll start embedded in the field with our Deployment Lead on our first real customer, shipping things a grower actually uses to run their orchard. From month six onward, you'll convert what worked into the reusable protocols and tools that make every deployment after the first faster to stand up.

This is a senior, individually-contributing role with no direct reports. You'll report to our Director of Engineering, with a direct line to our CEO on what the system could do next.

You'll work closely with the engineer who owns our deterministic data plane (ingest, fleet, telemetry), the team that owns our foundation model, and the person who owns the client relationship and translates what growers need into what you build.

What You'll Own

  • Client context layer and retrieval. Built and measured, not just assumed to work.

  • The tool schema exposing our platform's data and insights, including uncertainty in the return payload.

  • The product's agent systems — skill and instruction files as versioned, testable, reviewable artifacts, and the scheduled/event-driven work built on them, durable, idempotent, and observable.

  • One insight pipeline rendering to chat, email, PDF, and API.

  • The context schema and card structure that make Platform's multi-tenant isolation and client IP protections possible — including how clients' data and the insights engineered from it are protected.

  • Actuation. When the system carries a client-set policy into their systems — an irrigation setpoint, a crew instruction - you own making sure it executes reliably every time: safe to re-run, fully trackable, and only after the approvals and deployment steps the client has set up..

  • Eval suites, trace capture, drift monitoring, and per-client cost accounting.

What We're Looking For

  • Has built and measured production AI retrieval and context assembly, with quantification of the system’s usefulness, not demo impressions.

  • Consistently pushes repeatable work into deterministic code and spends model calls only where judgment is genuinely required.

  • Has shipped multi-tenant isolation in production: tenant-scoped data and indexes, per-client credential scoping, deletion that actually deletes.

  • Has built a config or skill system that a non-engineer colleague used daily and modified without you.

  • Has operated an agent system in production, not a prototype, with a real story about silent drift, a cost blowup, or a cron that double-fired.

  • Has built durable, idempotent, observable scheduled or event-driven agent work.

  • Has built eval suites, trace capture, or drift monitoring, and can speak to where ground truth came from and how often it arrived.

  • Likely has a full-stack or front-end web/application engineering background who made a deliberate turn toward agentic systems, rather than a long-tenured backend or data engineer moving into this space for the first time. Total years matter less than this shape.

Strong plus

  • Integration grit against client and legacy systems: enterprise APIs, CSV over SFTP, email deliverability.

What This Isn't

This isn't a role for someone who wants a settled spec and a quiet backlog. Requirements will arrive from an orchard, mid-season, and be wrong. It's also not a research role — you'll consume and expose what the model does, not train it — and not an infrastructure role, since the data plane underneath you is someone else's deterministic domain. If you're excited by the orchestration toolkit itself more than by what it takes to get something working in a grower's hands, this isn't the fit. If you want to build the layer that makes a decoded plant signal into something a business actually acts on, and to do it first in the field and then in code that outlasts the first customer, we'd like to talk.

Compensation & logistics

  • Salary range is $215k-235k per year, with meaningful early-stage equity

  • Standard benefits

  • Full-time, in-person at our Presidio office in San Francisco

  • Start date: ASAP

We are an equal opportunity employer and all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability status, protected veteran status, or any other characteristic protected by applicable law.

Demand for AI Engineer roles

New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.

Weekly new AI Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 78, the most 803, and the latest week had 438.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay
Compensation & logistics Salary range is $215k-235k per year, with meaningful early-stage equity Standard benefits
Location & working pattern

San Francisco, California, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.