VP of Delivery

Akka • Toronto, ON

3d • Remote

About The Position

Akka builds the platform that enterprises use to develop, deploy, and operate agentic AI systems. Our customers run mission-critical workloads on top of Akka — many of them in regulated industries (financial services, healthcare, public sector, defense-adjacent) where the cost of an outage, a data leak, or a botched upgrade is measured in regulatory exposure, not just churn. They are not buying SaaS. They are buying a managed runtime they can stake their business on. We extend resilience guarantees and 99.9999% availability commitments, and we deliver those through a hosted managed service.

The VP of Delivery owns the end-to-end customer experience: proof of concepts, onboarding, production operations, reliability, support, and the human relationships that turn a first deployment into a long-term partnership. This is not a SaaS-style "customer success" role — it is a delivery leadership role for a high-reliability managed service. The person in this seat is accountable for whether our customers' agentic AI workloads stay up, stay secure, and stay aligned with the commitments we made to them.

Requirements

• You own the customer's success as if it were your own business.
• Customer-obsessed, not customer-pleasing. You will tell a customer "no" when "yes" would set them up to fail. You will tell us "we shipped them a problem" when we did.
• Operator's instinct. You are drawn to the dashboard, the runbook, the postmortem. You believe reliability is a product feature and you treat it like one.
• Orchestrating us internally for the customer’s best. You make sure we together, irrespective of formal organization, use our strengths to make the customer successful.
• Comfortable with regulated reality. You don't bristle at change advisory boards, evidence collection, or auditor questions. You see them as part of the job and you've made them efficient before.
• Bias toward systems over heroics. When something breaks twice, you fix the system, not just the incident. You build delivery orgs that don't depend on any one person being awake.
• Builder, not administrator. Akka is still small enough that the VP of Delivery writes the playbook, doesn't inherit it. You are energized by that, not daunted.
• Has run a high-reliability managed service — meaning real production workloads, real on-call, real SLAs with teeth — for regulated or security-sensitive customers. Pure multi-tenant SaaS experience is not the same thing and is not sufficient on its own.
• Background that includes time as an SRE, platform engineer, or solutions architect — not just management.
• Has led delivery, customer engineering, TAM, or managed-services orgs at a company selling to regulated enterprises (financial services, healthcare, public sector, critical infrastructure, or similar).
• Has worked across multiple compliance regimes that customers care about — SOC 2, ISO 27001, HIPAA, FedRAMP, DORA, EU AI Act, or equivalents. We don't require deep expertise in any single one; we do require having operated in enough of them to know how delivery work shows up in a customer's audit and how our product helps or hurts their compliance.
• Has built and scaled a delivery organization through a stage transition (e.g., from founder-led delivery to a real org, or from one region to multi-region).
• Our platform integrates tightly with Kubernetes on all hyperscalers. It uses established technologies and complements those with our competence from distributed systems. (GCP, AWS, Azure, K8s, Go, Helm, Kustomize, Crossplane, Java, Scala, Akka Libraries)

Nice To Haves

• Recent, hands-on exposure to AI / agentic systems in production. Our product is an AI runtime; the person leading delivery cannot be learning what an LLM is on the job. "Recent" means within the last ~18 months and on workloads you were accountable for, not workloads you read about.
• Experience with distributed systems, event-driven architectures, or actor-model platforms.
• Exposure to data residency / international transfer regimes (GDPR, UK GDPR, Schrems II realities).

Responsibilities

• Customer outcomes. Every customer's production health, renewal posture, and reference-ability. You know the names of the top accounts, the state of their environments, and the next three things we owe them.
• Reliability as the customer experiences it. SLO commitments to customers, incident response, change management, and the operational rituals that keep customer workloads running. SRE owns platform reliability and Engineering owns building the product; you own how both land for the customer and you push hard on each when the customer experience requires it.
• The delivery org. customer engineers, TAMs, and the operations function that runs the managed service. You hire, develop, and hold the bar for the people who are physically in the room (or on the call) with our customers.
• Customer compliance enablement. Our customers run regulated workloads on Akka under many different regimes; you make sure our product and the way we deliver it actively help them maintain their own compliance posture. The CISO owns Akka's posture; you own translating it into evidence, behavior, and product feedback our customers can stand behind to their own auditors.
• The feedback loop into Product and Engineering. You are the highest-fidelity signal in the company about what our customers actually need next, and you make sure that signal lands.

Benefits

• A transparent, distributed work environment with a strong focus on work-life balance.
• Challenging work that interacts with innovative applications used by millions.
• A collaborative culture that attracts the "brightest minds" in the technology community.

What This Job Offers

• Job Type: Full-time
• Career Level: Director
• Education Level: No Education Listed