Thoughts on 'bullshit' jobs? (getting paid for not working?)
No Big N 400k salary goals here.
I'm talking about coasting-jobs - administrative bloat, poorly allocated govt funding, the ones where you might do some minimal hrs/week remotely on a full-time salary, or outsource 90% of the role.
The biggest pay:workload ratios (with a priority on low workload over high pay), no fulfilment/job-satisfaction necessary.
Do these exist or are they unicorns? Are they all they're cracked up to be? Can they be targeted as a profession, and if so, what would be your strategy to speedrun from 0xp into a career in one of these roles?
unnecessary personal context - i'm a data/coding nerd whose initial career-plan was the standard SWE route.
record scratch, and i've found myself in a different profession that's intrinsically rewarding but also high-effort+low-compensation.
So a CS job that's the opposite of that -- a high-compensation+low-effort 'coast'-- is a nascent 'plan-b' that might be useful if/when I eventually burnout on my current path.
Posted Sep 14, 2022, 9:14 AM UTC
I've had a job like you're probably describing. If you just wanted to coast and do extremely little, you could do that. However, like the other poster mentioned, you're going to have a persistent feeling that the gig could be up at any time. If you're in the office it's going to be even worse because you will undoubtedly attract attention from coworkers and managers by way of your physical presence. You could get lucky here, though, and nobody could care.
If you use the time to keep your interview skills fresh and grow your coding skills you could definitely use it as a stepping stone to a sweet spot where you make good money, you have a reasonable workload, and your coworkers are great. Having, say, 25 hours per week, every week, to focus on this without having to spend that time fighting some legacy codebase or doing rote tasks that don't improve your skills will be a golden opportunity.
However, if you coast and do next to nothing you might suddenly find yourself unemployed and playing catch up to get any job, of which you wouldn't be able to be picky.
Good points. Out of interest, what was your job like- the one that you mentioned at the start? How did you get into it, and you use it as a stepping stone?
I got "lucky," as I had no idea coming in and there were some personnel shifts (retirements and resignations) that enabled this. Everything was totally outside of my control and I truly fell into it.
The job was, honestly, a disaster. I had to sit in a small office with a team lead's son who would enter fits of autistic rage if the lights were on so it pitch black. He also knew EVERYTHING and I got to hear about it. And his nascent streaming career, despite having zero personality. I found out this guy had drove several people to resigning, as everyone who was forced to sit with him resigned within a few months.
Their processes were also a dumpster fire. Our daily scrum was at least 30 minutes because "while I have you all I should make it worth it." It would frequently exceed 45 minutes and had on a handful of occasions come close to 2 hours. Our appointed "scrum master" had some sort of dyslexia and we would watch her type updates/notes on JIRA tickets as we sat there. A single sentence could be a 2-3 minute endeavor.
It drove me nuts and I had to move on ASAP. Just be aware that bullshit jobs will very likely be a double edged sword - if everything is going smoothly you're not going to have bullshit jobs. I did not have the foresight to take full advantage of it as I was still much earlier in my career. Sitting in pure darkness, listening to the SME's SME lecture me on every topic, and sitting through marathon meetings was too much for me.