Experienced Devs

4000 readers

1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

[email protected]

Is it normal to be sent to another team? (programming.dev)

submitted 2 years ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

I am normally a helpful person who dives in to help, but when it comes from above that I'll be switching teams with no warning, it robs me of my autonomy, my investment in my team and product, and makes me feel like even more of a cog. Yes, it's good to broaden my experience, and maybe if it was handled better it would have felt better. But my job isn't just coding, it's social skills and research and all of that. Especially in the remote environment, it's hard. So this does feel bad.

Our product team failed to pull together a clear path forward, so I understand why this is being done, but it is still alienating. Is this a normal thing to expect in future roles?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 2 years ago

It really depends on the company. I'm in upper management and have had to move ICs within org and across org to account for ET level strategic changes. It doesn't happen often at my company, but it's never easy for the folks who end up getting shuffled; when reorging, you really want to move teams, not people. You can tell a lot about your leadership on whether or not they acknowledge the impact on people's lives; high EQ is incredibly important for long term happiness of your teams and that starts with empathizing with your teams when decisions are made.

It sounds like your product team had mission/roadmap issues. You can absolutely expect teams that are unable to find consensus in a direction within team or with senior leadership to be put on a clock before they're material impacted. Similarly if they are unable to produce value with their roadmap. You will be on teams like this in the future as well.

All this is to say that it should be a rare occurrence in general, but often enough in your career you'll get familiar with the process. I have noticed companies which are struggling are more prone to the shuffle.

I do want to say this change, while disruptive, can present new opportunities. You've already called out the importance of the role extending beyond coding which is wonderful to embrace. It's relatively easy to work with long established colleagues and typically miles harder to build a rapport from scratch with a new team. Getting good at meshing/norming with new people is a critical skill for everyone to develop and will pay dividends at many junctions in your career. Similarly, exposure to new ideas and thinking can help break up echo chambers which all of us seem to run into at one point or another. If nothing else, you'll learn a lot about how orgs influence outcomes and how investments are made (whether you agree with their decision making or not.)

Good luck!