Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta, delivered through small, embedded teams working inside each client's environment. We are hiring a Head of Delivery to lead our IT Delivery team — the people carrying the Deployment Strategist role on every engagement — and to ensure the successful, continuous delivery of complex software and AI-driven initiatives across every active client at once. The role is fully remote across Latin America.
This is a hands-on, results-oriented seat, not an oversight one. Azumo delivers through Deployment Strategists and Forward Deployed Engineers working without a handoff between them, and Head of Delivery is accountable for that system holding under real pressure: guiding the team, removing impediments, and owning delivery through the full project lifecycle, engagement after engagement.
Where this role sits
Every Azumo engagement is delivered by two roles held in one conversation: a Deployment Strategist, who owns the problem and whether the result is accepted,
and one or more Forward Deployed Engineers, who own the system and whether it works. Neither one produces a document for the other to execute — that handoff is exactly what the model exists to remove. Head of Delivery owns the model itself: whether it's staffed correctly on every engagement, whether it's actually being run the way it's designed, and whether the people carrying it have what they need to carry it well.
One question places the boundary: when an engagement goes sideways, did the DS and FDE make a bad call inside the model, or did the model quietly revert to something else — a requirements document, a status report, a third role absorbing the seam? The first is a judgment call, and it belongs to the DS and FDE. The second is the model breaking down, and it's this role's to catch before it becomes how the practice actually operates.
Head of Delivery doesn't run individual engagements. It runs the system
📌 Head of Delivery (México)
🏢 Azumo
📍 México