But as a programmer in his 50s, when I have personally encountered age discrimination, it's been instant. It wasn't just a thumb on the scale or issues with disparate impact, it was an obvious and clear reaction the moment I walked in the door. It's always stunning when a very pleasant and productive phone conversation becomes immediately hostile when somebody sees my face.
On the other hand, those moments have relatively been rare, and this industry is currently so competitive that they register as "I dodged that bullet" rather than anything truly harmful, although it's definitely been enough for me to see the words "culture fit" as having the definition "we practice illegal discrimination".
BTW, whenever these articles show up on HN we always seem to assume that "tech worker" means developer, but it really refers to everybody: support, manager, tester, etc. If you're a developer, there's tons of ways to keep your skills strong. But the support person who's been keeping a Sybase instance running for the last 20 years or who maintains some spaghetti netware system doesn't necessarily have any marketable skills. There's a lot of people whose skillset is essentially "I've been here a long time".
The funny thing is...as the developed world’s population ages they’ll have to unlearn that bias.
I think this could be solved by coming up with a more common vocabulary of tech job titles.
In medicine you have technicians, orderlies, surgeons, general practitioners, anesthesiologists, physician-scientists, nurses, physicians' assistants, teaching physicians, and so on. Not to mention all the hospital administrators. They're not all "medical engineers". They don't (at least not to the same degree) require a combination of CV parsing and oral exams to figure out what their experience actually entailed.
There's some movement to create separate career paths for DBAs, SREs, etc, though the day-to-day responsibilities there vary quite a bit. I'd like to see specificity in job titles going forward. Someone who assists designers in creating brochure websites probably needs a different job title than someone designing lockless data structures from scratch. And someone who evaluates different production databases and picks the one to ship to production servers probably needs a different job title.
My dad made software for decades until he retired. My brother and I have been working in tech now for decades ourselves. The taxonomy of job titles keeps changing. If tech people had allowed ourselves to be pigeonholed by some older taxonomy, then a) we'd mostly be unemployed, and b) there wouldn't be many people around to do the new class of jobs.
So at least for the rest of my career, I expect hiring will be not about getting an off-the-rack person who fills a highly specific title, but by finding somebody whose past experience is a good match for the current challenges.
I think there's wisdom in waiting for established roles before defining them. "Container engineer" is too specific or at least too early. But "Relational database administrator" (or something) has been around for decades and will be around for some time to come. Maybe the DB vendors and tools will change, but experience in data migrations and transactional thinking is valuable regardless.
https://timesmachine.nytimes.com/timesmachine/1977/10/23/iss... (p 370-395 or so)
The ads I can find there include Computer Console Operator ("must be able to operate 370/145 and 370/418 under DOS/VS with power"), Network Control Analyst ("3 yrs exp troubleshooting lines, modems, and multiplexors"), Keypunch Operator. Programmer and Programmer Analyst positions requiring COBOL, RPG II, Fortran IV, and a lot of assembler. And IBM was its own job category.
And relational DBA is a great example. That used to be a serious job, one with prestige and promise. People were even specific about vendors; one was an Oracle DBA or a Sybase DBA. But now that's in decline. These days programmers are supposed to understand data migrations and transactional thinking. The notion of submitting requests to the DBA department worked in the days of 6-18 month release cycles, but not today. Relational databases themselves are commoditized, going from a central technology to a peripheral one. Does Google even have a relational database running anywhere these days?
Basically the only job title that has lasted is programmer, and even that has changed almost beyond recognition. Maybe we've now plateaued, and jobs will be stable for the next 40 years. But I doubt it. "Virtual server" is a phrase like "radio with pictures" or "horseless carriage". Its a sign that we know things are changing, but we don't know where they're going yet.
>People were even specific about vendors; one was an Oracle DBA or a Sybase DBA.
I can confirm it, anecdotally. I knew a guy who several years ago went to the US on H1-B as an Oracle DBA. And I've heard of and seen ads for other such cases - earlier.
Similarly for PowerBuilder or VB developer earlier, and of course you still see ads for Python / C++ / Haskell / whatever developer.
That's a good point. I think that mismatches in salary expectation are often driven by this. I can find jobs that feel very similar, but ask for "Senior Developer", "Software Engineer II", "Lead Software Engineer", "Tech Lead", "Software Architect", "Programmer Analyst". Then, the varied use of "Junior, Senior" vs "I, II, III", etc.
* Salary: you get what you pay for. (Senior folks -- you need to stand and deliver.)
* Interview process: it's broken, so we actively de-emphasize rote memorization. We instead look for application of principles to solve problems, because that maps well to our work.
* It's hard to gauge experience: we find experience is most valuable when it helps in delivery. Related to interview process, we look for people who can help us deliver solutions, and experience informs us about that.
* We devalue experience: yep, and we don't. Thanks, other hiring managers, for leaving us with a pool of candidates you're ignoring!
On the whole, we try to identify attributes among candidates that we believe are age-agnostic: curiosity in problem solving, a commitment to continuing to learn, ethical and moral code, etc. It's not perfect but it's our list and we continue to improve against it with each subsequent interaction with candidates.
It isn't just job hopping. Even if you ignore promotions to a new title, many workplaces give out yearly salary adjustments that are a bit higher than inflation. Compound interest over 20 years adds up.
Note that I'm well past 40, so I'm in this boat. There are people with a very similar skill set to mine that are less expensive, mostly because they are younger.
For example, why assume that an older person should earn more than a younger person? Instead, it's better to think about paying people in proportion to the value that they provide to the company.
I understand that many startups simply do not have the cash required to pay a high base salary. But, that's what equity compensation is for.
Find me a fresh out of school 20 year old with 30 years experience and I'll pay them more too.
Just because someone has worked 30 years, doesn't mean they have 30 years of experience. They may have 5 years of experience 6 times or even worse stopped learning anything new 15 years ago.
I'm in my mid 40s and I've hired developers who are older than I am and had 10+ years of C# but have never done a unit test, didn't understand the concepts of continuous integration/continuous deployment, didn't know Linq (introduced in 2008), Web API (introduced in 2011), and didn't even know WCF.
I needed developers and thought with their experience with different technologies they would be able to adapt. I was hiring based on Joel's "smart and gets stuff done".
Was I wrong. Older developers who haven't kept up with the trends for the last decade and haven't kept up with the changes in technology are worse than young developers who don't know.
As far as the pay ceiling, yes I've reached a ceiling as a developer. But not as an architect who both keeps up the latest shiney frameworks and has a deep understanding of the fundamentals.
I can also deliver inexperienced employees who are underpaid.
(Also, most companies pay employees more than fair value, to discourage them from shirking.)
This has been happening for a decade or more... Every time I look at salaries they've gone up significantly more that other fields.
Consider an employee working at an investment bank 15 years ago versus today. 15 years ago, most value was generated by hoards of sales people and traders who cultured deep personal relationships with deep-pocketed customers. Today, tech people command a greater share of the wallet, and banks are making deep cuts to the ranks of sales people and traders.
These companies are emerging, though, right? 37Signals? I'm sure there are other small well-paid companies, if only from the evidence of a job ad I once saw. Now, "Compensation: Competitive" and "Compensation: Market" have been batted around for years, even around here, but this ad was for a programmer at a financial technology company and in the space for "Compensation" they put "Extremely high." Then again, those places are probably actually using the Big-O concepts they ask about in interviews.
You never see anything like that in Internet companies.
You might find these interesting:
https://en.m.wikipedia.org/wiki/Shapiro%E2%80%93Stiglitz_the...
http://news.mit.edu/2016/economist-bengt-holmstrom-nobel-pri...
Both statements are prejudiced - pre-judging someone based on factors they cannot control.
I agree that older candidates typically have expectations of higher total compensation.
My point is that, either:
1. That expectation is unfounded -- they are looking to be paid out of proportion to the value they would provide back to the company, or
2. That expectation is justified, in which case the cash-poor company should find some way of striking a deal, so that they can bring on an employee of high value.
They shouldn't earn more, if they're providing the same value as someone paid less. But, they typically ask for more, because they have more experience (which is difficult to validate), and usually have more financial obligations.
It is up to the employer to decide if they want to pay the price of seniority.
> I understand that many startups simply do not have the cash required to pay a high base salary. But, that's what equity compensation is for.
As one gets older, it's in their best interest to become more financially risk averse, and require more predictability and less uncertainty. Startup equity is very high-risk, and therefore not acceptable as a replacement to more salary.
I do not agree about risk aversion. I know several older software developers who have finally paid off their student debt and accumulated some savings, and are now ready to accept some higher risk compensation. In addition, I know younger workers who are in desperate need of cash.
I personally feel there's a point where it's a law of diminishing returns, somewhere around the 5-10 year of experience mark.
> it's better to think about paying people in proportion to the value that they provide to the company.
In general older developers are bringing experience from other projects, other industries, past crises, and soft skills that provide value (for instance, I think a 24 year old and a 40 year old have different approaches to telling someone they disagree with them)
The younger candidate might be inexperienced but a fast learner; the older candidate might have a lot of experience, but might be reluctant to adopt the companies coding practices...
There’s no way to know which of them is going to provide more value in the long term; but you do know that one of them expects a significantly higher salary.
I'm having trouble making sense of this. Isn't that exactly what the hiring manager does? Then, if that number is too far off, it gets adjusted later, once more data as to value comes in.
How do you know that before you ask them?
Even then, I think the compensation can be structured to reflect that risk profile.
> * Salary. Older employees are more experienced, but, just as importantly, they've already job-hopped a bit, so their base is a lot higher.
First of all, why does job hopping entitle you to a higher salary? A guy who's done 5 jobs of 2 years each, with one of them being most relevant to my position, vs. someone who's done 1 job of 10 years somewhere most relevant to my position is an easy choice. The latter will be more useful for my organization. Job hopping also seems negatively correlated to specialization, which IMO is your key differentiated value as a prospective employee.
Why should your career ADHD command a higher salary?
> And they've probably a lot more personal financial responsibilities. All told, they're unlikely to go for the same salary as a new grad.
Yeah, I can see this coming from a mile away and so I tend to not waste the time of people for whom this is the case. The easiest way for me to do this is being upfront about salary for the position.
> * Interview process. Anecdotal experience, but, the interview process is structured towards new grads. They've studied algorithms recently, so it's at their fingertips. Unless you've brushed up before interviewing you can look sloppy and unsure in comparison. This can be harder if you've an existing job and family commitments. (Note: I'm not saying you shouldn't study; just pointing out that this can happen.)
Fair.
> * It's hard to gauge experience. Simply because a person has been in the industry for 10 years doesn't mean that they're "more experienced".
True.
> * Finally, we devalue experience. A personal bugbear is hearing hiring managers say that they can train up a new grad to be a tech lead in about a year. Unless you've worked on a couple of largish projects - and seen your own designs evolve in response to requirements, I question that strategy. But, who knows - maybe I'm completely off-base there.
The factor here, roughly speaking, is IQ. Give me someone with higher raw intelligence and they'll often quickly get somewhere that someone with more experience has. Just existing and showing up for 10 years doesn't mean you're automatically better than all the 22-year-olds I have lined up for an interview.
---
I wanted to voice some unpopular opinions from the other side of this coin because it seems most people on HN resonate more with the "employee" rather than the "employer".
That person who has specialized for 10 years probably hasn't been exposed to the five different environments with 5 different ways of doing things and being able to mix and match the best of all of the environments.
That person who has specialize may know how to code, but do they have experience talking to different customers in different verticals? Have they been involved in the full life cycle including devops?
* Salary. Older employees are more experienced, but, just as importantly, they've already job-hopped a bit, so their base is a lot higher. And they've probably a lot more personal financial responsibilities. All told, they're unlikely to go for the same salary as a new grad.
* Interview process. Anecdotal experience, but, the interview process is structured towards new grads. They've studied algorithms recently, so it's at their fingertips. Unless you've brushed up before interviewing you can look sloppy and unsure in comparison. This can be harder if you've an existing job and family commitments. (Note: I'm not saying you shouldn't study; just pointing out that this can happen.)
* It's hard to gauge experience. Simply because a person has been in the industry for 10 years doesn't mean that they're "more experienced". It's very tricky to gauge: it's easy to tell when someone is less experienced than you, but much harder if they're more experienced. Plus, how do we evaluate experience? Design questions? Software architecture? Looking at code they've written? It's very fuzzy, and a lot depends on the skill of the interviewer and their own experience.
* Finally, we devalue experience. A personal bugbear is hearing hiring managers say that they can train up a new grad to be a tech lead in about a year. Unless you've worked on a couple of largish projects - and seen your own designs evolve in response to requirements, I question that strategy. But, who knows - maybe I'm completely off-base there.
EDIT: I'd like to raise a final point: sometimes the impact of experience is only apparent when you've to scale your product architecture or your team. Assuming that most startups fail (i.e. never make it that far), this means most very early stage teams can get by with an ad-hoc process and/or system until they pass that hump.