- If you want somebody who will work 14-hour days, well, that eliminates most people over 40.
- If you want to pay appropriate to someone who's 25, well, that eliminates most people over 40.
- If your company is a pit, if your management is insane, if your coworkers are psychopaths, well, most people over 40 have seem that enough times to not go there.
I've seen companies advertising for "senior software engineer". They want 5-7 years of experience. I've got 30. They don't want to pay for 30. Is that ageism? Or am I just too expensive? Or does my experience exceed the hiring manager's ability to correctly value?
I'm not saying that ageism doesn't exist. But I am saying that there are some reasons other than ageism that older software engineers find it harder to get hired.
The marginal return to experience is minimal after a decade or so, particularly when it comes to the average software job. If you have decades of experience, you need to be in a higher leverage position (either consulting or management) to get appropriate pay for the position.
This doesn't make tech ageist. My local grocery store also doesn't pay the senior cashiers any more than the high school ones.
In web programming? Maybe not so much...
If all you need is someone with a few years' experience, the younger candidates are probably going to be willing to work longer hours, for less money, than the older candidates.
In other words, why pay a 20+ year veteran a lot of money to do Rails programming when a recent college grad knows enough to do a decent job, and can be paid an entry-level salary? Not every engineer on a team needs to be senior.
I suspect this is also good career advice: if you don't want to compete with entry-level programmers for jobs, specialize in an area where more experience makes you a more desirable job candidate.
I don't have enough data/experience to confirm that, but it seems plausible.
Embedded systems programming is far more architecture and device specific than web applications are, thankfully. Embedded systems programming requires a much large body of knowledge: chipsets and their features, device-specific options, the behavior of the RTOS (if there is one), esoteric configurations in the cross-compiler or build tool, ability to interactively debug (read the instruction set, use the interface (JTAG, etc), cope with interrupts), ability to thrive with extreme resource limits, and write comprehensive tests with a nearly-exhaustive test plan; since a final release can't be rolled back once customers have purchased it.
This isn't because of some inherent superiority or prestige of embedded systems programming (salaries are lower across the board compared to backend applications programmers), it's just plain more complicated.
A 20-year senior backend programmer should really have progressed to an architect or principal engineer role at that point in her career. An embedded systems developer with 20 years of experience is more typical because of its inherent complexity.
That is absurd. That kind of bullshit talk is why ageism exists and what perpetuates it.
People know it's a problem. Whether or not they actually do anything about it is a different story. Like any "ism."
"Uncle" Bob Martin once gave a talk where he asked for a show of hands of "How many of you have been programming for 5 years? 10 years? 15? 20?". The results in his audience roughly correlated to his thesis, that the number of programmers has roughly doubled every 5 years since programming was a thing.
Are there fewer older programmers at a given company because of ageism? I'm sure that's part of it. But don't forget that there are far, far fewer programmers with 20 years of experience than with 5 years of experience.
Programming is actually a very permissive industry. There are corporate environments in which you can be barely competent and still keep your job - if not gain promotions.
That's the key to getting a job with 20 years of experience. You need to be able to convince the hiring manager that you're worth the extra money in that job. (And then the hiring manager needs people above him that will let him spend the extra money.)
The only candidates I see regularly wearing suits to interview are executives and college junior/seniors. I'm hiring you to code, not model. I couldn't care less what you're wearing as long as it's clean and reasonably respectable.
That's an ageist statement.
Based on conversations in some of our tech groups, yes, it is seen as non-existent by some.
"On average between 1989 and 2007, the unemployment rate of workers under age 25 was 2.2 times as high as the overall unemployment rate. [...] In March 2015, the overall unemployment rate was 5.5 percent, and the unemployment rate of workers under age 25, at 12.3 percent, was 2.2 times as high."