xsevensinzx (5/3/2016)
Hey guys,Need some advice. I got a really good job offer recently to work at a company as a DBA. I'm currently a data architect that built and manages a data warehouse for a analytics team. I'm kind of their only tech resource and everything is sort of tied into what I do regardless of my suggestions to hire redundancy for me.
I'm struggling to leave the business hanging, but I'm generally becoming unhappy due to a number of things that likely won't get fixed from a management standpoint. So, I'm kind of forced to seek opportunities elsewhere to continue my growth in my passion for data. Yet, I'm seriously guilt tripping a lot on the impact of that decision.
Any advice from those of you who have left mid-project or sunk a lot of passion/investment into a organization, idea, team and still had a difficult choice of moving on would be much appreciated.
I'm a little late chiming in here but you've gotten some good advice already.
One thing that doesn't seem to have come up is what looks like a drastic change in your job functions. You're going from an architect position to an administrator and those are very different roles. You need to figure out what you like about being an architect, what you don't like, what you hope to achieve as a DBA, and what appeals most. It's more than just a job hop here.
If your current job hasn't given you adequate backup and resources in case you're not available then they're on the hook for keeping things running. You flat out said that you've hit the ceiling and walls regarding what you can do there so you're going to leave. Loyalty is great and keeping your baby running is always something we want to do.
Consider all the aspects and decide if the DBA job is where you really want to go or if you want to expand your role in another company. Because you are leaving.