Software Engineer or Manager? Things to Know Before Making the Switch

Summary

In this insightful video, the speaker shares their personal journey transitioning from a Software Development Engineer to a Software Development Manager and back again. They delve into the decision-making process, the stark differences in day-to-day responsibilities, and the pros and cons of each role. Highlighting the importance of team culture, the challenges of constant interruptions, and the loss of hands-on technical work, the speaker provides valuable insights for those contemplating a similar career shift. Their experience underscores the value of trying different paths to understand one's true passions and the significant growth opportunities that come with stepping out of one's comfort zone.

Takeaways

• 😀 The speaker transitioned from a software development engineer to a manager and then back to an engineer, providing insights into both roles.
• 🔧 There are two ways to become a software manager: directly request the role or take the lead in a team without a manager, demonstrating management skills.
• 🏗️ The speaker's transition into management was natural, as they joined a team in need of organization and process building.
• 📚 The importance of training and resources was highlighted, including company-specific training and the book 'Managing the Unmanageable'.
• 🌐 A manager's day is filled with meetings and interruptions, contrasting with the focused, uninterrupted time an engineer might enjoy.
• 💼 The role of a manager involves mentoring, developing team culture, and balancing technical roadmaps and priorities.
• 🚧 The speaker felt a loss of technical depth as a manager, which was a significant drawback for them due to their passion for technology.
• 🤝 A key part of management is achieving through others, which requires building a strong team and fostering collaboration.
• 🔑 The speaker realized their passion for technical work after an intense hour of problem-solving, which was more satisfying than their managerial duties.
• 🔄 The transition back to an engineer was a gradual process to ensure minimal disruption to the team.
• 🛑 The experience as a manager provided the speaker with valuable skills and clarity on their career preferences, despite the challenges.

Q & A

What was the individual's initial career transition from software development engineer to what role?

The individual transitioned from a software development engineer to a software development manager.

Why did the person decide to switch back to their previous role as a software development engineer?

The person switched back because they missed the technical aspects of software development and felt more passionate about it compared to the managerial responsibilities.

What are the two general ways to become a software manager according to the script?

The two general ways are either directly requesting the role from your manager or by taking the lead in a team without a manager and doing the tasks that a manager would typically do.

What was the individual's approach to stabilizing the team they joined as a manager?

The individual focused on setting up processes, such as regular sprint planning and being accountable for time spent on tasks, to build a culture and community within the team.

What challenges did the person face when transitioning to a managerial role, especially during COVID?

The person faced challenges like building team camaraderie without in-person interaction, maintaining team culture, and dealing with the absence of large blocks of uninterrupted time for deep technical work.

What type of training did the individual undergo to prepare for the managerial role?

The individual underwent extensive training provided by their company, which included many hours of resources to understand what it means to be a manager at Amazon.

How did the person describe their day-to-day experience as a manager?

The day-to-day experience as a manager was filled with meetings, stakeholder management, and less time for deep technical work, which was a significant change from their previous role.

What was the individual's realization about the importance of team culture in their role as a manager?

The individual realized that building a healthy team culture was crucial for success, as the manager's effectiveness is directly tied to the team's performance and ability to work collaboratively.

What was the 'inflection point' that led the person to reconsider their career path as a manager?

The 'inflection point' was a moment of intense frustration during a series of unproductive meetings about a technical solution, which led to the realization that they missed the technical depth and problem-solving aspects of software development.

How did the individual's experience as a manager impact their current role as a software development engineer?

The experience as a manager provided valuable insights into people management, communication, and empathy, which have been beneficial in their current role as a software development engineer.

What advice does the individual offer to others who are considering a transition from an individual contributor to a management role?

The individual advises others to try the management role to gain clarity on their preferences, as they believe the experience can provide valuable skills and insights, even if they ultimately decide that management is not the right path for them.