Engineering Management Body of Knowledge
The official study resource for the Engineering Management Academy certifications — EMA-I, EMP-II, and EME-III. EMBoK v2.0, aligned to the EMA Competency Framework v1.0.
About this document
The Engineering Management Body of Knowledge (EMBoK) is the canonical study resource for all three Engineering Management Academy certifications. It covers everything the examinations assess, organised exactly as the exams are structured: five competency domains, each carrying equal weight, each broken into five competencies.
What distinguishes the three certifications is not which topics they test but the altitude at which they test them. An Associate exercises judgment within a single team; a Professional exercises it across teams, usually through other managers; an Expert exercises it across an organisation, largely by designing the systems within which others lead. Accordingly, every competency in this document is developed in three altitude bands — At Associate, At Professional, and At Expert — after its core concepts are established once.
This is deliberately not a collection of facts to memorise. All three exams test judgment — your ability to read a realistic situation and choose the most defensible action. This document teaches concepts, the established models that inform good decisions, and — most importantly — what strong versus weak judgment looks like at each altitude. Read it to build instincts, not to cram.
The three certifications
| Aspect | EMA-I (Associate) | EMP-II (Professional) | EME-III (Expert) |
|---|---|---|---|
| Certifies | First-line judgment leading a single engineering team | Organisational judgment across teams, usually as a manager of managers | Executive judgment at organisational scale |
| Typical scope | One team | Several teams / a department | An engineering organisation |
| Experience | No requirement | 3+ years leading teams | 7+ years shaping orgs |
| Questions | 60, drawn from a randomised bank | 75, drawn from a randomised bank | 90, drawn from a randomised bank |
| Duration | 90 minutes | 105 minutes | 120 minutes |
| Pass standard | 70% | 75% | 80% |
| Structure | 5 domains × 12 questions | 5 domains × 15 questions | 5 domains × 18 questions |
| Validity | 3 years, no mandatory renewal | 3 years, no mandatory renewal | 3 years, no mandatory renewal |
All three exams use the same question styles — single-answer, multiple-answer, scenario, ranking, and true/false — and all three are predominantly scenario-based: you are given a situation a manager at that altitude would realistically face and asked what you would do, what you would do first, or which option is best (or worst). There is usually a clearly correct answer and several plausible distractors that represent common mistakes. What escalates from exam to exam is the scope, ambiguity, and consequence of the scenarios — and the bar itself: each level is longer and holds a higher pass standard than the one before it.
The five domains
Every exam is balanced: engineering management fails at its weakest dimension, so no domain dominates. Each is worth 20% of your score, at every level.
- People Leadership — building, growing, and retaining effective engineers, teams — and leaders.
- Delivery & Execution — turning intent into shipped, reliable software, predictably.
- Strategy & Vision — connecting engineering work to business outcomes and direction.
- Technical Judgment — exercising sound engineering judgment without doing the engineering yourself.
- Culture & Coaching — shaping the environment in which good engineering happens.
The next chapter, The Framework & the Three Altitudes, defines the full 5×5 competency framework and — critically — what changes as judgment moves from one altitude to the next. Read it before the domain chapters: it teaches the pattern the whole document follows.
How to use this Body of Knowledge
- Read for judgment, not recall. For each competency, pay closest attention to the strong judgment and common pitfalls material — it mirrors how scenario questions are constructed.
- Read your altitude — and the one below it. Every band builds on the previous one. EMA-I candidates should master the core concepts and the Associate bands. EMP-II candidates should read the Associate bands too: Professional questions assume first-line judgment is already solid. EME-III candidates should read all three bands; executive scenarios frequently hinge on recognising which lower-altitude instinct no longer applies.
- Work the self-checks. Each competency ends with questions to test understanding at each altitude. If you can answer the ones for your level in your own words, you understand the material.
- Use the framework as a map. If you score poorly on a practice attempt, the domain breakdown tells you exactly which chapters to revisit.
- Don't confuse familiarity with mastery. Many candidates recognise the right behaviour but choose the comfortable one under pressure. The exams reward the right call, especially when it's the hard one.
A note on the models cited
Throughout, this document references widely-recognised models and research from the engineering-leadership canon (for example, situational leadership, the SBI feedback model, RACI, the DORA software-delivery metrics, and Amy Edmondson's work on psychological safety popularised by Google's Project Aristotle). These are tools for reasoning, not doctrine — the exams test whether you can apply judgment, not whether you can name a framework. Suggested further reading is collected in the appendix.