Asked to make a tough choice with reorg - move out of org or stay in current org and give up scope

Question

Put on an exciting Staff level project for the last 6 months. Now, asked to make a tough choice - move out of Org or stay in current Org and give up scope.

Pros of moving:

Scope: getting multiple jr level engineers to carry out the scope I created.
Exciting product.

Cons of moving:

Current manager turned down the scope expansion.
Have built relationships within current team. Enjoy working with them (more familiar)
Less depth AI/ML work but more product heavy (which is high impact as well but slightly less interesting from ML standpoint)
Lots of unknowns with new team - unknowns beyond staff scope IMO

TLDR; What would others in the same situation recommend? From taro courses, Option 1 seems better. But there are unknowns especially with current manager refusing the offer.

Alex Chiou · Accepted Answer

It feels like going to the other org is better. You have 6 months of signal working there, so I'm sure you have a good handle on the quality of its team and scope. When going from senior to staff, you need to be very particular about the team you work on:   It does suck that your manager seems to be unsupportive of the move though. In general, manager relationships are very valuable, so hopefully you can maintain it and not burn any bridges. Here's a good thread about this: How can I gracefully leave my job?  Best of luck!

Asked to make a tough choice with reorg - move out of org or stay in current org and give up scope

Discussion

Other Great Discussions

How possible is it to spot red flags about toxic culture during the interview?

Is it worth transitioning to become a Machine Learning Engineer?

Does it make sense for me to choose a specialization like ML? If so, what's the impact?

Looking to transition to ML Engineer? What do you want to know?

How does Stack Ranking work (at FAANG) and how can I be proactive at a base level?