EMA-I Body of Knowledge
The official study resource for the Engineering Management Associate (EMA-I) certification. Aligned to the EMA Competency Framework v1.0.
About this document
This Body of Knowledge (BoK) is the canonical study resource for EMA-I candidates. It covers everything the examination assesses, organised exactly as the exam is structured: five competency domains, each carrying equal weight, each broken into five competencies.
It is deliberately not a collection of facts to memorise. EMA-I tests judgment — your ability to read a realistic situation and choose the most defensible action. Accordingly, this document teaches concepts, the established models that inform good decisions, and — most importantly — what strong versus weak judgment looks like in practice. Read it to build instincts, not to cram.
What EMA-I assesses
EMA-I certifies that you can lead a single engineering team effectively: that you can exercise sound first-line management judgment across people, delivery, strategy, technical decisions, and culture. It assumes no specific years of experience — it measures capability, not tenure.
| Aspect | Detail |
|---|---|
| Questions | 60, drawn from a randomised bank |
| Duration | 90 minutes |
| Pass standard | 70% |
| Structure | 5 domains, equally weighted — 12 questions each |
| Question styles | Single-answer, multiple-answer, scenario, ranking, true/false |
| Validity | 3 years, no mandatory renewal |
Most questions are scenario-based: you are given a situation a first-line engineering manager 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.
The five domains
The exam is balanced: engineering management fails at its weakest dimension, so no domain dominates. Each is worth 20% of your score.
- People Leadership — building, growing, and retaining effective engineers and teams.
- 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.
How to use this Body of Knowledge
- Read for judgment, not recall. For each competency, pay closest attention to the "Strong judgment vs. common pitfalls" sections — they mirror how scenario questions are constructed.
- Work the self-checks. Each competency ends with questions to test understanding. If you can answer them 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 exam rewards 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 exam tests whether you can apply judgment, not whether you can name a framework. Suggested further reading is collected in the appendix.