EM’s might also be technical but in a different domain. The question is how much the company values expertise in a specific technical domain or even tech stack, compared to people management, product sense, etc.
I am an engineering manager and this article has brought me a lot of wisdom. Thank you very much for sharing your knowledge. A sentence that impacted me, by reminding me of this wise principle, was: "The best managers are first engineers, then leaders. Not the other way around."
Nice! I agree with most of what you wrote. Many of the problems with large tech orgs would be solved if the highest levels of leadership remained knowledgeable of the tech. How can they do that when the footprint is very large? Any advice or resources to point to for that?
Thanks for the good article. I’m not an engineer but I understand what’s going on in the projects and I’m working on big software projects. What would be your advise for me, just exit the tech industry because only techies should stay their :)? Would love to discuss this with you. Cheers Hanif
Good reflections. The Staff figure is the one representing engineers in conversations of a bigger scope. Not someone to substitute the EM/PM. Not someone to dictate, but to enable
In our organization, the staff engineers are called ‘architects’, but it’s basically the same role.
I completely agree about the responsibility and division of work you suggested. As an EM, it’s MY JOB to lead and understand the technical aspects of my team’s work. There is no problem in delegating the technical design, but you should be the one taking the final decision, and in any case - fully understand what and how it’s going to be implemented.
Thanks for this great article Alex, and thanks for the mentions.
I don't think we necessarily disagree on the topic of coding. Staying technical involves a lot more than just coding. An EM should have a solid technical background - and I mean it when I say solid - but should also be able to give up their attachment to the code and move on to other aspects: architecture, planning, etc.
And as you also mention, if prefer the approach of occasional Engineer-ications as they allow the Manager to fully focus on that specific task for a week, get a real understanding of what is going on with the team and tooling, and then take initiative out of those learnings. I see this as a much more deliberate, disciplined, and effective approach than just picking some random tasks every now and then just because "you can".
Ultimately, this is a hot topic, and the pendulum keeps swinging back and forth when it comes to the general sentiment in the industry. Definitely a subject to follow and be open-minded about
In your opinion, how do you feel about a data manager/lead becoming CTO of an org? Does such a person have enough technical experiences to adapt into that role?
I have a specific person in mind: Elizabeth Stone who recently transitioned from VP of data into a CTO at Netflix.
How "engineering" be "non-technical"? My jaws dropped reading through....
EM’s might also be technical but in a different domain. The question is how much the company values expertise in a specific technical domain or even tech stack, compared to people management, product sense, etc.
I am an engineering manager and this article has brought me a lot of wisdom. Thank you very much for sharing your knowledge. A sentence that impacted me, by reminding me of this wise principle, was: "The best managers are first engineers, then leaders. Not the other way around."
Nice! I agree with most of what you wrote. Many of the problems with large tech orgs would be solved if the highest levels of leadership remained knowledgeable of the tech. How can they do that when the footprint is very large? Any advice or resources to point to for that?
Thanks for the good article. I’m not an engineer but I understand what’s going on in the projects and I’m working on big software projects. What would be your advise for me, just exit the tech industry because only techies should stay their :)? Would love to discuss this with you. Cheers Hanif
Good reflections. The Staff figure is the one representing engineers in conversations of a bigger scope. Not someone to substitute the EM/PM. Not someone to dictate, but to enable
In our organization, the staff engineers are called ‘architects’, but it’s basically the same role.
I completely agree about the responsibility and division of work you suggested. As an EM, it’s MY JOB to lead and understand the technical aspects of my team’s work. There is no problem in delegating the technical design, but you should be the one taking the final decision, and in any case - fully understand what and how it’s going to be implemented.
Thanks for this great article Alex, and thanks for the mentions.
I don't think we necessarily disagree on the topic of coding. Staying technical involves a lot more than just coding. An EM should have a solid technical background - and I mean it when I say solid - but should also be able to give up their attachment to the code and move on to other aspects: architecture, planning, etc.
And as you also mention, if prefer the approach of occasional Engineer-ications as they allow the Manager to fully focus on that specific task for a week, get a real understanding of what is going on with the team and tooling, and then take initiative out of those learnings. I see this as a much more deliberate, disciplined, and effective approach than just picking some random tasks every now and then just because "you can".
Ultimately, this is a hot topic, and the pendulum keeps swinging back and forth when it comes to the general sentiment in the industry. Definitely a subject to follow and be open-minded about
What an incredibly insightful post.
In your opinion, how do you feel about a data manager/lead becoming CTO of an org? Does such a person have enough technical experiences to adapt into that role?
I have a specific person in mind: Elizabeth Stone who recently transitioned from VP of data into a CTO at Netflix.