The same model at work: a major airline's maintenance technology
At a major airline's maintenance-technology organization I sit between architecture and delivery with no direct reports, and over the last year I turned that seat into an AI-assisted way of working that colleagues across the org adopted, from engineers to directors.
I sit between architecture and delivery, and I stay involved across the whole lifecycle.
- Before a decision: I establish what's actually true. That covers the code, data flows, runtime behavior, ownership and dependencies.
- During design: I turn loose program goals into decisions teams can build, with contracts, failure paths, ownership and validation gates.
- During build: I write code and infrastructure myself, review other engineers' changes (usually as the only reviewer), and create well-scoped work for others.
- During release and incidents: I give go/no-go recommendations, write option briefs for leadership, join overnight changes and bridges, and do root-cause analysis.
- After: I capture what we learned so the next person, or the next agent, starts ahead.
I have no direct reports. I lead through evidence, technical judgment, tools that make other people faster, and decisions framed clearly enough for leadership to act on. The common thread: I make other people faster and safer, and I stay with the work until it lands.
- I ship pull requests of my own across repositories spanning the maintenance portfolio.[SYS]
- I review changes for engineers across the organization, usually as the sole reviewer.[SYS]
- The team toolkit holds shared agent skills and application profiles, with engineers and leaders contributing changes.[SYS]
- The HR-migration assessment covered the full fleet of affected apps using parallel sub-agents after I proved the method by hand.[SYS]
- The batched holiday-freeze remediation went from rollback to verified production release in a matter of days.[MAIL]
- I cleared the shared UI library's vulnerability backlog and rolled runtime and observability upgrades across the app fleet.[SYS]
- I run enablement sessions on agentic engineering, join interview panels for senior roles, and receive regular peer and leadership recognition.[MAIL]
- Code review across teams has been a constant part of my role alongside architecture work.[SYS]
Evidence:[SYS]verified in a system[MAIL]seen in mail, calendar or chat[AI]found by an AI, not re-checked[EST]an estimate