fortinet in  
Software Engineer a month ago

Insights on Transitioning to a Managerial Role from Tech Lead/Architect

Hello folks,

Hope you're all doing well! I find myself at a crossroads in my career and would greatly appreciate your valuable insights.

I currently hold a Tech Lead/Architect role with approximately 11 years of backend-heavy experience. I've been presented with the opportunity to transition into a managerial position from an individual contributor (IC) title. I'm in a bit of a dilemma as I don't have strong inclinations either way(accept or decline) and would like to weigh the pros and cons.

Some background, In my current project, I'm already overseeing team tasks, running sync-ups, and managing to find some time for development alongside design and reviews. Some colleagues believe I could make a good manager, citing qualities such as being easy to work with, having a developer's heart, and a keen understanding of individual differences and abilities, which I strive to balance effectively.

While I'm neither overly excited nor opposed to this transition, I am leaning towards the advice of "If in confusion, go for it." I'm curious to hear about your thoughts, experiences, and insights on making such a transition, considering the current market trends and growth.

Looking forward to learning from your perspectives!

19g615kyyk9yt1Software Engineering Manager a month ago
I transitioned from an IC to Manager few years ago. It’s only worth it if you really believe in advancing people’s careers more than yours. Setting up people for promo means literally you are planning their promo and aligning the right opportunities for them. Then it’s a different ball game fighting for that with Senior Management. Be ready for all that and then think about transition. IMHO being IC means you mostly control your destiny unless there are major **ck ups by managers. Being manager means you are managing up and managing down and your team will play a huge role in your destiny.



Software Engineering Manager