This article shares hard-earned truths for engineers becoming managers. It covers the shift from teammate to authority, handling stress and sensitive information, mastering feedback and networking, and staying effective amid meetings and politics. It ends with tips on training yourself, managing up, and finding peer support.

• Management means carrying others' emotional burdens home constantly, with no relief valve—you lose peer status and get excluded from gossip/casual moments once you hold authority over pay and firing decisions
• Your words carry outsized weight now (jokes read as orders), so managing what you say and don't say becomes a core skill, especially when you must sell decisions you disagree with
• There's no formal training for management—you have to self-teach labor law, feedback, and coaching by finding mentors, HR contacts, and peer groups on your own
• Progress feels invisible compared to engineering's quick wins, so you have to manually create milestones and celebrate small victories to stay motivated through months-long objectives

To secure a promotion, proactively take on responsibilities associated with the role you aspire to, even before receiving the title. Consistent, sustained performance and ownership of broader team issues are key, demonstrating capability and readiness for advancement.

• Act like you already have the next-level role by taking on its responsibilities before getting the title or promotion
• Consistency over time matters more than a single impressive moment—sustained ownership proves readiness
• Look for gaps or broader team problems no one owns, and step in to solve them rather than waiting to be asked
• Making yourself hard to replace in a higher role (i.e., someone would struggle to "take your position") signals you're already operating at that level

Phil Eaton recalls how a junior developer at Linode, Drew DeVault, used clear logic and dogged persistence to reshape the engineering team’s architecture and decision-making culture. Eaton learned that you don’t need seniority to drive change—you need preparation, the will to debate, and the judgment to know when to push and when to let go.

• A junior developer with no formal authority (everyone was titled "Developer") reshaped Linode's entire engineering architecture and culture through logic and persistence rather than seniority.
• Influence comes from preparation, sticking to your argument, and acting in good faith—not from waiting for permission from senior colleagues.
• Without someone willing to push back, teams drift toward popular or easy decisions instead of smart ones.
• Pushing too hard has real costs—Eaton's own overly aggressive advocacy once drove teammates to quit, teaching him when to press an argument and when to let go.