Earlier quoted context omitted.
Agreed, sometimes people aren't aware that HN is its own little echo chamber. I was talking to a recruiter recently for a managerial job and somehow got onto the topic of hiring. I asked him what's the hardest jobs for him to fill right now. He told me he's dying for entry level .NET/ASP and Java developers. Corporations have built their castles on these technologies, not FOSS/Mobile and need staff. Degrees were an i…
> He told me he's dying for entry level .NET/ASP and Java developers. How many years of experience and how much demonstrated expertise did he require from these" entry-level" candidates that he supposedly can't find?
The Unemployable Programmer
271–280 of 464 posts
Re: The Unemployable Programmer
#272Earlier quoted context omitted.
I'd say it goes deeper than this: there's a greater emphasis today on the candidate being productive from day one. I don't know what is causing it (too much exposure to efficient software?), but in many industries hiring managers would rather keep looking for an absolute perfect candidate while leaving behind several that have the skills but need the training. I have heard the stories about managers spending 100 extr…
> I'd say it goes deeper than this: there's a greater emphasis today on the candidate being productive from day one. Which drives me crazy. Nobody can be truly productive on day one. You have processes to learn, even if it is just an informal "way we do things". You have existing code to become familiar with. You have team dynamics to work into. It takes time. Personally, I cringe whenever I read a job advert mention…
The best description I've heard is that it's a spectrum from "100% training provided" to "productive on day one." Older recruiters tell me that decades ago the spectrum was too far in the other direction -- willing to hire anyone, and piling on the training. But now it's too far the other way, dropping good candidates who aren't able to perform independently on day one.
Re: The Unemployable Programmer
#273Going mainstream implies major changes, which are not technological, but still exclude many players because big corporate players bring immense business differences.
To be honest, skill and intelligence never mattered when it's about success. Humans want to be happy, technological progress interests nobody. That's where the "overskilled" comes from.
Re: The Unemployable Programmer
#274Earlier quoted context omitted.
> This is an absolutely baffling article. The job market for developers is not glutted by over-supply, it's one where marginally-qualified people get hired for salaries well above the national average because companies need SOMEONE to do the job. And virtually nowhere cares about degrees, especially for experienced devs. What is baffling is this Valley-centric, web and mobile development-centric line being repeated c…
Agreed, sometimes people aren't aware that HN is its own little echo chamber. I was talking to a recruiter recently for a managerial job and somehow got onto the topic of hiring. I asked him what's the hardest jobs for him to fill right now. He told me he's dying for entry level .NET/ASP and Java developers. Corporations have built their castles on these technologies, not FOSS/Mobile and need staff. Degrees were an i…
Re: The Unemployable Programmer
#275Earlier quoted context omitted.
This is something being glossed over by most of the responses. Age discrimination (or rather, age preconception, if that's a less loaded term) is frighteningly real.
i would expect that an older person with more battle tested experience ought to fair better tbh, so i don't get it with the agism. Unless the position is meant for a high strung startup where you're expected to basically live there, with no dependents to look after etc.
However, rather than re-hash all that, it's worth taking a look at the numbers - numbers that absolutely indicate a younger skewing workforce. For instance, the average age at Facebook is 26, and 31 at Google. Tech as a whole leans young, with the "oldest" tech company workforce (HP) still younger than the national median [1]
Now, whether simply having a younger workforce points towards actual age discrimination is a matter of fair debate. A perfectly reasonable explanation might be that tech is a young field, hence a young workforce. However, there are enough confounding factors (limitations of experience, work/life balance in dev roles, etc.) that certainly make for rational arguments in favor of age being more of burden than boon.
Then, of course, you have stuff like this :
> "Young people are just smarter. Why are most chess masters under 30? I don't know. Young people just have simpler lives. We may not own a car. We may not have family. Simplicity in life allows you to focus on what's important." -- Zuckerberg
True or not, it would be weird to argue that his opinion is somehow a rare isolated outlier. It speaks to a common conception - both in the valley and in tech - that this is a business for the young.
[1] http://bits.blogs.nytimes.com/2013/07/05/technology-workers-...
Re: The Unemployable Programmer
#276Earlier quoted context omitted.
> And having a single development job at a big company for a decade isn't some kind of career-killing move... unless you turn it into one, by letting your skills stagnate and wither, which is on you. Working 40 hrs without training or proper mentoring leads to skill stagnation. A $500 training budget will get you nowhere and you'll find yourself using long weekends (like I'm doing right now) learning new skills. Mayb…
Can anyone please tell me what developers use training budgets for? I feel like most things I have learned are from free resources such as blogs and StackOverflow. What do people spend money on? Books I suppose are the most likely candidate, but those can definitely be bought with $500... Do people actually get value out of conferences? Those always seem more like cash grabs and marketing events than actual training…
Other than that, books and screencasts seem to be a good way to spend that training budget as well. But there's a ton of videos online available for free too.
Of course, they all require time. Which is money. :)
Re: The Unemployable Programmer
#277This is an absolutely baffling article. The job market for developers is not glutted by over-supply, it's one where marginally-qualified people get hired for salaries well above the national average because companies need SOMEONE to do the job. And virtually nowhere cares about degrees, especially for experienced devs. And having a single development job at a big company for a decade isn't some kind of career-killing…
> This is an absolutely baffling article. The job market for developers is not glutted by over-supply, it's one where marginally-qualified people get hired for salaries well above the national average because companies need SOMEONE to do the job. And virtually nowhere cares about degrees, especially for experienced devs. What is baffling is this Valley-centric, web and mobile development-centric line being repeated c…
I haven't found that to be the case here in the Raleigh/Durham, NC area. I never finished my bachelors degree (although, I do have three different associates degrees), and I have never found it to be an inhibition to my career.
Re: The Unemployable Programmer
#278This is an absolutely baffling article. The job market for developers is not glutted by over-supply, it's one where marginally-qualified people get hired for salaries well above the national average because companies need SOMEONE to do the job. And virtually nowhere cares about degrees, especially for experienced devs. And having a single development job at a big company for a decade isn't some kind of career-killing…
In the valley, there are plenty of experienced and uncredentialed people working great jobs. There are relatively few unqualified people doing the same, except when hiring squeezes exceedingly tight.
Outside the valley, defending the decision to hire someone without credentials is virtually impossible. There may be plenty of interest, but someone along the way will chicken out rather than risk the backlash if someone without a degree turns out to be incompetent.
The fact that 'marginally-qualified' people get hired is orthogonal (or maybe even antithetical) to whether 'marginally-credentialed' people do. If a company can't judge competence, they just look for degrees and get shitty employees. That's what's happening outside the valley, and it hurts companies and skilled, degree-less employees alike.
Re: The Unemployable Programmer
#279Earlier quoted context omitted.
This is something being glossed over by most of the responses. Age discrimination (or rather, age preconception, if that's a less loaded term) is frighteningly real.
i would expect that an older person with more battle tested experience ought to fair better tbh, so i don't get it with the agism. Unless the position is meant for a high strung startup where you're expected to basically live there, with no dependents to look after etc.
In others, especially those with the high-strung startup mentality you mention, they are looking for people to work more hours for less pay and promises. Younger people are more able / willing to take risks. Experienced workers are not as interested in promises, but prefer defined returns on their individual investments.
Re: The Unemployable Programmer
#280Earlier quoted context omitted.
What are the corporate-fief states? What does that mean, or what is that in reference to?
Roach-motel markets: you can get in, but you can't get out. More technically, monopsonistic or oligopsolistic factor markets, where the number of employers is small and thus control hiring in the local market. (Though I would expect Nebraska to be fairly competitive in hiring, given its surprisingly large number of finance and insurance companies.)