First-Time Engineering Manager Survival Guide at a Startup
Transitioning from an individual contributor (IC) to an engineering manager is one of the most challenging yet rewarding career moves a developer can make. At a startup, this transition is often accelerated, throwing new managers into the deep end with little to no formal training. If you're a first-time engineering manager at a startup, this guide is for you. We'll cover the essential skills and mindset shifts you need to not only survive but thrive in your new role.
The Mindset Shift: From Maker to Multiplier
The biggest challenge for new engineering managers is letting go of the "maker" mindset. As an IC, your success was measured by your individual contributions: the code you shipped, the bugs you fixed, and the features you built. As a manager, your success is now measured by the output of your entire team. Your role is to be a "multiplier," enabling your team to be as effective as possible.
This means you need to resist the urge to jump in and code every time there's a problem. Instead, your focus should be on empowering your team to solve problems themselves. This can be a difficult transition, especially if you're used to being the go-to technical expert. But it's crucial for your success as a manager and for the growth of your team.
"Your new job is not to be the best engineer on the team, but to make every engineer on the team better." - A wise engineering leader
Prioritizing Your Time: Coding vs. Managing
One of the most common questions first-time managers ask is, "Should I still be coding?" The answer is: it depends. In an early-stage startup, you might still need to contribute to the codebase. However, your primary focus should be on your managerial responsibilities. A good rule of thumb is to spend no more than 20-30% of your time on individual technical work.
Here's a breakdown of how you should be spending your time:
- People Management (40%): One-on-ones, feedback, career development, and team building.
- Project Management (30%): Planning, prioritization, and ensuring your team is working on the right things.
- Technical Leadership (20%): High-level architecture, code reviews, and technical guidance.
- Individual Contribution (10%): Coding, bug fixes, or other technical tasks.
Building Strong Relationships with Your Team
Your relationship with your team is the foundation of your success as a manager. Take the time to get to know each of your direct reports on a personal level. Understand their career goals, their strengths and weaknesses, and what motivates them.
One-on-one meetings are the most important tool for building these relationships. These meetings should be a dedicated space for your direct reports to talk about whatever is on their mind, whether it's a technical challenge, a career question, or a personal issue. As a manager, your role is to listen, ask thoughtful questions, and provide support.
The Art of Effective Feedback
Giving and receiving feedback is a critical skill for any manager. At a startup, where things are moving quickly and constantly changing, regular feedback is essential for keeping your team on track. When giving feedback, be specific, timely, and focus on the behavior, not the person. The "Situation-Behavior-Impact" (SBI) framework is a great tool for structuring constructive feedback.
It's also important to create a culture where feedback is a two-way street. Encourage your team to give you feedback on your performance as a manager. This will not only help you grow as a leader but also build trust and psychological safety within your team.
Navigating Pressure and Uncertainty
Startups are inherently chaotic and unpredictable. As a manager, you'll be shielded from some of this chaos, but you'll also be responsible for shielding your team from it. It's your job to create a sense of stability and purpose for your team, even when things are in flux.
Be transparent with your team about the challenges the company is facing, but also be optimistic and confident in your team's ability to overcome them. Celebrate small wins, and don't be afraid to be vulnerable and admit when you don't have all the answers.