AI Engineer

About Ditto:

Ditto is redefining how data moves at the edge. Our mission is to make it seamless for developers to build resilient, real-time applications, regardless of network conditions. Whether you're in a stadium, airplane, or remote military base, Ditto's peer-to-peer sync engine ensures devices stay connected and data stays consistent, even without internet. With more than $145 million in funding and trusted by organizations like Chick-fil-A, Delta Airlines, and the U.S. military, Ditto powers mission-critical experiences across aviation, retail, travel, hospitality, defense, and more.

As a globally distributed, fast-growing startup, we’re committed to building a diverse and inclusive team that reflects the wide range of perspectives needed to solve the world’s hardest connectivity problems.

As an AI Engineer at Ditto, you build the system that builds our software. We are moving engineering from handcraft — every change written, tested, and shipped by a person tending it one at a time — to an operated platform where agents do the work and engineers tend the agents. You will help build Symphony: the brief runtime that executes agent teams, the typed tool surface those agents reach the host through, the telemetry that makes every run measurable, and the evaluation loop that turns a bad output into a better brief instead of a hand-patched diff.

This is deliberately a blend of AI engineering and developer tooling, because at this layer they are the same job. Getting an agent to reliably build, test, and ship an iOS change is part prompt and context design, part sandboxing and process supervision, part CI and release plumbing, and entirely a measurement problem. Your users are Ditto's own engineers, and your product is the thing they run every day — so you will care as much about a clear error message and a fast local loop as you do about token cost per completed task.

This role suits someone comfortable in ambiguity, opinionated about evaluation over intuition, and happy to own a system end to end.

• Build the agent execution runtime: Design and ship the layer that compiles a brief into a running team of agents — topology and handoffs, deterministic gates, the shared message bus, session lifecycle, and the recovery behavior that keeps a long run from losing its work.

• Design the tool surface agents work through: Replace "here is a shell, please be careful" with typed, versioned toolpacks backed by reviewed repository recipes — sandboxed execution boundaries, lease handling, process-tree ownership, and MCP servers that expose our internal systems to agents safely.

• Make quality measurable, then improve it: Build the evals, benchmarks, and metric sets that score a run; instrument the system with per-phase timing, structured error taxonomies, and cost attribution; and use that signal to tune prompts, context, and topology rather than guessing.

• Own the model substrate as a swappable input: Bind briefs to capability classes instead of vendor model names, work with routing and inference infrastructure across hosted and on-prem serving, and tune context, caching, and model selection against real cost, latency, and accuracy data.

• Partner with service teams and raise the bar: Work directly with Ditto's engineering teams to turn their workflows into briefs they trust, establish the patterns others compose from, and mentor engineers as agentic development becomes the default path rather than the experiment.

• 5+ years of professional software engineering experience
  , including meaningful time building and operating LLM-backed systems in production — not prototypes or demos, but something real people depended on.

• Hands-on depth with agentic systems
  : tool and function calling, multi-agent orchestration, context and prompt engineering, structured output, and a practical understanding of where these systems fail and why.

• Strong developer-tooling instincts from building the things engineers depend on — CLIs, build systems, CI/CD, internal platforms — with the empathy for the daily loop that comes from having been the person on call for it.

• A rigorous approach to evaluation. You have…