Summary
What you’ll impact
The Senior Full-Stack Engineer designs and implements the application layer that connects the AI foundation model to growers’ workflows for plant health insights. They build client context retrieval, multi‑tenant isolation, configurable agent systems, and event‑driven jobs with web and backend tech, ensuring durability and observability. Deliverables include an insight pipeline via chat, email, PDF and API, plus eval suites, trace capture, drift monitoring, and cost accounting. Collaboration with data‑plane, model, and client teams turns orchard needs into repeatable production features.
Responsibilities
What you'll do
- 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.
Requirements
What you’ll bring
- 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.