Skip to the content ForoHackers
Log inJoin

Engineering management: start here

Engineering management
#587 · Ophuscado · · Report

Engineering management is the work of getting a team of engineers to deliver good software, steadily, without burning out. The manager writes less code and spends the time on people, priorities and the system around the team. It is a different craft from programming, not a promotion in the same one.

Key concepts

  • One-to-ones: regular private conversations about work, growth and obstacles; the main tool for trust and early warning.
  • Feedback: specific, timely and about observable behaviour, given in both directions.
  • Delegation: handing over the outcome and the authority with it, not just the task.
  • Prioritisation: saying what the team will not do, so the rest gets done well.
  • Team health: onboarding, on-call load, meeting load and how decisions get made.

Vocabulary

  • IC: individual contributor, someone who builds rather than manages.
  • Span of control: how many people report to one manager.
  • Blameless postmortem: reviewing a failure for causes in the system, not for culprits.
  • Skip-level: a conversation with your reports' reports.

What to study, in order

  1. Run a weekly one-to-one as both sides: write the agenda, take notes, follow up on every promise.
  2. Practise giving feedback with a simple structure: situation, behaviour, impact, next step.
  3. Write a team charter: purpose, how work is chosen, how decisions are made, how incidents are handled.
  4. Run a blameless postmortem on a past failure and list changes to the system, not to people.
  5. Read about delegation levels and apply a clear one to each task you hand out.

Related tags

#technical-leadership #program-management #careers #interviews

Log in or join to reply.