EMA-I Associate

Proficiency indicators

• I1A certified Associate can delegate an outcome rather than a set of steps, stating the constraints and the level of authority that goes with it. team
• I2A certified Associate can match the scope of what they hand off to a person's demonstrated capability on that kind of work, with a deliberate stretch and a safety net. team
• I3A certified Associate can recognise the moment they are about to take delegated work back, and choose support over rescue. team

Scenario contexts at this level

• An engineer is struggling with a delegated project and the deadline is close.
• A senior engineer wants a decision made for them that is theirs to make.
• Two engineers are unclear who owns a piece of work and both have stopped.

Proficiency indicators

• I1A certified Associate can give corrective feedback anchored in a specific situation and observable behaviour, and name its impact, without diagnosing intent. team
• I2A certified Associate can hold a difficult conversation early rather than waiting for a review cycle or hoping the problem resolves. team
• I3A certified Associate can invite and act on feedback about their own management from the people they lead. team

Scenario contexts at this level

• A high performer's behaviour is quietly damaging the team and nobody has said so.
• An engineer reacts defensively to feedback and the manager must decide what to do next.
• The team gives the manager a hard piece of upward feedback in a retrospective.

Proficiency indicators

• I1A certified Associate can run a structured interview against criteria defined before the process starts, and recognise the biases that unstructured evaluation invites. team
• I2A certified Associate can assess what a candidate can do rather than which tools they were permitted, and distinguish capability from fluency. team
• I3A certified Associate can design a first ninety days that gives a new hire explicit outcomes, a named guide, and early feedback. team

Scenario contexts at this level

• A panel disagrees about a candidate after an interview loop with no rubric.
• A new hire is three weeks in and nobody can say whether they are doing well.

Proficiency indicators

• I1A certified Associate can diagnose whether an engineer's underperformance is a matter of skill, will, or the conditions they were given, before choosing a response. team
• I2A certified Associate can set expectations explicitly enough that a later performance conversation refers to something the engineer already knew. team
• I3A certified Associate can follow a fair process to an honest consequence, including a formal one, without avoiding it or rushing it. team

Scenario contexts at this level

• An engineer has missed targets for two quarters and attributes it to unclear requirements that were, in fact, unclear.
• A well-liked engineer is not meeting the bar and the manager is tempted to wait for the next cycle.

Proficiency indicators

• I1A certified Associate can run a one-on-one that belongs to the report — their growth, their concerns — rather than to the manager's status needs. team
• I2A certified Associate can respond to a promotion request with evidence, a named gap, and a path, rather than a yes to retain or a no without reasons. team
• I3A certified Associate can help an engineer weigh the senior individual-contributor track against management without steering them toward the manager's own path. team

Scenario contexts at this level

• A talented engineer asks for promotion before consistently showing the next level's judgment.
• A senior engineer is bored and the manager cannot offer a promotion this cycle.

See What this exam does not assess below. Assessed from EMP-II.

Proficiency indicators

• I1A certified Associate can sequence a team's work by value and cost of delay rather than by who asked loudest or most recently. team
• I2A certified Associate can say no by surfacing the cost of yes — "we can do X, and Y slips" — and let the stakeholder choose. team
• I3A certified Associate can protect a team's focus against constant reprioritisation, and recognise when too much started work means nothing finishes. team

Scenario contexts at this level

• Two stakeholders each insist their feature is the top priority for the sprint.
• A product manager wants a small feature added mid-sprint that the lead engineer says will disrupt the goal.
• The team has ten things in progress and nothing has shipped in three weeks.

Proficiency indicators

• I1A certified Associate can distinguish an estimate from a commitment, and buffer the commitment deliberately rather than promising the estimate. team
• I2A certified Associate can re-plan openly when a commitment is at risk, giving stakeholders the choice between scope, date and quality rather than absorbing the gap with overtime. team
• I3A certified Associate can decline to give a date on the spot without an estimate, and say what it would take to give one. team

Scenario contexts at this level

• The team is three weeks into a six-week commitment and the estimate has doubled.
• An executive asks for a delivery date in a meeting before any estimation has happened.

Proficiency indicators

• I1A certified Associate can run an incident in progress in the right order — restore service, communicate, then find the cause — and resist debugging while users are down. team
• I2A certified Associate can lead a blameless postmortem that changes the system rather than naming the person. team
• I3A certified Associate can treat on-call load and service-level objectives as the team's operational ownership, not an interruption to real work. team

Scenario contexts at this level

• A production incident is in progress and the engineer who caused it wants to find the root cause first.
• A release introduced a regression and the postmortem is drifting toward blame.

Proficiency indicators

• I1A certified Associate can name a risk early, with its likelihood and impact, rather than hoping it does not materialise. team
• I2A certified Associate can manage a dependency on another team by negotiating a timeline and a fallback, before escalating and before building around it. team
• I3A certified Associate can trade scope before quality when a deadline is fixed, and say so. team

Scenario contexts at this level

• The team's roadmap is blocked on a platform team's request that has waited four weeks.
• A fixed launch date is approaching and the only ways to hit it are to cut scope or cut testing.

Proficiency indicators

• I1A certified Associate can choose the lightest process that solves the team's actual problem, and change it when the problem changes. team
• I2A certified Associate can recognise when a drop in throughput is caused by interruptions and fragmentation rather than effort, and change the flow of work rather than push the people. team
• I3A certified Associate can introduce AI-assisted tooling to a team's workflow with an explicit view of what it changes about review, testing and ownership. team

Scenario contexts at this level

• Velocity has dropped for three sprints; engineers say they are busy but nothing ships.
• The team adopts a coding assistant and pull requests get larger and faster than review can handle.

Proficiency indicators

• I1A certified Associate can translate a business goal into the team's work as outcomes — the change wanted in the world — rather than a feature list. team
• I2A certified Associate can ensure every engineer can say why their current work matters to the business. team
• I3A certified Associate can re-derive the team's plan when circumstances change, instead of defending the original list. team

Scenario contexts at this level

• The organisation has adopted OKRs and an engineer cannot connect their tickets to any key result.
• A strategy arrives as a list of features with no theory of why they matter.

Proficiency indicators

• I1A certified Associate can explain a technical trade-off to a non-engineering stakeholder in the language of their outcome, without jargon and without condescension. team
• I2A certified Associate can partner with product and design as peers whose constraints are real, rather than as a queue of requests. team
• I3A certified Associate can deliver bad news about a delivery to a stakeholder early, with options, rather than late with excuses. team

Scenario contexts at this level

• A stakeholder presses for a date and does not understand why the estimate has a range.
• A product manager and the lead engineer disagree about a feature's size in front of the team.

Proficiency indicators

• I1A certified Associate can hold a defined share of a team's capacity for platform and quality work and defend it with evidence of what its absence costs. team
• I2A certified Associate can present a team roadmap as bets with expected outcomes and confidence, not as a list of promised dates. team
• I3A certified Associate can recognise when a roadmap is a wish list assembled bottom-up with no connecting thesis. team

Scenario contexts at this level

• Product wants no reduction in feature output this quarter and the team's technical debt is slowing delivery.
• The team's roadmap is due and it is a list of everything anyone asked for.

Proficiency indicators

• I1A certified Associate can frame a build-versus-buy decision around total cost, differentiation and reversibility rather than engineering preference. team
• I2A certified Associate can account for the cost of the team's delivery — people, vendors, infrastructure — well enough to argue for a change in it. team
• I3A certified Associate can evaluate an AI service or vendor as a third option beside build and buy, with its own cost and risk profile. team

Scenario contexts at this level

• An engineer proposes building an internal tool that a vendor sells.
• The team is asked to justify a new headcount request in business terms.

Proficiency indicators

• I1A certified Associate can choose delivery metrics that measure flow and stability rather than activity, and say what each one cannot show. team
• I2A certified Associate can recognise when a metric has become a target and is being gamed. team
• I3A certified Associate can decline to use a single productivity number for individuals, and explain why. team

Scenario contexts at this level

• Leadership wants a productivity score per engineer.
• A metric improved sharply in one sprint and nothing else changed.

See What this exam does not assess below. Assessed from EMP-II.

Proficiency indicators

• I1A certified Associate can improve a design decision through questions — what does this assume, what happens when it fails, who has to coordinate — without taking it over. team
• I2A certified Associate can spend deliberation on the irreversible decisions and let reversible ones move fast. team
• I3A certified Associate can see a system boundary and a team boundary as one decision. team

Scenario contexts at this level

• The team is choosing between a quick design and a sound one with a launch approaching.
• A proposed split of a service would require two teams to coordinate on every change.

Proficiency indicators

• I1A certified Associate can make technical debt visible in terms stakeholders understand — what it costs per month, what it risks — rather than as an engineering complaint. team
• I2A certified Associate can distinguish debt worth repaying from debt worth carrying, and schedule repayment as ordinary work. team
• I3A certified Associate can recognise a proposed rewrite as a bet and evaluate it as one. team

Scenario contexts at this level

• Product wants no reduction in feature output and the team says the debt is unbearable.
• A senior engineer proposes rewriting a working system in a new framework.

Proficiency indicators

• I1A certified Associate can set a quality bar the team owns — tests, review, definition of done — and hold it under deadline pressure. team
• I2A certified Associate can shape a code-review culture that teaches rather than gatekeeps, and notice when review has become rubber-stamping. team
• I3A certified Associate can state what review must establish for AI-generated code, and who is accountable for it. team

Scenario contexts at this level

• A deadline is close and the team proposes skipping tests to make it.
• Coding assistants have made pull requests larger and review has become cursory.
• Two senior engineers block each other's pull requests over style.

Proficiency indicators

• I1A certified Associate can stay close enough to the team's technical work to judge it — reading designs, reviewing selectively, asking sharp questions — without becoming its bottleneck. team
• I2A certified Associate can decide when to intervene in a technical decision and when to let the team own it, and know which decisions are theirs. team
• I3A certified Associate can resist doing the engineering themselves when the team is struggling, and choose the intervention that leaves the team stronger. team

Scenario contexts at this level

• A newly promoted manager is still doing significant individual-contributor work and their team is not growing.
• The team is about to make a technical decision the manager believes is wrong.

Proficiency indicators

• I1A certified Associate can introduce AI assistance to a team with explicit expectations for verification, ownership and disclosure. team
• I2A certified Associate can recognise the risks AI assistance introduces — unverified code, leaked data, eroded understanding — and put proportionate controls in place. team
• I3A certified Associate can distinguish where AI assistance genuinely helps the team from where it is being used to look fast. team

Scenario contexts at this level

• The chief executive asks whether engineering should adopt AI coding assistants everywhere.
• An engineer ships code generated by an assistant that they cannot explain in review.

Proficiency indicators

• I1A certified Associate can treat a security vulnerability, a privacy obligation or a compliance requirement as the team's own work, prioritised by risk rather than deferred to a function. team
• I2A certified Associate can respond to a security finding proportionately — triage by exploitability and exposure — rather than freezing or ignoring it. team
• I3A certified Associate can recognise a privacy or access-control problem in an everyday decision before it becomes an incident. team

Scenario contexts at this level

• A scanner reports hundreds of dependency vulnerabilities and the team is paralysed.
• An engineer has had unaudited write access to production data for months.

Proficiency indicators

• I1A certified Associate can respond to an admitted mistake, a naive question or a challenge to their idea with curiosity rather than punishment. team
• I2A certified Associate can pair psychological safety with high standards, and recognise that "going easy" is not safety. team
• I3A certified Associate can invite open disagreement about ideas and then expect commitment once the decision is made. team

Scenario contexts at this level

• Nobody on the team challenges anything in design reviews.
• Two senior engineers have a persistent tension that is affecting the team.
• An engineer admits to a costly mistake in a retrospective.

Proficiency indicators

• I1A certified Associate can develop an engineer's judgment through questions rather than supplying the answer, and know when directing is the right exception. team
• I2A certified Associate can recognise when they are rescuing rather than coaching, and what the team learns from each. team
• I3A certified Associate can coach a senior engineer who is strong technically but does not mentor, document or lift others. team

Scenario contexts at this level

• An engineer brings every decision to the manager and the manager keeps deciding.
• A strong engineer is uninterested in helping anyone else grow.

Proficiency indicators

• I1A certified Associate can notice who on the team gets the stretch work, the visibility and the benefit of the doubt, and correct the pattern. team
• I2A certified Associate can run team rituals — meetings, reviews, on-call, recognition — so that they do not systematically favour the loudest, the most present or the most similar to the manager. team
• I3A certified Associate can recognise glue work and ensure it is valued and distributed rather than left to whoever will not refuse it. team

Scenario contexts at this level

• Office-based engineers get spontaneous time with the manager; remote ones get scheduled calls, and promotions are following the pattern.
• One engineer does all the coordination work and none of the visible work.

Proficiency indicators

• I1A certified Associate can recognise burnout and disengagement early from changes in behaviour, and respond to the person before the output. team
• I2A certified Associate can protect a sustainable pace, and treat a run of heroics as a system failure rather than a badge. team
• I3A certified Associate can recognise people specifically and in the way that person values, including on a distributed team where effort is not visible. team

Scenario contexts at this level

• A high performer has become withdrawn over two months.
• The team has been in crunch for a quarter and leadership calls it commitment.

Proficiency indicators

• I1A certified Associate can make the costly right call — on quality, on honesty, on a person — when pressure points the other way, and know that the team is watching. team
• I2A certified Associate can act on a values breach by a high performer rather than let results buy an exemption. team
• I3A certified Associate can recognise when they are being asked to shade the truth about status and decline. team

Scenario contexts at this level

• A manager is asked to report a slipping project as on track.
• The team's best engineer treats colleagues with contempt and delivers more than anyone.

Proficiency indicators

• I1A certified Associate can manage their own time and calendar so that the team's needs, not the inbox, determine where the hours go. team
• I2A certified Associate can recognise their own overload and burnout, set boundaries, and ask for help before it reaches the team. team
• I3A certified Associate can separate their own anxiety about a situation from the decision it needs. team

Scenario contexts at this level

• A new manager is working evenings to keep up with both coding and management and is visibly exhausted.
• A manager's calendar is entirely meetings and the team has not had a real one-on-one in a month.