Delivery Lead

The Delivery Lead owns the build. You run delivery within the pod you are deployed to: sprint output, release quality, blockers, and the handshake between engineering and in-country implementation teams. You are technical and fast. You can read a PR, challenge an estimate, and step into the codebase when a blocker demands it, but your primary job is that the pod ships. You work alongside a solution architect who owns design decisions. The division is simple: they own what gets built and how it is structured; you own that it actually ships on time at quality. In practice, you will both get your hands dirty across the line, and that is expected. What matters is that delivery has a single accountable owner: you.
Responsibilities:
Own delivery end to end within your deployed pod: sprint planning discipline, release criteria, deployment checklists, and what ships versus what waits.
Stay technically credible: review PRs meaningfully, challenge estimates with evidence, and write code when a blocker or spike demands it. A release you approve is a release you stand behind.
Run the delivery cadence: standups that surface real blockers, sprint reviews that measure output honestly, and retrospectives that change behavior.
Triage and resolve blockers fast, whether technical, dependency-based, or people-based. Escalate to the head of product and delivery only what genuinely needs escalation, with a proposed answer attached.
Coordinate delivery with remote implementation teams: field escalations, deployment coordination, and keeping in-country implementation aligned with what engineering shipped.
Report delivery status upward accurately and concisely: no filtering, no spin, and no surprises. Weekly written status the head of product and delivery can forward without editing.
Mentor engineers continuously through code review, pairing, and honest feedback on estimation and quality. Raising the team's delivery discipline is part of the job, not adjacent to it.
Work jointly with the Solution Architect on technical hiring: you assess delivery instincts and code quality; they assess design depth.
Requirements:
8-12 years of software engineering experience with a clear record of shipping. You have owned releases, not just contributed to them.
Technical fluency in our stack or close to it: NestJS/TypeScript, React, PostgreSQL, Docker. You can read code critically and contribute when needed, even if delivery leadership is where you spend most of your time.
Proven delivery ownership across at least one multi-engineer team: you set the cadence, held the bar, and shipped against real client commitments.
Fast, structured communication: written status updates, blocker escalations, and client-safe delivery summaries that need no rewriting.
Experience working with remote or cross-geography teams: time zones, low-bandwidth communication, and field constraints do not slow you down.
Mature judgment on quality versus speed trade-offs: you know when to hold a release and when holding it costs more than shipping it.
Comfort operating without formal people's authority: you drive delivery through competence and clarity, not organizational structure.

Experience
8-12 yrs