Domain 1 — People Leadership
People Leadership is the work of building, growing, and retaining effective engineers and teams. It is the most human part of the job and, for most new managers, the steepest part of the transition: the skills that made you a strong engineer (solving problems yourself) are nearly the opposite of the skills that make you a strong people leader (getting the best from others). This domain carries 20% of the EMA-I exam (12 questions).
The throughline across all five competencies below is judgment about people under uncertainty — deciding how much to delegate, what feedback to give and when, whom to hire, how to handle underperformance, and how to invest in growth. None of these have formulaic answers; the exam rewards the response that balances care for the individual with responsibility to the team and the work.
1.1 Delegation and ownership
Delegation is how a manager scales beyond their own two hands — and how engineers grow. The core skill is matching the scope of what you hand off to the person's current capability plus a deliberate stretch: enough challenge to develop them, not so much that they fail unsupported.
A useful mental model is the task-relevant maturity idea: how much direction someone needs depends not on their seniority in general but on their experience with this specific kind of task. A senior engineer may need close support on their first incident command even though they need none on system design. This connects to situational leadership — flexing between directing, coaching, supporting, and delegating as competence and confidence grow.
Delegation is not abdication. You delegate the task and the decisions, but you retain accountability for the outcome. Good delegation is explicit about three things: the desired outcome, the constraints (deadline, budget, what not to touch), and the level of authority ("decide and proceed" vs. "recommend and check with me").
Strong judgment looks like: delegating outcomes rather than dictating steps; giving someone a stretch with a safety net; being clear about decision rights; resisting the urge to take a task back the moment it gets messy.
Common pitfalls: delegating only the boring work and hoarding the interesting decisions; "delegating" by dumping an under-specified task and disappearing; swooping in to rescue at the first sign of struggle (which teaches the team they can't be trusted); or delegating authority you then quietly override.
Self-check: Why is task-relevant maturity a better guide to how much support to give than someone's overall seniority? What three things should an explicit delegation make clear?
1.2 Feedback in both directions
Feedback is the mechanism by which behaviour changes. Most feedback fails not because it is wrong but because of how and when it is delivered: too vague to act on, too late to matter, or so cushioned the message disappears.
The most reliable structure separates observation from interpretation. The SBI model — Situation, Behaviour, Impact — anchors feedback in a specific moment ("in yesterday's review"), describes observable behaviour rather than inferred character ("you interrupted twice"), and names the consequence ("she stopped contributing"). It avoids diagnosing intent or generalising ("you always…"), which is what triggers defensiveness.
Feedback should be timely (close to the event), specific, behaviour-anchored, and two-way — a manager who never asks for feedback signals that feedback flows only downward. Praise follows the same rules: "great job" is forgettable; naming the specific behaviour and its impact makes it repeatable.
Strong judgment looks like: giving small corrections frequently so feedback stops feeling like a verdict; being direct about hard messages while remaining respectful; treating clarity as a kindness; soliciting upward feedback and acting on it visibly.
Common pitfalls: saving feedback for the performance review; softening a hard message until it's unrecognisable; feedback that targets the person ("you're careless") instead of the behaviour; giving feedback while visibly frustrated, so the emotion drowns the content.
Self-check: Rewrite "you need to communicate better" using SBI. Why does behaviour-anchored feedback provoke less defensiveness than character-based feedback?
1.3 Hiring and onboarding
Hiring is one of the highest-leverage decisions a manager makes; a single bad hire can cost a team far more than an empty seat. The competency is structured, calibrated evaluation rather than gut feel. Structured interviews — consistent questions mapped to a defined rubric, scored independently before discussion — are markedly more predictive and more equitable than unstructured "vibe" conversations.
Calibration matters as much as structure: interviewers must share a standard for what "meets the bar" means, or the same candidate gets wildly different verdicts. Guard against well-known biases — the halo effect (one impressive trait colouring the whole assessment) and affinity bias (favouring people like yourself). A useful principle: hire for the ability to do the job and grow, not for surface similarity.
Onboarding is where a good hire is either activated or wasted. The goal is early, real contribution: a clear 30/60/90 framing, a first task small enough to ship quickly, an explicit buddy or guide, and documented context so the new person isn't blocked on tribal knowledge.
Strong judgment looks like: defining the bar before interviewing; scoring against a rubric; protecting the standard even under hiring pressure; designing onboarding so the first win comes fast.
Common pitfalls: lowering the bar because a seat has been open too long; over-indexing on a single impressive signal; "onboarding" that is a week of reading with no real task; assuming a strong hire needs no support.
Self-check: Why are structured interviews more predictive and more equitable than unstructured ones? What's the risk of leaving the hiring bar implicit?
1.4 Performance management
Performance management is setting clear expectations, supporting people to meet them, and following through with honest consequences when they don't. New managers tend to fail at the last part — they avoid the hard conversation, hoping the problem resolves itself. It rarely does, and the cost lands on the rest of the team, who see the gap and quietly recalibrate their own standards.
The foundation is clear expectations: people can only meet a bar they can see. When performance falls short, separate the diagnosis — is this a skill problem (they don't know how) or a will problem (they're not applying themselves)? — because the response differs entirely. Skill gaps call for coaching and time; will or fit problems call for a direct, documented conversation.
Handle problems early, privately, and specifically, with a genuine belief that improvement is possible and a clear picture of what "fixed" looks like. If a formal improvement plan becomes necessary, it should be a fair, time-boxed, well-supported chance to succeed — not a paperwork prelude to a decision already made.
Strong judgment looks like: addressing issues early rather than letting them fester; distinguishing skill from will; being clear and humane simultaneously; recognising that protecting the team sometimes means a hard decision about one person.
Common pitfalls: avoiding the conversation until it becomes a crisis; vague feedback that never names the actual gap; treating a will problem as a skill problem (endless coaching that goes nowhere); tolerating a "brilliant jerk" whose behaviour erodes the team.
Self-check: Why is distinguishing a skill problem from a will problem the first step? What signal does the rest of the team take from unaddressed underperformance?
1.5 One-on-ones and career development
The 1:1 is the manager's highest-frequency, highest-leverage tool — a recurring, protected space that belongs primarily to the report, not the status update. Status can travel by other channels; the 1:1 is for the things that don't surface in standups: blockers, frustrations, growth, early signs of disengagement.
Run 1:1s as their meeting: let them set much of the agenda, listen more than you talk, and use open questions. Over time, weave in career development — understanding where someone wants to go and creating the experiences (not just conversations) that get them there. Frameworks like growth ladders or competency matrices help make "what does the next level look like?" concrete and fair.
Retention is largely won or lost here. People rarely leave suddenly; the signals — withdrawal, cynicism, a stopped flow of ideas — appear first in 1:1s, for managers paying attention.
Strong judgment looks like: holding 1:1s consistently even when busy; making them the report's space; connecting day-to-day work to the person's longer-term growth; noticing disengagement early and addressing it.
Common pitfalls: cancelling 1:1s whenever things get busy (signalling the person is low priority); hijacking them for status updates; only discussing career growth at promotion time; talking more than listening.
Self-check: Why should the 1:1 be primarily the report's meeting rather than the manager's status check? Where do the earliest signs of attrition usually appear?
Key takeaways
- Match delegation to task-relevant maturity; delegate outcomes and decision rights, keep accountability.
- Make feedback timely, specific, behaviour-anchored (SBI), and two-way.
- Hire against a defined, calibrated bar; design onboarding for an early real win.
- Address performance issues early; separate skill from will; clarity is a kindness.
- Treat 1:1s as the report's protected space and the engine of growth and retention.