If so, what did you learn?
Have you ping ponged between being an individual contributor and being an engineering manager?
For further actions, you may consider blocking this person and/or reporting abuse
If so, what did you learn?
For further actions, you may consider blocking this person and/or reporting abuse
Mayu Hakim Watanabe -
Rick van den Broek -
keploy -
Ben Halpern -
Top comments (5)
Yes. I became an engineering manager at one company, then went back to being an IC at a different company. It was an interesting experience, as a manager had to deal more with the "human factor" of development and work and I really liked that. I will do it again in the future.
I'd say yes, though I've never officially been a "manager", I've had to do a lot of people management as "lead engineer" on teams that do not have a "manager" (and "manager" is sort of a dirty word where I work now - we don't have them, not officially anyway).
I've done performance reviews, led the standups, retros, made all the Jira tickets and epics, etc. While doing a lot of the coding too 😅Basically being "leader engineer" here means "lead engineer and also manager".
One thing I think I've learned is how to listen. Especially when people want to vent. People need someone they feel is safe to vent to. Then they need some help seeing the bright side. Sometimes, my natural instinct is to commiserate and say "oh yeah dude I totally hate xyz too, what a load of crud", but I don't think that's what they need to hear, they need some help seeing the positives, and looking beyond the immediate challenges.
I guess you could say: only complain upwards. I complain to my mentor, but I never complain to the people whom I mentor (even when I want to), that's not what they need from me!
Complaining upwards is a great piece of advice!
Are you working at an org with a flat structure then? How is that?
It's pretty flat. Technically we have titles but they're a little meaningless.
I think somewhat of a hierarchy has emerged anyway with three layers:
It can be a little chaotic, but I've also enjoyed that I can easily move around and do different things without bureaucracy and switching my job title. I wouldn't want to be a leader all the time, it's tough. I stay hidden in my code hole until duty calls and some project needs a lead engineer. Even when I'm in IC mode though I still do one-on-ones with people I used to manage, lots of code reviews, and there are often some quasi-management tasks that pop up here and there.
Very interesting, thank you for sharing. What would you say the biggest pain point or thing to watch out for with that structure is?