Leadership8 min read

Engineering Management

Manage engineering teams through hiring, performance reviews, career development, process design, and building psychological safety.

managementleadershipteamhiring

Engineering management is the discipline of building and running high-performing engineering teams. Unlike technical leadership (what to build), management focuses on people systems: hiring, retention, performance, and culture.

Your job as an engineering manager is to maximize the output of your team, not your own. Remove blockers. Develop people. Build a culture of psychological safety, high standards, and continuous improvement. Measure team health, not just delivery metrics.

Workflow

Run structured 1:1s and provide continuous feedbackFeedback delayed to annual reviews is too late to course-correct; surprises in reviews indicate management failure.
Define and use a career ladderAmbiguous advancement criteria lead to perceived unfairness, disengagement, and attrition.
Build a structured hiring processUnstructured interviews introduce bias and poor signal; structured processes improve both quality and diversity.
Run effective performance reviewsInconsistent, surprise-heavy reviews damage trust and can trigger attrition spikes.
Build psychological safety and team healthTeams with psychological safety are 2× more innovative and significantly outperform on complex tasks (Google Project Aristotle).

Output Format

1:1 notes, career ladder, hiring scorecard, performance review template, team health survey results, development plans per engineer.

Examples

SBI feedback: "In yesterday's planning meeting (S), you interrupted Alex three times before they finished (B), which made them visibly hesitant to share ideas for the rest of the meeting (I). What was going on for you?"

Career ladder snippet: "L3 → L4: independently leads projects with 2-3 engineers, identifies and fixes systemic problems, mentors L1-L2s without prompting"

Interview scorecard: criteria rated 1-4 (strong no/no/yes/strong yes): problem-solving, communication, technical depth, growth mindset, values alignment

Edge Cases & Gotchas

High performer with low EQ: acknowledge the output, name the impact on team health, set concrete behavioral expectations-don't trade team health for individual performance
Quiet quitting: often a response to unmet expectations or lack of growth-diagnose root cause in 1:1s before jumping to PIP
Remote teams: over-invest in async documentation and deliberate social connection to compensate for lost ambient communication

When to Break These Rules

In seed-stage startups, the founder-engineer dynamic is different from mature EM roles-lighter process, more direct execution, revisit structure at Series A/B.

Reference Files

Camille Fournier "The Manager's Path": https://www.oreilly.com/library/view/the-managers-path/9781491973882/
Liz Wiseman "Multipliers": https://multipliersmindset.com/
Manager README template: https://managerreadme.com/
Rands in Repose: https://randsinrepose.com/