Why me.
I run delivery for ten vendor teams on a program with contracted scope and a launch date that does not move. I built the board those teams plan from. This role is the same job from the other side of the table.
What the posting asks, and what I have done
| The posting asks for | What I have done |
|---|---|
| Complex enterprise deployments with multiple teams and partners | Release Train Engineer on a tolling modernization program: ten workstreams, each with its own vendor or contractor team, onshore, offshore and in Europe, across five ten-week increments. Before that, two streaming apps on five platforms at A+E Networks, and about ten teams in India and California at Eptura. Case study |
| Scope through launch, with accountability for commitments | The first increment closed with every committed requirement accepted, and I ran the two-day close-out roadshow for the client. At a publicly traded retailer I ran readiness checkpoints and go or no-go decisions under SOX, and the go-live landed on time. At Meta I supported the embedded voice in the Ray-Ban Stories glasses and ran final QA. It shipped on the public launch date. |
| Plans with milestones, owners, dependencies and success measures | I interviewed every workstream lead before planning and turned the answers into one script that every lead plans from. The planning board shows what each increment holds, what it inherits and what it hands on. Every metric is declared with the query that will produce it. |
| A clear view of delivery health | The board never shows a number it cannot source, and a gate with no data shows a dash, never green. The prototype on this site carries the same two rules. Prototype |
| Technical fluency with AI systems, APIs and security dependencies | Delivery lead at a stealth AI startup for teams fine-tuning Gemini, ChatGPT and Claude models on customer data. I co-built the requirements app my current program works in, including its role-based access, and it fails closed without a key. I also run local models on real coding jobs against hidden tests. Case study |
| Judgment under ambiguity; finding material risks early | On my board, ambiguity is shown and never guessed, and machine suggestions stay marked as proposals until a person confirms them. I check the agents’ numbers: a reported 682 tests turned out to be 384. |
| Trust with customers and executives, across teams outside my reporting line | Each of the ten teams belongs to its own vendor or contractor. I lead them through the plan and the Scrum of Scrums I rebuilt, and I run a retrospective with all leads at the end of each increment. Earlier, eight years on agency accounts for American Express, Citi and Toyota, from pitch to launch. |
| Repeatable delivery methods | One planning script for ten vendors. Reusable AI skills that produce a meeting readout from a transcript and refresh the delivery report numbers from exports. The first increment’s delivery report came from the board. |
The gap, plainly
I have led delivery from the client and vendor-coordination side, not from inside a model provider. And I have never been accountable for a consumption or revenue number.
The nearest I have come to the commercial side is agency work: estimates, statements of work, staffing plans and change orders. That is pricing a project, not owning a forecast. I would learn the second from the account teams, and I would not pretend to it in a review.
My titles have been Scrum Master, Agile Coach and Release Train Engineer. What I bring is the plan, the gates and the honest board, and a habit of reading everything first. This site is that habit, done in a day.