Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "jumping ship"
-
Flexible working hours, Home Office, fair compensation, working on a greenfield product 🥰.
I was in a bad spot two years ago jobwise and I don't regret jumping the ship for a second.
I would never have guessed that flexible hours and WFH would be so beneficial to my mental health!
Not everything is perfect all the time, but it gets pretty damn close all things considered.3 -
Shit will hit the fan pretty soon. We're understaffed, the team is all talking about jumping ship and all other teams rely on our work, so if we jump ship, it sinks. It's really amazing that management is unaware or choosing to actively ignore the possibility. Either way, they're fucking up big time. Honestly, if it happens, it will be well deserved, it just sucks for everyone else working under them4
-
Suddenly, I find myself in a crossroad situation. I have been offered a position which would align perfectly with my career path aspirations (cloud solutions architect) with double the pay to my current salary. If only those were the only variables in this equation, taking the offer would be a no-brainer. Alas, it is never that simple (unless all you care about are pay and career path, of course)…
So, let’s break it down to pros and cons of jumping ship, shall we?
Pros:
- double pay compared to current salary
- aligns with my career aspiration
- part of a team of cloud solutions architects (mentorship opportunities)
- varying projects (position is at a consultancy firm)
- shares of the company come with the position ($$$ if it grows)
- possibility to influence strategic decisions
- no more 2h+ commutes
Cons:
- it’s a consultancy startup (emphasis on both consultancy and startup)
- 100% wfh
- would mean losing my current team where we are well and truly glued together and have such great vibes (and I value this, very very highly - this really is the main con)
- would mean losing my current work environment, where we have a gym and sauna at the office etc all kinds of stuff that support my athletic lifestyle
- would mean I don’t have as many opportunities to visit my parents anymore (since they live close to my current office but not close to me)
- at my current position I have super interesting projects both ongoing and in the horizon for a long time to come
- would mean eating my words (see previous point, and the fact I’ve said to my TM ”I can see myself staying as long as this job offers me opportunities to keep learning skills that are meaningful to me”), and I value my integrity
- would mean leaving my colleagues in quite a hairy spot, effectively betraying them in my mind (when our lead dev jumped ship a few years ago, he left us in quite a limbo and hands full of shit we didn’t know what to do about… I don’t wish that situation for anyone)
So, to sum it up, my reasons to stay are more those of moral integrity and convenience, well as the will to see the wheels I got rolling to the end, whereas my reasons to go are more personal finances and career oriented. A difficult decision. What to do?14 -
Be me, a ret***
Already 3 months in a new position. (check my previous rant)
Storm have passed for a while but another storm is brewing.
C levels are having disagreement with each other.
Caught in the crossfire as one the of C's hire.
Have some chit chats with both side of C, each telling different stories.
C#1 told me there was a demand from C#2 to force tech guys (not defined who or how many) to resigns.
C#2 told me there is no plan to close the whole tech team. But there's a distrust brewing in the tech team especially on the C#1
Be me, C#1 hire...
Me telling them IDK what their real intentions are but there's a high probability for my reputation to be tarnished on the job Market.
I've always had good review amongst peers and confident I did and do a satisfactory job for my previous employer.
Be me:
Resorted to flexing my connection to high ranking (think of C suites) reference who I've worked and have good relations with.
Connected them to my C#2.
Dunno how the C#2 thinks of me and what my value to C#2 are.
Don't know what the future hold for me.
Tried doing one interview but topics of my reputation comes up because of me jumping to executive position without having "Manager" ever in my resume.
Got a bit too defensive on that and it might eff up my chance to have a backup ready in case I urgently need to jump ship.
Depression and impostor syndrome hits like a truck every day.2