Career roadmap

Engineering Manager

Build and run a team that ships well: people first, delivery second, code third.

Time: 6-12 months part-time
Entry bar: Senior engineering experience. Almost never an external entry-level move.
Stages: 5 · 25 topics

0/25 studied0%

Before you start Eng Manager

4-6 weeks · 0/5 topics

The job is not senior engineering with meetings. Understanding that early prevents failure.

Output is now the team's output, which requires a different definition of a good day.
- Manager versus tech lead versus staff engineer
- Letting go of individual output
- The multiplier mindset
- Common first-year failure modes
The core management ritual, and the one most often wasted on status.
- Structure and cadence
- Listening more than talking
- Career conversations
- Building trust deliberately
Timely and specific, including the difficult kind.
- Giving feedback that changes behaviour
- Receiving feedback without defensiveness
- Praise in public, correct in private
- Documenting for review cycles
Giving away work you enjoy, to people who will do it differently.
- Matching task to growth need
- Setting context, not instructions
- Accepting a worse first attempt
- Escalation boundaries
Calendars fill instantly. Protecting thinking time is a deliberate act.
- Maker versus manager schedules
- Meeting hygiene and cancellation
- Prioritising your own work
- Avoiding becoming a bottleneck

BuildRun a project as tech lead first: delegate the interesting work and coach rather than solve.

5-7 weeks · 0/5 topics

The part of the job with the longest-lasting effect and the least immediate feedback.

Engineers leave managers who cannot articulate their path.
- Levelling frameworks and expectations
- Growth plans with evidence
- Promotion cases that succeed
- Supporting non-linear paths
Including the conversations nobody wants to have.
- Setting clear expectations
- Addressing underperformance early
- Improvement plans done fairly
- Managing out with dignity
The highest-leverage activity a manager does, and the easiest to do badly.
- Role definition and scorecards
- Structured interviewing
- Reducing bias in the process
- Closing candidates honestly
Time to first meaningful contribution is a measurable management outcome.
- Structured onboarding plans
- Buddy and mentor systems
- Early wins by design
- Understanding why people leave
Psychological safety is the strongest predictor of team performance.
- Psychological safety in practice
- Handling conflict between engineers
- Burnout detection and prevention
- Team rituals that are worth keeping

BuildWrite growth plans for a real or hypothetical team of five, each with concrete next steps.

4-6 weeks · 0/5 topics

Predictable shipping without turning the team into a feature factory.

Commitments you can keep, and honesty about the ones you cannot.
- Estimation and uncertainty ranges
- Capacity planning realistically
- Handling interruptions and support load
- Renegotiating scope early
The minimum process the team needs, and no more.
- Choosing a working model with the team
- Removing ceremonies that add nothing
- Code review and quality standards
- Incident and on-call processes
DORA metrics, used to improve the system rather than rank individuals.
- Lead time and deployment frequency
- Change failure rate and MTTR
- Avoiding individual productivity metrics
- Reporting to leadership
Staying technical enough to make good calls, without taking the decisions away.
- Architecture decisions and who makes them
- Managing technical debt deliberately
- Reviewing designs, not just code
- Balancing autonomy with consistency
Protecting the team while keeping the organisation informed.
- Reporting status honestly
- Pushing back on unrealistic asks
- Negotiating with product
- Communicating bad news early

BuildIntroduce one delivery improvement and measure its effect over a quarter.

4-6 weeks · 0/5 topics

Beyond one team: organisation design, strategy and managing managers.

Team boundaries determine architecture, whether you intend it or not.
- Team topologies and interaction modes
- Conway's law in practice
- Splitting and merging teams
- Ownership boundaries
Connecting what the team builds to why the business cares.
- Writing a team charter
- Investment allocation across work types
- Multi-quarter planning
- Communicating strategy repeatedly
The next transition, with its own set of new failure modes.
- Coaching managers rather than teams
- Skip-level conversations
- Consistency across teams
- Delegating management work
Reorganisations, migrations and layoffs are part of the role.
- Communicating change honestly
- Managing through uncertainty
- Driving a technical migration
- Supporting people through difficulty
Headcount, tooling and cloud spend become your responsibility.
- Headcount planning and justification
- Tooling and vendor evaluation
- Cloud cost ownership
- Making a business case

BuildWrite a team strategy document connecting engineering work to business outcomes.

3-5 weeks · 0/5 topics

EM loops are behavioural-heavy with a technical round and a people scenario round.

The dominant round. Specific stories with outcomes beat general philosophy.
Ch — Behavioural Questions
- Managing an underperformer
- Resolving conflict between engineers
- A project that failed and why
- Growing someone into a promotion
Live scenarios: what would you do, right now, in this situation.
- Two engineers in open conflict
- A star engineer behaving badly
- A team missing every deadline
- Someone resigning unexpectedly
Still assessed, because managers who cannot follow the work lose credibility.
- System design at a high level
- Code review discussion
- Technical trade-off reasoning
- How you stay current
Planning, estimation and stakeholder scenarios.
- Recovering a late project
- Handling an executive escalation
- Balancing features and debt
- Introducing process to a resistant team
Be able to state what you believe and give evidence you practise it.
- Your approach to growth and feedback
- How you handle disagreement
- What you changed your mind about
- How you measure your own success

BuildA written management philosophy and three deeply prepared stories with outcomes.

Every growing engineering organisation needs them, and good ones are scarce because the skill set barely overlaps with senior engineering.

Content last reviewed 2026-08-31. Guidance only — no institute or paid placement is endorsed anywhere in this book.