Warp: We're Building the Platform for Agentic Development Warp began with the vision of reimagining one of the fundamental dev tools — the terminal — to make it more usable and powerful for all developers. As AI has advanced, Warp has evolved beyond its terminal roots into a full agentic development environment: a workbench for dispatching agents to code, deploy, and debug production software. Today, we have two products: Warp, the agentic development environment born out of the terminal, and Oz, our orchestration platform for running hundreds of cloud agents in parallel.

With both products, we’re creating the scaffolding for developers to build their own workflows for working with agents. In Warp, seamlessly switch between running commands, launching agents, and iterating on code with agents— eliminating the need to jump between a terminal and an IDE. It all works with our built-in SOTA agent or top agents like Claude Code, Codex, Gemini CLI, and OpenCode.

In Oz, build custom agents that are triggered programmatically, tracked centrally, and are shared across full teams to run agents across organizations without compromising security or reliability. Continue cloud agent runs that were triggered by Oz locally in Warp or on the web with one click. With over 750k active developers at companies including Docker, Ramp, Peloton, and over half of the Fortune 500 and revenue that grew over 44x last year, Warp is one of the fastest-growing startups in the AI development space.

Our mission has remained the same even as AI has advanced: to empower developers to ship better software more quickly, freeing them to focus on the creative and rewarding aspects of their work. If you want to help define what development looks like in the agentic era at a company where your work reaches hundreds of thousands of engineers every day, we'd love to have you. Why this role?

Warp is scaling its enterprise motion around Oz Cloud Agents — cloud-connected background agents that run from events, schedules, or integrations, giving teams scalable automation with shared observability. As enterprises adopt Oz, they need hands-on technical guidance to deploy production agents — configuring environments, designing agent workflows, setting up self-hosted infrastructure, and iterating on prompts and skills. We're hiring an Implementation Engineer to be the dedicated technical lead for these engagements.

This person will run our structured Implementation Support program, working directly with customer engineering teams from use case selection through production deployment. You'll sit at the intersection of engineering and enterprise GTM; building alongside customers, not just advising. You'll architect agent workflows, configure Docker environments, write skills and prompts, debug integrations, and guide self-hosted deployments.

You'll also work closely with Product and Engineering to translate field learnings into product improvements, shaping the platform based on what you see in the field. As an Implementation Engineer, you will... Lead implementation engagements end-to-end.

Requirements

gathering, use case selection, success criteria definition) through weekly implementation sessions to wrap-up (outcome review, ROI validation, expansion planning). Architect agent workflows with customers. Help enterprise teams design agent architectures for their specific use cases — selecting agent triggers, configuring sandboxed environments, and structuring multi-step agent workflows.

Build alongside customers. Write and iterate on agent prompts, skills, and configurations. Set up environments, secrets, MCP servers, and integrations.

Debug agent runs using session sharing and observability tools. Guide self-hosted deployments. For enterprises running agents on their own infrastructure, help configure self-hosted workers, Docker daemon connectivity, private registries, and task routing.