Skip to main content

Learning path

Engineering Manager learning path: everything to study, topic by topic

Comprehensive Engineering Manager assessment covering team building, delivery management, people management, technical strategy, organizational design, and engineering leadership.

Short answer

To learn Engineering Manager, work through 6 modules and 32 topics in the order they build on each other. It starts with Team Building & Hiring, then moves on to Delivery Management and People Management. Use the map as a checklist, or measure your level and study only what is missing.

6
modules
32
topics
55
min to assess

What you will study

Topics are grouped by module. Open one to see its objectives and key concepts.

1 · Team Building & Hiring4 topics
  • Hiring Process

    Designing and running effective engineering hiring processes end-to-end

    Objectives

    • Design a structured interview process
    • Reduce hiring bias through rubrics

    Key concepts

    • job descriptions
    • structured interviews
    • rubrics
    • sourcing
    • bias reduction
  • Onboarding

    Creating effective onboarding programs for new engineering hires

    Objectives

    • Design a 30-60-90 onboarding plan
    • Measure onboarding effectiveness

    Key concepts

    • 30-60-90 day plans
    • buddy systems
    • ramp-up metrics
    • first PR
    • knowledge transfer
  • Team Composition

    Building balanced teams with complementary skills, experience levels, and diversity

    Objectives

    • Build a balanced team composition
    • Address bus factor risks

    Key concepts

    • skill matrix
    • T-shaped engineers
    • seniority mix
    • diversity
    • bus factor
  • Culture Building

    Establishing and maintaining a healthy engineering team culture

    Objectives

    • Foster psychological safety in a team
    • Build team culture intentionally

    Key concepts

    • psychological safety
    • team norms
    • values alignment
    • remote culture
    • rituals
2 · Delivery Management5 topics
  • Sprint Planning

    Running effective sprint planning sessions that set teams up for success

    Objectives

    • Facilitate productive sprint planning
    • Balance ambition with realistic capacity

    Key concepts

    • capacity planning
    • sprint goals
    • commitment vs forecast
    • backlog readiness
  • Velocity Tracking

    Using velocity and flow metrics to improve team predictability and delivery

    Objectives

    • Use velocity for forecasting, not comparison
    • Identify delivery bottlenecks

    Key concepts

    • velocity
    • cycle time
    • throughput
    • WIP limits
    • burndown charts
    • flow metrics
  • Risk Management

    Identifying, assessing, and mitigating delivery risks proactively

    Objectives

    • Build and maintain a project risk register
    • Escalate risks at the right time

    Key concepts

    • risk register
    • probability/impact matrix
    • mitigation plans
    • escalation triggers
  • Dependency Management

    Tracking and resolving cross-team and external dependencies

    Objectives

    • Map and manage cross-team dependencies
    • Reduce dependency-related delays

    Key concepts

    • dependency mapping
    • critical path
    • blocking vs blocked
    • API contracts
    • SLAs
  • Release Planning

    Planning and coordinating releases with feature flags, rollbacks, and phased rollouts

    Objectives

    • Plan a safe release strategy
    • Use feature flags for risk mitigation

    Key concepts

    • feature flags
    • canary releases
    • blue-green deployment
    • rollback plans
    • release trains
3 · People Management5 topics
  • One-on-Ones

    Running effective one-on-one meetings that build trust and uncover issues early

    Objectives

    • Structure effective one-on-ones
    • Use coaching questions to develop reports

    Key concepts

    • active listening
    • coaching questions
    • cadence
    • agenda ownership
    • action items
  • Feedback Culture

    Giving, receiving, and fostering a culture of continuous feedback

    Objectives

    • Give constructive feedback using SBI
    • Build a team culture of continuous feedback

    Key concepts

    • SBI model
    • radical candor
    • feedback frequency
    • peer feedback
    • psychological safety
  • Performance Reviews

    Conducting fair, motivating performance reviews and managing underperformance

    Objectives

    • Conduct a fair performance review
    • Manage underperformance constructively

    Key concepts

    • calibration
    • rating systems
    • recency bias
    • PIPs
    • promotion criteria
  • Career Growth

    Supporting engineers' career development through growth plans and stretch opportunities

    Objectives

    • Create individualized growth plans
    • Help engineers navigate career transitions

    Key concepts

    • career ladders
    • growth plans
    • stretch assignments
    • IC vs management track
    • mentoring
  • Conflict Resolution

    Mediating interpersonal conflicts within engineering teams

    Objectives

    • Mediate conflicts between team members
    • Know when to escalate to HR

    Key concepts

    • mediation
    • active listening
    • root cause analysis
    • restorative conversations
    • HR escalation
4 · Technical Strategy4 topics
  • Tech Debt Prioritization

    Identifying, quantifying, and prioritizing technical debt reduction alongside feature work

    Objectives

    • Quantify tech debt using business impact
    • Balance debt reduction with feature delivery

    Key concepts

    • tech debt quadrants
    • interest metaphor
    • debt registers
    • investment ratio
    • refactoring ROI
  • Architecture Decisions

    Facilitating architecture decisions through ADRs and collaborative design reviews

    Objectives

    • Facilitate architecture decisions with ADRs
    • Balance team autonomy with alignment

    Key concepts

    • ADRs
    • design reviews
    • RFC process
    • reversibility
    • technical alignment
  • Build vs Buy

    Making build-vs-buy decisions based on strategic value, cost, and team capacity

    Objectives

    • Evaluate build vs buy using TCO and strategic value
    • Assess vendor lock-in risk

    Key concepts

    • TCO analysis
    • core vs context
    • opportunity cost
    • vendor lock-in
    • integration cost
  • Vendor Evaluation

    Evaluating and selecting third-party tools, platforms, and service providers

    Objectives

    • Run a structured vendor evaluation process
    • Negotiate favorable SLAs

    Key concepts

    • evaluation criteria
    • proof of concept
    • SLA review
    • migration cost
    • vendor risk
5 · Organizational Design6 topics
  • Team Topologies

    Applying team topology patterns: stream-aligned, enabling, complicated-subsystem, platform

    Objectives

    • Apply team topology patterns
    • Reduce cognitive load through team design

    Key concepts

    • stream-aligned teams
    • platform teams
    • enabling teams
    • cognitive load
    • team interaction modes
  • Scaling Teams

    Growing engineering organizations while maintaining velocity and culture

    Objectives

    • Plan team scaling without destroying culture
    • Know when and how to split teams

    Key concepts

    • team splitting
    • Dunbar numbers
    • communication overhead
    • hiring plans
    • org structure
  • Cross-Team Processes

    Designing processes that enable multiple teams to collaborate effectively

    Objectives

    • Design cross-team collaboration processes
    • Balance standardization with autonomy

    Key concepts

    • inner source
    • shared libraries
    • API governance
    • guilds
    • communities of practice
  • Incident Management Culture

    Building a blameless incident management culture with effective post-mortems

    Objectives

    • Run blameless post-mortems
    • Build a healthy on-call culture

    Key concepts

    • blameless post-mortems
    • incident severity
    • on-call rotations
    • SLOs
    • error budgets
  • Remote Team Practices

    Building high-performing distributed teams through async communication, remote culture, and inclusive practices

    Objectives

    • Design async-first communication practices for distributed teams
    • Build and sustain team culture in a fully remote environment

    Key concepts

    • async communication
    • remote culture building
    • distributed team productivity
    • time zone management
    • remote hiring
    • virtual team building
  • Organizational Redesign & Team Topology

    Applying Team Topologies principles to restructure engineering organizations for flow, cognitive load, and delivery efficiency

    Objectives

    • Diagnose organizational coupling using Conway's Law and Team Topologies principles
    • Propose a restructuring that reduces cognitive load and increases delivery flow

    Key concepts

    • stream-aligned teams
    • platform teams
    • enabling teams
    • complicated-subsystem teams
    • cognitive load
    • interaction modes
    • Conway's Law
6 · Engineering Leadership8 topics
  • Executive Influence

    Influencing business decisions as an engineering leader through data and storytelling

    Objectives

    • Present engineering investments in business terms
    • Influence executive decisions with data

    Key concepts

    • business cases
    • engineering metrics
    • DORA metrics
    • executive communication
    • ROI framing
  • Budget Management

    Managing engineering budgets including headcount, tools, infrastructure, and contractors

    Objectives

    • Build an engineering department budget
    • Optimize cloud and tooling spend

    Key concepts

    • headcount planning
    • cost per engineer
    • cloud cost optimization
    • contractor vs FTE
    • capex vs opex
  • Technical Due Diligence

    Conducting technical due diligence for acquisitions, partnerships, and major investments

    Objectives

    • Conduct a technical due diligence review
    • Assess acquisition integration risks

    Key concepts

    • code quality assessment
    • architecture review
    • team assessment
    • risk inventory
    • integration plan
  • AI/ML Team Management

    Managing AI/ML teams effectively, adopting AI-assisted development tools, and governing ethical AI use

    Objectives

    • Lead AI/ML teams with clear goals and measurable outcomes
    • Govern ethical AI adoption within engineering organizations

    Key concepts

    • managing AI/ML teams
    • AI-assisted development tools
    • measuring AI productivity
    • upskilling teams for AI
    • ethical AI governance
  • Engineering Strategy & OKRs at Scale

    Defining and cascading engineering strategy through OKRs, headcount planning, and multi-team goal alignment

    Objectives

    • Define a multi-team engineering strategy and cascade it via OKRs
    • Align quarterly engineering goals with business north star metrics

    Key concepts

    • engineering strategy
    • OKR cascading
    • headcount planning
    • goal alignment
    • strategy vs tactics
    • north star metrics
    • quarterly planning
  • Managing Multi-Team Dependencies

    Coordinating across multiple engineering teams: dependency mapping, cross-team OKRs, platform vs feature team dynamics

    Objectives

    • Build a dependency map across 4+ engineering teams and surface critical path risks
    • Design escalation paths that resolve cross-team blockers without management overhead

    Key concepts

    • dependency mapping
    • cross-team OKRs
    • platform teams
    • Team Topologies
    • API-as-contract
    • Gantt vs PERT
    • escalation paths
  • Budget Ownership & Headcount Planning

    Managing engineering budgets: headcount planning, contractor vs FTE decisions, tooling costs, and cost justification

    Objectives

    • Build a headcount plan that aligns engineering capacity with product roadmap
    • Justify engineering budget decisions in business ROI terms to finance stakeholders

    Key concepts

    • headcount planning
    • FTE vs contractor
    • engineering ROI
    • budget cycles
    • cost centers
    • tooling budgets
    • growth vs efficiency modes
  • Executive Communication & Board Reporting

    Communicating engineering strategy and metrics to executive stakeholders: board presentations, OKR reviews, and incident briefings

    Objectives

    • Translate engineering metrics into business impact narratives for board-level audiences
    • Structure a post-incident briefing that builds executive confidence rather than erodes it

    Key concepts

    • executive narratives
    • engineering metrics for execs
    • board presentations
    • risk communication
    • incident briefings
    • BLUF format
    • storytelling with data

Levels: Junior, Mid, Senior, and Expert

Explain it in your own words

Graded by AI · no account · 1 question

No options to guess from: you write, the AI grades against the topic's rubric and tells you what level your answer reads at.

0 / 600

Already studying Engineering Manager?

The assessment measures topic by topic, and your plan skips what you already know.

Open to read. An account is only needed to be measured.

Frequently asked questions

Where should I start studying Engineering Manager?

Start with Team Building & Hiring: Hiring Process, Onboarding, and Team Composition. The map orders topics by what they depend on, so each one prepares the next.

How long does a full Engineering Manager assessment take?

A full assessment of this path takes about 55 minutes. Study time depends on where you start; a diagnostic shows which topics you can skip.

Do I need an account to use this page?

No. The map, objectives and key concepts are open. You only need an account to be measured, get your gap by topic and receive a plan.