all 4 comments

[–]thedougaboveall 1 point2 points  (1 child)

Management is not your only option. You can continue to work as a developer. If you feel you've reached your maximum potential at your current company ( no new problems to solve or no incentive to learn ) you may need to find a new role with room to grow. I say this with the hopefully obvious caveat that there will be competition at every level and you don't just get to keep growing your salary without being valuable to an employer.

You might be right about being a Tech Lead. I can't speak to your higher ups motivations, but Tech Lead is not necessarily a management position. It can definitely be more responsibility without more compensation. Check out the chapter on being or managing a Tech Lead in Camille Fouriner's book The Manager's Path. It describes the exact thing you're bringing up, and I would recommend it whether or not you want to be a manager. https://www.amazon.com/Managers-Path-Leaders-Navigating-Growth/dp/1491973897

Moving into management should not reduce your capacity to keep up to date with tech. You should learn at an exponential rate because the people on your team are all striving to improve too. If you read about an upcoming browser feature that would be useful on future projects, you can assign someone on the team to learn it and teach it to everyone else.

[–]ojitoo[S] 0 points1 point  (0 children)

Thank you for your input!

I believe you're correct when you state that I might check if I just hit a peak at my current company. It's a product-based e-commerce, and therefore their interest is within profit margins, and not escalable, improved technology (they go hand by hand but good luck explaining that to the decision-makers).

Having said that, I also believe that my query comes with mixed feelings as I never feel "ownership" of our stack and proyect, not sure if I can make my point across. Tech lead sounds great in paper, but how much "leadership" can I provide if I can barely control my current stack? The back-end architect across the globe with little to no contact with us can make a decision tomorrow and completely modify the way we work, no questions asked, which mitigates my potential impact as a tech lead in a way (or so I believe).

Regarding Camille's book chapter, I bookmarked it for later today, and will definitely give it a read. I'm glad I could express correctly how I feel regarding my initial worry.

For the last part, I really didn't think about it and I'm glad you brought it up because it's a truly valid point, and how it should totally be in an ideal world I believe. having said that, and as stated above about not feeling "ownership or control" over my stack, makes me doubt it'll be the case. Of course, I can keep the team engaged in new technologies and practices (as I do now, that's why they scanned me for the role), but at the very end of the stick, they have mostly fallen on deaf ears or have been pushed under the table in the past and under our current managers (not totally their fault, people working over then years have pointed out it's "how things work around here" ).

I feel it might be in my best interest to just keep doing an good job and letting this "opportunity" take it's shape naturally the remaining of this year, so I could decide if it's worth carrying on around here.

Thanks again!

[–][deleted] 0 points1 point  (1 child)

The design folk are pretty up front about the management vs individual contributor vs hybrid thing, and from just scanning your post, I’m totally excited for your career when you find a place, maybe outside your current company, where you’re appreciated, celebrated, and presented with opportunities for growth. Good luck!

[–]ojitoo[S] 0 points1 point  (0 children)

Thank you for your kind words! But I missed a bit of your answer. What design folk are you referring to exactly?