Head of Delivery - Latin America - Remote

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 that lets engagements run themselves: staffing the DS seat, converting PMs, BAs, and QAs into it, watching for the failure modes before they turn into habits, and reporting the health of the whole delivery portfolio as a practice — not engagement by engagement.

What you will own

Portfolio health. Every active engagement's scope, schedule, risk, and client-satisfaction signal, rolled up into one honest picture for senior management and stakeholders — not smoothed for the report, and never later than the client already knows it.

Staffing the model. Make sure every engagement that needs a Deployment Strategist has one, and that the seat is never left running on borrowed time from someone else's day job.

Guiding and coaching the delivery team. Coach PMs, BAs, and QAs into the DS role directly — selection against the three real gaps (domain depth, commercial nerve, client-facing initiative), paired with a strong FDE — and watch for the model quietly reverting: a requirements document reappearing, an FDE who's stopped talking to the client, acceptance turning into a testing phase.

Removing impediments. The blockers a DS or FDE can't clear alone — access, a missing counterpart, a decision stuck above the engagement — get raised to you and cleared, not logged on a list that ages.

Delivery discipline, applied not just championed. Agile is the operating rhythm across every engagement, not a slide; you set how it runs and catch where a team has quietly drifted from it under deadline pressure.

Billing, time, and budget. Accurate billing and time tracking across the portfolio, and the budget health of every active engagement — the real numbers, not the version that gets smoothed before it reaches you.

How we work

Our engineers build with AI every day — Claude Code, Codex, and similar tools are the standard toolchain, not an experiment — and every client codebase runs an automated security, cost, and architecture audit from day one, graded by severity down to the file a