40 ice breakers and energisers for software engineering teams in the office — quick standup warmups, meeting openers, retro games, and all-hands activities that don’t feel forced.
8 tips for engineering managers working with product managers — shared priorities, healthy tension, and a partnership that ships without the blame game.
8 ways engineering managers can prioritize technical debt — sell it to product, pick high-leverage fixes, and stop the backlog from becoming a graveyard.
8 ways to coach senior engineers without micromanaging — grow scope, sharpen influence, and keep seniors challenged without treating them like juniors.
9 software engineering metrics managers should actually track — DORA-style delivery signals, quality, and health metrics that don’t turn into surveillance.
8 ways to resolve conflict on software engineering teams — technical disagreements, interpersonal friction, and how managers intervene without making it worse.
100 brilliant names for your software engineering team — agile, git, stack, and debugging puns that actually stick (and won’t make the exec team cringe).
7 tips for setting engineering manager OKRs that don’t suck — outcomes over output theater, team goals vs personal goals, and metrics you’ll actually use.
8 tips for managing remote software engineering teams — async defaults, trust without surveillance, inclusive rituals, and keeping culture from going quiet.
10 tips for your first 90 days as an engineering manager — listen first, map the system, earn trust, and ship small improvements without breaking the team.
8 ways engineering managers prioritize software engineering work when everything is urgent — impact vs effort, kill lists, saying no with options, and protecting focus.
25 engineering manager interview questions hiring panels actually ask — plus what strong answers sound like for behavioral, people, and delivery rounds.
Get 15 practical tips to ace your next engineering manager interview — story banks, STAR structure, underperformer answers, and what panels actually score.
9 software engineering retrospective tips — psychological safety, sharper prompts, action owners, and how to stop retching the same issues every sprint.
9 things every new engineering manager should know — from letting go of IC heroics to running 1:1s, feedback, and your first 90 days without burning out.