The Engineering Manager Handbook (Development Manager) · The Engineering Manager's Job
The Manager's Operating System
Turn a reactive calendar into a deliberate system of cadences — 1:1s, team rituals, planning, reviews and reporting — so nothing important depends on memory.
Scenario
Example organisation: Rita is promoted to engineering manager (in her company the title is Development Manager) for two teams, eleven engineers. Her calendar fills with whatever arrives: escalations, recruiting calls, status meetings. Some 1:1s happen every three weeks, some not at all. Quarterly planning starts a week late because she forgot to collect input.
What you see on the team
- 1:1s that happen irregularly; some engineers haven't had one in a month.
- Recurring work (hiring loops, reviews, planning) handled at the last minute.
- The manager always busy, always behind, rarely thinking ahead.
- Teams that don't know when decisions or feedback will come.
The common mistake
Running management from the inbox — reacting to whatever arrives — instead of from a deliberate system of cadences that make recurring responsibilities automatic.
Why it happens
Managers inherit a calendar, not a system. Urgent requests are loud; important routines are quiet until they're late. Project Oxygen's list of what effective managers do includes being a good coach, communicating effectively and supporting career development (re:Work) — all of which need regular, protected time to happen at all.
The playbook
Define your cadences — weekly, monthly, quarterly — and put them in the calendar:
| Cadence | Activity |
|---|---|
| Weekly | 1:1s with every direct report; staff meeting with leads; written update to your manager; hiring pipeline review |
| Bi-weekly | Team planning/demo/retro (attend some, not all) |
| Monthly | Skip-level conversations (2–3 people); delivery and health metrics review; budget check |
| Quarterly | Planning with product; career conversations; team health survey; org review |
| Twice a year | Performance reviews and calibration |
Protect thinking time: at least two blocks a week for strategy, writing and preparation.
Keep a lightweight system: one document per direct report (1:1 notes, goals, feedback, wins — useful at review time); one page of team priorities; a weekly update template.
Size the role: Will Larson suggests managers support six to eight engineers (Sizing engineering teams); far beyond that, the manager can only be a coach and safety net. If you have eleven, plan to add a lead or split.
What to say
To your teams in week one:
"Here's how I'll work: weekly 1:1s with each of you, a written update every Friday, quarterly career conversations, and I'll be in planning and retros every other cycle. If I miss any of these, call it out."
Trade-offs
- Rigid cadences can feel bureaucratic; adjust frequency per person and situation, but don't drop them silently.
- Weekly 1:1s for many reports consume a lot of time; that's the job — or a signal the span is too large.
- Delegating rituals to team leads frees time but needs regular check-ins on how they run.
Signals it's working
- Every report has a 1:1 at the agreed cadence.
- Planning, reviews and hiring steps start on time, every time.
- You have thinking time each week and use it.
- Your teams can predict when decisions and feedback will come.
Key points
- Run management from deliberate cadences, not the inbox.
- Put weekly, monthly, quarterly and half-yearly routines in the calendar; protect thinking time.
- Keep a simple system: notes per report, a priorities page, a weekly update.
- Watch your span: around six to eight direct engineers is sustainable for active management.
Practice questions
A new engineering manager's 1:1s happen irregularly and planning starts late. What's the fix?
Answer
Build an operating system of cadences — weekly 1:1s and updates, monthly metrics and skip-levels, quarterly planning and career conversations — in the calendar, plus protected thinking time and simple notes per report.
How many direct reports can an engineering manager actively support?
Answer
Around six to eight engineers, per Will Larson's guidance; much beyond that, the manager tends to become a coach and safety net rather than actively investing in each person and the team's area.
What should be in a weekly update to your own manager?
Answer
Progress against priorities, risks and what you're doing about them, people topics (hiring, attrition risk, wins), and decisions or help you need — short and in the same format each week.
Open in the app to mark lessons complete, take notes and track your progress.