The complexity of multi-AOC structures
Airline groups with multiple Air Operator Certificates face a structural tension that single-AOC operators don't. Each AOC has its own regulatory accountability – its own Accountable Manager, its own compliance obligations, its own relationship with its national aviation authority. But the group wants to capture synergies, standardise where possible and have coherent technical strategy across the portfolio.
The Group Technical Director role exists to resolve this tension. But the mandate definition matters enormously. Get it wrong and you either hire someone who can't navigate the regulatory complexity, or someone who can't drive group-level value creation.
Starting with the real questions
Before writing a job description, the mandate sponsor needs to answer some fundamental questions about what the role actually needs to achieve:
Questions to answer first
- What is the actual authority relationship between group and OpCo technical leadership?
- Where does regulatory accountability sit, and what is the group role vs OpCo role in regulatory interface?
- What synergies is the group trying to capture, and which require technical coordination?
- What is the current state of each OpCo's technical capability, and what needs to change?
- How does this role interface with group CEO, OpCo MDs, and the board?
The authority question
The most important question is about authority. In some group structures, the Group Technical Director has direct line management of OpCo technical leadership. In others, it's a dotted line or purely advisory. In some cases, the role has budget authority; in others, budget sits with OpCos.
These distinctions matter for candidate selection. A leader who has built their career in direct line management environments may struggle in an influence-based role. Conversely, someone who excels at cross-functional coordination may not have the edge required when they actually need to direct OpCo teams.
We've seen mandates fail because this wasn't clarified upfront. The candidate was assessed against one model of the role, but the reality was different. Getting clear on authority early allows for honest assessment of what kind of leader is actually needed.
The regulatory dimension
In multi-AOC structures, regulatory accountability remains with each AOC. The Accountable Manager of each operating company is personally accountable to their national aviation authority. This creates complexity for the Group Technical Director role.
The best candidates understand this complexity intuitively. They know they can't override OpCo Accountable Managers on compliance matters. They know that different NAAs have different expectations and approaches. They can work within this framework while still driving group-level standardisation where it's appropriate and valuable.
Candidates without multi-regulatory experience often underestimate this complexity. They come from single-AOC environments where the technical director had clear authority within one regulatory framework. The multi-AOC environment requires a different skill set.
Capability assessment challenges
Assessing candidates for Group Technical Director roles is harder than for single-operator roles. The candidate pool is smaller – genuinely multi-AOC experience is rare. And the transferability of single-AOC experience is uncertain.
We look for specific indicators:
- Experience working across regulatory boundaries, even if not in a formal group structure
- Evidence of influencing without direct authority – matrix management, cross-functional leadership
- Understanding of how synergies are actually captured in technical operations (and which 'synergies' are illusory)
- Political awareness – the ability to navigate complex stakeholder environments
- Commercial understanding – how technical decisions affect group economics
Structuring the mandate
A well-structured mandate for Group Technical Director search should include clarity on authority model, specific objectives for the first 12-24 months, stakeholder map and relationship expectations, performance metrics, and non-negotiable requirements vs nice-to-haves.
The specificity matters. "Drive technical synergies" is not a clear objective. "Establish common fleet technical policy across three AOCs within 18 months" is. "Strong stakeholder management" is not helpful. "Weekly interface with OpCo MDs and monthly presentation to group CEO" establishes real expectations.
The search process
Given the complexity and the small candidate pool, Group Technical Director searches require a different approach than typical senior technical roles. Market mapping needs to be more creative – the best candidates may not currently hold group-level titles but have relevant capability from other contexts. Assessment needs to probe for specific competencies that standard interviews miss. And stakeholder alignment within the group needs to be managed carefully throughout the process.
If you're considering a Group Technical Director appointment and would like to discuss how to structure the mandate, we'd be interested to understand your situation.
Hiring Group Technical Director?
We'd be interested to understand your structure and help design an effective search mandate.