Team doesn't have much impact -- considerations when switching

I think you should make the switch.

considering it would be my third move in a short time

To be clear, 2 of these switches were across companies, and this change (if you do it) would be within the same company. Is that right?

Transitioning within the same company is very different than a transition across companies. Team switches are less disruptive because:

• Your knowledge of scripts/tooling will carry over
• Your knowledge of company culture, and some work relationships, will carry over
• The company will want their top employees to work on the highest priority projects.
• External people will never have to know that you switched teams internally (that's your story to share).

As long as you somewhat trust your skip manager, I'd make the change. If the initiative is truly important, and the skip is good, they'll be a magnet for good people.

To clarify, I joined the company a few months ago. Then I was asked to switch teams internally after a month. Now I’d be switching teams internally again. But I agree with your points. Thank you.

If your skip is supportive, I would just do it if you really can't find a way to make your current team's work more fulfilling for you.

I'm really happy that you appreciated my post about handling ambiguity! There is some nuance there though as success depends on your personality, mentality, and progress towards senior (L5). Let's clarify with a story from my own past:

• I joined Meta as an E4 working on Portal
• Portal was everything you just described with your new org. Product definition was uncertain. Org structure was a mess and constantly mutating
• I had a hard time at Portal due to the chaos. I was able to get "Exceeds Expectations" (EE) both halves there, but I was so, so stressed. My ability to handle ambiguity wasn't anywhere near advanced enough for the colossal mess that was Portal execution. I was very reactive and non-assertive. I got EE because I wrote great code and reacted very well, not because I was demonstrating the leadership required from E5s
• Looking back, I would have really enjoyed working on Portal as an E5 or E6 (or at least an E4 that had made more meaningful progress towards E5). The ambiguity there means that scope was pretty much growing on trees. There were entire orchards of low-hanging fruit

All that being said, I didn't have Taro back when I was working at Portal. If I had Taro back then, I'm sure I would have made the necessary mindset shifts sooner (I mostly had the skills, it's just that the mindset wasn't there). So that's a huge advantage you have over past-Alex 😄

I'm going to make a course about L4 -> L5, but in the meantime, we have this: [Taro Top 10] Mid-Level Engineer To Senior Engineer (L4 To L5)

Thank you all for your advice! Turns out my manager wants me to do something different than what my skip suggested... but I'll make a new post for that.