To me, that would just depend on your financial situation. I’m in that same boat where I love my job, people respect my skill, but my pay is quite quite terrible (“entry level” + contractor = poor).
I would NOT take that new job. It’s likely, since learning new skills, you wouldn’t be at a level to where you’d get the respect you command now. I’d just try to find a job which I can be of help to. Turn this one down (IMO) and keep searching.
Now, if you are making 60k and you are being offered 120, I dunno because I’d have a hard time turning that down.
If you are desperate for money, then yes I’d take the new job. I’m just talking from my own experience and I’m in a similar boat. So that’s how I’d handle the situation.
Good point. This position will not be for lead position as I’m not expert on those technologies. In fact, I’m quite surprised why they would reach me out. I wasn’t even looking for a job but I’ve known them (not the developers but the company). No clue on why they are desperately trying to recruit me… I’ve turned down multiple times until they gave me a number I couldn’t turn away.
Are they fully aware that you know almost nothing about these languages? You acknowledge you don’t know the languages but you haven’t said whether the company knows that.
If so, then I mean I’d talk to the developers and get a feel for the community there. No point going to a job where you’ll hate the people you work with. See if you can sit down with the team and just get a feel for how they are.
I’d almost ask them why they are so interested but perhaps that wouldn’t be wise since that might “wake them up” and get someone else.
I’d probably take it in a heartbeat. And I would put back at least 75% of my current salary for when the job doesn’t exist any more. Learning new stuff and furthering your skillset can only lead to being more employable and advancing your career.
With that said, I’d take it. The new company obviously values you, if they are willing to keep giving you an increasing number each time you say “no”. It is true you likely won’t be in a experience level and there will be people smarter than you (or know the new languages/tech better than you), but that’s more of a reason TO GO! You will have people you can learn from again.
I did this about 3 years ago and I don’t regret it one bit (I even had to move to a new city), but in the end it was worth it (and I didn’t get an offer of 2x my pay ;)).
As for the resignation, you simply tell them the truth. You maxed out on your potential for growth and you found an opportunity that will let you get to the next level.
All your assumptions are correct… The new work location is just 2 blocks away from where I work. The big difference is that they don’t have a gym…oh well… I can live w/o it. No doubt, I’m already packing for the new job (at least in my mind). However, I positioned myself w/ current project where I’m literrally the ‘leg’… w/o me there won’t be a progress… why? I’m the ONLY developer in the group…also our first release is coming up very soon… I’ll stay for the release but… on day 1…is when I’ll be out… I’m pretty sure we’ll have bugs and new features that need to be implemented… This is going to be quite rough for the team. Honestly, I feel like asshole at the moment…
More of a reason to have a talk with your boss sooner than later. If you are leaving, talk with him. Let him know that you want to see this through the initial release and be there to train anyone they hire to replace you (which means they have to act fast).
If you are staying, no need to talk with your boss, other than to catch up on things related to the project.
Okay, I’ll rephrase, have that conversation when you can, as soon as you can Nothing keeps a business relationship on good terms when leaving a company like open communication. If you don’t ever want to work at a place again, simply give poor communication about your leaving.