Stage profile · Management

Engineering Manager

Owns first-line management responsibilities for team outcomes, people development, collaboration, and operating mechanisms; understands the business and domain boundaries and uses professional judgment to review and delegate.

Read these as observable expectations across repeated work, not as a checklist for a single project. First distinguish whether the role expects the work, whether the person had a chance to demonstrate it, and whether the evidence supports the claim. Lack of opportunity or evidence is not itself a negative judgment. AI use is judged by verified outcomes, sound boundaries, and the quality of decisions; choosing not to use AI can be sound.

Four complementary evaluation lenses

These lenses and the A–H capability map answer different questions. One experience may provide evidence across lenses, but do not count the same result multiple times.

Business outcomes

Understand the people served and intended outcomes, make evidence-based trade-offs, and verify contribution. For platform, infrastructure, reliability, and safety work, cost, efficiency, risk reduction, and internal-user outcomes count; direct revenue ownership is not universal.

Domain expertise

Apply relevant knowledge to diagnose, design, implement or review, validate quality, and make evolution decisions. The professional leaves required depend on the role.

Team influence

Help others work effectively through communication, coordination, review, shared methods, coaching, or organizational mechanisms. IC influence is not measured by direct reports; managers also own formal people responsibilities.

Human competitiveness

Observe questioning, reasoning, learning transfer, judgment updates, relationship handling, and recovery in work. This is not a fixed personality or potential verdict; do not infer it from extroversion, fluent speech, or willingness to overwork.

Evidence to verify

Use this structure to understand a real example. Strong judgment can appear in a failed project; a successful result alone does not prove personal causation.

  1. Context and goal
  2. Role and authority
  3. Judgment and trade-offs
  4. Actions and collaborators
  5. Outcome and guardrails
  6. Attribution limits
  7. Counterevidence and adjustment

The labels beside capability references describe that capability’s role in this standard; they do not make the whole standard optional. Any role or scenario condition is stated separately.

Business outcomesView progression
  1. Defines team goals, outcome measures, and quality guardrails with partners and recalibrates priorities.

    Evidence to inspect: The team explains outcomes and trade-offs and adjusts based on evidence.

    Capability map and its role here：Business outcomes and validationDifferentiating herePlanningDifferentiating here
  2. Allocates capacity across delivery, reliability, talent growth, and technical investment.

    Evidence to inspect: Allocation reflects business risk and outcomes, with trade-offs recorded.

    Capability map and its role here：Investment choicesDifferentiating hereCapacity and dependenciesDifferentiating here
  3. Owns team outcomes and explains how management decisions contributed and where attribution is limited.

    Evidence to inspect: Distinguishes team delivery, external conditions, and personal contribution without appropriating credit.

    Capability map and its role here：AttributionDifferentiating hereMetrics and causal reasoningRelevant when context applies
  4. Plans and reviews with business partners at the cadence the decisions require, linking user opportunities, team investment, and outcome validation; the cadence can change with context.

    Evidence to inspect: Plans trace to opportunity evidence, outcome measures, and resource allocation.

    Capability map and its role here：PlanningDifferentiating here
  5. Renegotiates commitments when goals, capacity, or external conditions change, with clear accountability for scope cuts, deferral, or stopping.

    Evidence to inspect: Business partners acknowledge revised commitments and track their consequences.

    Capability map and its role here：Capacity and dependenciesDifferentiating here
Domain expertiseView progression
  1. Understands the team’s business flow, key domain rules, and data definitions; reviews product, technical, and quality risks, engaging AI experts when relevant, without being measured by personal coding depth.

    Applies when: Assess AI risk only when the team’s products, tools, or workflows involve AI.

    Evidence to inspect: Asks the right questions, involves appropriate experts, and owns the decision.

    Capability map and its role here：System designRelevant when context appliesAI evaluation and governanceDifferentiating hereQuality, security, and safetyDifferentiating here
  2. Builds testing, release, and incident-response practices proportionate to business risk; adds AI verification and human oversight when AI is used.

    Applies when: Does not require AI adoption; when applicable, assess verification, fallback, and accountability.

    Evidence to inspect: Quality and recovery are measurable without excessive manager approval.

    Capability map and its role here：Engineering systemsDifferentiating hereReliability and incidentsDifferentiating here
  3. Enables product, design, and engineering to discover problems and validate outcomes end to end.

    Evidence to inspect: The team tracks adoption and outcomes, not just on-time releases.

    Capability map and its role here：Product discovery and experience designDifferentiating hereBusiness outcomes and validationDifferentiating here
Team influenceView progression
  1. Builds capabilities for team goals through hiring, feedback, coaching, and performance management.

    Evidence to inspect: Role gaps and growth goals are clear; performance decisions use sustained evidence.

    Capability map and its role here：HiringDifferentiating hereGrowth and developmentDifferentiating here
  2. Designs clear goals, ownership, delegation, and decision mechanisms that reduce recurring friction.

    Evidence to inspect: Issues are resolved at the right level and members have decision space.

    Capability map and its role here：Team designDifferentiating hereDelegation and successionDifferentiating here
  3. Manages cross-team commitments, conflict, and escalation so the team can focus on key outcomes.

    Evidence to inspect: Partners accept priorities and escalation paths; conflicts do not remain unresolved.

    Capability map and its role here：NegotiationDifferentiating hereStakeholder influenceDifferentiating here
  4. Plans team roles, capability gaps, hiring and development cadence, capacity, and leadership succession.

    Evidence to inspect: Staffing supports business and technical plans, with succession measures for key roles.

    Capability map and its role here：Delegation and successionDifferentiating here
  5. Addresses performance gaps and sustained overload through clear feedback, support, and review periods.

    Evidence to inspect: Distinguishes goals, capability, motivation, and environment, with verified follow-up.

    Capability map and its role here：Frontline managementDifferentiating here
Human competitivenessView progression
  1. Makes people decisions from sustained, multi-source evidence while checking bias and uncertainty.

    Evidence to inspect: Can explain evidence, counterevidence, and follow-up observations.

    Capability map and its role here：Growth and developmentDifferentiating hereIntegrityDifferentiating here
  2. Builds relationships where mistakes, risks, and disagreement can be discussed candidly while maintaining accountability.

    Evidence to inspect: Issues surface earlier and retrospectives use evidence.

    Capability map and its role here：FeedbackDifferentiating hereConflict navigationDifferentiating here
  3. Reviews whether management mechanisms produce intended outcomes and adjusts personal behavior.

    Evidence to inspect: Feedback and team signals lead to specific management changes and follow-up.

    Capability map and its role here：Structured reflectionDifferentiating hereLearning transferDifferentiating here
  4. Uses explicit standards in promotion, performance, and resource decisions, manages conflicts of interest, and protects factual reporting.

    Evidence to inspect: Comparable cases use consistent criteria, with routes for appeal and correction.

    Capability map and its role here：IntegrityDifferentiating here
  5. Recognizes management blind spots and workload limits, seeks support, delegates, and restores judgment after setbacks.

    Evidence to inspect: Support and delegation reduce recurring firefighting, and decision quality recovers.

    Capability map and its role here：Resilience and recoveryDifferentiating here