Why Bad Jobs-or No Jobs-Happen to Good Workers
spectrum.ieee.org
Why Bad Jobs-or No Jobs-Happen to Good Workers
1–10 of 80 posts
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#2Shorter version:
If you want experienced, wildly competent workers, you'll have to pay for them. If you're not willing to pay for the experienced workers, you'll have to train inexperienced workers. Also, the requirements you're listing for the job is probably ridiculous, and your screening process is probably broken.
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#3I think this all goes back to the fact that wages are stagnant for most of the world, and companies don't foster employees anymore.
You need to cultivate experience in workers sometimes, especially if you have a complex system in place.
Employees have no loyalty anymore, because of the cutting of benefits and wages.
Employers have no loyal employees anymore, which means they require 3 to 5 years experience to give them some return on hiring said employee.
Students are having a hard time finding work, because Employers are requiring this experience.
Employers have a skills gap, because they can't hire Students to fill the gap, because they'd just quit before giving some return (loyalty).
I think I'm starting to see the clusterfuck caused by limiting compensation and benefits...
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#4I landed a great programming job with no experience and no degree because I could walk in there and talk about what I had taught myself and done on my own time. I know this doesn't transfer to every situation in every industry, but I think much of the problem stems from people who haven't put in much effort to make themselves marketable and to educate themselves. If I saw that, I would make the assumption that the company could spend money training them and they wouldn't necessarily come away a harder-working, more motivated person.
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#5I landed a great programming job with no experience and no degree because I could walk in there and talk about what I had taught myself and done on my own time. I know this doesn't transfer to every situation in every industry, but I think much of the problem stems from people who haven't put in much effort to make themselves marketable and to educate themselves. If I saw that, I would make the assumption that the co…
Same here.
The issue with most people is that "you don't know what you don't know", coupled with the fact that most still have the idea that college/on the job training will suffice, while many companies are no longer providing training.
It takes a specific mentality to take the time to learn a craft with little to no immediate benefit in sight--you see this in other fields too, but they're not the norm.
The question is, do we try to change our culture to generate more self-starters, or do we change the institutions that need skilled labor?
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#6I landed a great programming job with no experience and no degree because I could walk in there and talk about what I had taught myself and done on my own time. I know this doesn't transfer to every situation in every industry, but I think much of the problem stems from people who haven't put in much effort to make themselves marketable and to educate themselves. If I saw that, I would make the assumption that the co…
Sounds like you did have experience: stuff you had done independently. More and more that's becoming a requirement to get a good job out of college, at least in certain fields. Combined with your ability to speak intelligently about that experience, it sounds like the hiring decision was pretty easy. What I've found more common, is recent graduates who expect their degree /alone/ will get them a great job out of college, and that's becoming more and more difficult.
Edit: After reading my comment, I don't think I made it clear enough that I'm agreeing with your point about people not marketing or educating themselves adequately. After spending 4 years in college, I think a lot of people expect to show up at a job interview, show the interviewer their degree, and get a job. The reality is obviously quite different.
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#7I think this all goes back to the fact that wages are stagnant for most of the world, and companies don't foster employees anymore. You need to cultivate experience in workers sometimes, especially if you have a complex system in place. Employees have no loyalty anymore, because of the cutting of benefits and wages. Employers have no loyal employees anymore, which means they require 3 to 5 years experience to give th…
I'm just an employee, but if you want to gain my loyalty, just throw some benefits and wages at me. Cycle avoided.
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#8Shorter version: If you want experienced, wildly competent workers, you'll have to pay for them. If you're not willing to pay for the experienced workers, you'll have to train inexperienced workers. Also, the requirements you're listing for the job is probably ridiculous, and your screening process is probably broken.
Soon as I graduated I encountered the experience wall - it was ridiculous. "junior" level positions required 2-3 years experience and paid less then working at Walmart.
Now that I have over 5 years experience in my field, I'm rolling in offers and have my pick.
I've had managers complain about lack of loyalty in employees. I typically fired back suggesting that if you take new graduates out of school and actually invest in them, you'll have a much stronger core workforce that is likely far more invested into the company then random mercenaries you pick off the market. Apparently I don't get management theory though...
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#9The unstated counter-argument is that the employer will have to train inexperienced workers who will leave as soos as they become competent and experienced, or pay as much as you would for the experienced person in the first place.
Myself, I'd rather train someone up in my process without them learning bad habits, even if that means they're pairing with me for 30 hours out of 40. That said, I'm an exception.
Once upon a time, some companies hired new workers as QA, trained as QA, and those with the aptitude were moved into programming. I know that IBM still has an internship program that streams people into their system.
Re: Why Bad Jobs-or No Jobs-Happen to Good Workers
#10The unstated counter-argument is that the employer will have to train inexperienced workers who will leave as soos as they become competent and experienced, or pay as much as you would for the experienced person in the first place. Myself, I'd rather train someone up in my process without them learning bad habits, even if that means they're pairing with me for 30 hours out of 40. That said, I'm an exception. Once upo…
If people leave after training then that's a retention problem and has nothing to do with how skilled they where when they started. And yes, giving a 22 year old tech worker a 25+% raise might seem crazy, but if you want to keep up with their increase in value you have to consider such things normal.