The Framework & the Three Altitudes
Every Engineering Management Academy examination assesses the same underlying structure: the EMA Competency Framework v1.0 — five domains, each containing five competencies. This chapter defines that structure once, and then defines the thing that actually distinguishes the three certifications: the altitude at which judgment is exercised. Read this chapter before the domain chapters; it teaches the pattern every one of them follows.
The competency framework at a glance
| Domain | Competencies |
|---|---|
| 1. People Leadership | Delegation & ownership · Feedback in both directions · Hiring & onboarding · Performance management · 1:1s & career development |
| 2. Delivery & Execution | Prioritisation under constraint · Estimation & honest commitments · Incident response & operational ownership · Scope, risk & dependencies · Process selection |
| 3. Strategy & Vision | Translating goals to technical direction · Communicating with non-engineers · Roadmapping (product vs. platform) · Resource allocation & build-vs-buy · Meaningful engineering metrics |
| 4. Technical Judgment | Evaluating architecture & its org consequences · Technical debt · Code review & quality · Staying technically credible · When to intervene |
| 5. Culture & Coaching | Psychological safety & productive conflict · Coaching vs. directing · Inclusive practice & equitable opportunity · Recognition, motivation & sustainable pace · Modelling values under pressure |
Twenty-five competencies. Every exam question — at every level — maps to exactly one of them.
Why the same domains at every level
It would be tempting to give each certification its own syllabus: put feedback in the Associate exam, org design in the Professional one, strategy in the Expert one. The framework deliberately refuses that. Engineering management does not shed responsibilities as it scales — it re-expresses them. An executive still hires, still gives feedback, still makes technical judgment calls; what changes is the scope of the decisions, the distance from the work, and the instruments available.
There is a second reason: management fails at its weakest dimension. A director with brilliant strategy and no ability to develop leaders will fail, exactly as a first-line manager with excellent 1:1s and no delivery discipline will. Balanced assessment — five domains, equal weight, at every level — reflects how the job actually breaks.
The three altitudes
Associate (EMA-I) — leading a team. The unit of ownership is a single team and the people on it. Judgment is exercised directly: you delegate the task, give the feedback, run the 1:1, make the call in the incident. The dominant transition being tested is from doing the work to getting the work done through the team. Time horizon: weeks to a quarter.
Professional (EMP-II) — leading across teams. The unit of ownership is a group of teams, usually led through other managers. Judgment is exercised at one remove: you rarely fix the problem yourself — you coach the manager who owns it, or fix the boundary, process, or incentive that produced it. New instruments appear (skip-levels, calibration, cross-team prioritisation, organisational design at department scale) and a new failure mode appears with them: doing your old job instead of your new one. The dominant transition is from managing work to managing managers and the system between teams. Time horizon: quarters to a year.
Expert (EME-III) — leading an organisation. The unit of ownership is the engineering organisation itself and its leadership layer. Judgment is exercised through systems: structures, standards, succession, culture, and the selection and development of leaders. Decisions are more ambiguous, more consequential, harder to reverse, and visible to everyone — the exam tests calibration under precisely those conditions. The dominant transition is from leading directly to building the machine that leads — an organisation that runs well without your daily presence. Time horizon: years.
| Dimension | Associate | Professional | Expert |
|---|---|---|---|
| Owns | A team | A group of teams | An organisation |
| Works through | Direct action with the team | Managers | Leaders, structures, and systems |
| Typical instruments | 1:1s, feedback, delegation, sprint & incident judgment | Skip-levels, calibration, cross-team prioritisation, manager coaching | Succession, org design, executive alignment, leadership development |
| Ambiguity | Bounded — most facts are knowable | Partial — signal is filtered through others | High — long feedback loops, political dimensions |
| Characteristic failure | Doing instead of delegating | Doing the managers' jobs; refereeing instead of fixing the system | Staying operational; failing to build leaders and successors |
One competency, three altitudes
Take delegation & ownership, the first competency of People Leadership, and watch it re-express itself:
- Associate: you delegate a meaningful project to an engineer — matched to their task-relevant maturity, with explicit outcomes, constraints, and decision rights — and resist taking it back when it gets messy.
- Professional: you delegate a team to a manager. The discipline is the same but the object is different: you hand over outcomes and decision rights, keep accountability, and resist reaching around the manager to their engineers — even when you could fix the problem faster yourself.
- Expert: you delegate through structure. Ownership is designed rather than assigned conversation by conversation: the org chart, charters, and decision rights determine who owns what. The failure you guard against is no longer a snatched-back task; it is an organisation whose critical functions silently depend on one irreplaceable person — including you.
Every competency in this document follows this arc. Once you can see it in one competency, you can anticipate it in all twenty-five — which is precisely the instinct the higher exams reward.
How the exams sample the framework
Each exam draws its questions from a randomised bank, split equally across the five domains at the exam's altitude: EMA-I draws 60 (12 per domain), EMP-II draws 75 (15 per domain), and EME-III draws 90 (18 per domain), balanced across each domain's competencies. Scenario questions dominate at every level, but their character shifts with altitude:
- EMA-I scenarios put you in the room: a struggling report, a slipping sprint, a conflict between quality and a deadline.
- EMP-II scenarios put you one level up: two of your managers disagree, a team is masking a slip, calibration is contested, a shared platform is the bottleneck.
- EME-III scenarios put you at the executive table: a key director is being courted, a reorg reshapes leaders' scopes, a public bet is failing, the leadership behaviours that worked at 150 people are failing at 300.
A useful consequence for candidates: higher-altitude exams assume the lower altitudes. EMP-II questions take sound first-line judgment as given; EME-III questions frequently hinge on recognising that a lower-altitude instinct — stepping in directly, solving it yourself — is exactly the wrong move at scale.
How to read an altitude band
Each competency in the domain chapters is structured the same way:
- Core concepts — the ideas and models that hold at every altitude, established once.
- At Associate / At Professional / At Expert — how the competency is actually exercised at each level, each band ending with what strong judgment looks like there and the common pitfalls the exam's distractors are built from.
- Self-check — questions per altitude to confirm you can reason in your own words, not just recognise the right answer.
Study the bands for your exam and the ones below it. The bands above your exam are worth skimming too — knowing where a competency is heading is often the clearest way to understand why the bar at your level is set where it is.