11–20 of 29 posts
Why not just start slacking off hard? What are they going to do, fire you?! You want to quit anyways. I would say do not quit before having another job. Most likely you will slack off and it will go unnoticed because the need to overwork yourself is in your head.
You will be extremely lowballed at any offer you get, with the company not willing to budge. I've personally seen this happen to several colleagues of mine. Even their recruiters just shrugged and said it was all they could get for them. Definitely start interviewing, but in order to do so you will have to stop working unpaid overtime for your company. Since you're already leaving anyway, promotions or looking to get…
Why not just start slacking off hard? What are they going to do, fire you?! You want to quit anyways. I would say do not quit before having another job. Most likely you will slack off and it will go unnoticed because the need to overwork yourself is in your head.
Why not just start slacking off hard? What are they going to do, fire you?! You want to quit anyways. I would say do not quit before having another job. Most likely you will slack off and it will go unnoticed because the need to overwork yourself is in your head.
Read my post about contract jobs if you do quit and have trouble finding something new.
Why not just start slacking off hard? What are they going to do, fire you?! You want to quit anyways. I would say do not quit before having another job. Most likely you will slack off and it will go unnoticed because the need to overwork yourself is in your head.
Ive seen people do this and it's actually healthier of an option
In 8 months you can certainly find another job, but more likely you’ll want to spend a little time decompressing. Don’t worry too much about it, software developers are still in very good demand.
At higher paying ones, you might have to do a HR filtering interview, code test, hour long chat with an engineer, a higher level manager, a whiteboard, another code test, and then present it to a panel which consists of four engineers... and possibly get rejected somewhere along this route. Some of the people in this process are not always there and they may not put hiring at first priority, so this can drag out very long.
If you have a "runway", you'll be under pressure to perform, which ironically might make you screw up somewhere along the process as I have before. It's so much easier just to settle for the lower paying job.
And as someone who has been on the hiring side, I've seen people who we wanted to hire, but failed because of this pressure. Two people who were going through extended interviews just refused to do an hour long coding challenge properly (they lazily copied something from SO which didn't answer the question). One interviewee snapped at the interviewer during the test. The process was also quite long because we didn't really need another person, so it took about 2-3 months to get back to the second guy we interviewed, who wasn't that qualified but better than the others.
However, if you're facing intense stress and burnout, the lower paying job might be a step forward.
I'm taking two days off at the moment. I woke up with the reality no one will contact me with an IT issue. My new life has it's pressures however I enjoy the less frantic environment.
Once you get get a job offer tell them you can't start for a month. If that's ok with them, accept and put in your 2 weeks, and get 2 weeks unpaid in-between jobs to unwind before starting your new journey.
The last time I switched jobs, I even negotiated a 3-4 weeks paid leave as I had PTO I wanted to take from my previous job, but they wanted me to start earlier than 1.5 months (the date I gave them mentioning I wanted to take my vacation at my old job). They hired me and let me take 3 weeks off after working for 2 weeks and it was all on payroll not affecting my annual PTO hours.