Join the discussion — anonymously
Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.
Comments (2)
That's a tough spot to be in. It's understandable to be excited about career progression and a title bump, but the 'catch-all' nature of the new team definitely sounds like a red flag, especially if there's uncertainty about long-term viability. Have you tried to get more concrete information about the specific projects this new team handles? Understanding the actual revenue impact or strategic importance could give you a better sense of its stability, rather than just relying on general perceptions. Maybe a direct conversation with the hiring manager about the team's roadmap and how it aligns with Splunk's overall strategy would be beneficial. Good luck weighing it out!
Honestly, it sounds like you're being tempted by a shiny object with a lot of potential downsides. 'Career progression' and 'visibility' are great, but if the team itself is unstable and houses 'projects on the chopping block,' that visibility might just be you being seen as the first to go when cuts happen. Your current role sounds stable, and that's incredibly valuable, especially in the current tech climate. Think about what truly matters: is it the title and perceived advancement, or is it job security and a known quantity? Sometimes the 'safe bet' is the smarter long-term play, even if it doesn't offer the same immediate glamour.