5 ms·

My take is a bit different, and it may explain the phenomenon you've noticed on HN. TLDR; I believe a lot of people mistake price discrimination as age discrim

My take is a bit different, and it may explain the phenomenon you've noticed on HN. TLDR; I believe a lot of people mistake price discrimination as age discrimination. Long version: Let's say you need some code monkey to slap together go or rust services. Well, sure, you get a lot of people applying with 25 years experience, you also get a lot of people applying with 5 years experience. Now here's the rub, it's highly unlikely that anyone's been coding go or rust services for 20 years in any case. (To be honest, it's even unlikely that anyone's been coding go or rust services for 5.) So any of those applicants, as long as their references check out, will do. Which salary do I want to pay? If I have a low level, quasi hardware layer service that I need coded in C or C++? Fine, yes, experience matters. It matters a lot in those instances, and I'd be foolish to hire some kid to do that. But there is less and less of that kind of work. (Flip side being that such work is more and more critical.) The dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff that could be satisfactorily accomplished by any warm bodied techie. So it just makes no sense to pay more for those warm bodies.

rfrey 7y ago
Isn’t that solved by specifying “junior developer” or “intermediate developer”? Or by including the salary range?
- bilbo0s 7y ago
  Well, as a rule, I never included salary range. I ask for salary requirements. Then only proceed down the evaluation and hiring path with applicants where the salary matches what is available in the budget. Better chance you get an employee who's happy with the pay that way. I always specified entry level, intermediate, etc, but as times get harder, what you start to realize out here in flyover country is that everyone is applying for all positions. They don't really care about the title or labels. (At least, I suspect it's because times are getting harder? I don't know of any other reason highly experienced people would be applying for some of these kinds of positions.)
- commandlinefan 7y ago
  It should be - but I’m positive that everybody with over 10 years experience is calling themselves a “senior developer” by now. There’s no level after that, so most everybody over 35 is a senior developer.
  - scarface74 7y ago
    There are “principal developers” and architects, but just like with products and the “Innovator’s Dilemma” at some point, your skillset overserves the market. After a certain level of competence, experience doesn’t add value if you’re applying to be a developer for yet another software as a service crud app. Either be happy with salary stagnation and cost of living raises (if that) or move on to greener pastures.
    - commandlinefan 7y ago
      Well, I’d be way happy if I could spend the next 20 years making what I’m making now (adjusted for inflation) doing what I’m doing now, but it seems like there’s a certain age where your salary expectation is $0 - IF you’re in software. I don’t get why this doesn’t happen to doctors, lawyers, accountants, etc.
      - scarface74 7y ago
        I keep reading that. But from what I’ve seen from corporate America and outside of the startup culture, if you keep your skills and network current, there are still opportunities. That being said, I’m 45 and the oldest ICs that I know are late 40s early 50s. One has started only applying for remote work.
    - PorterDuff 7y ago
      If you make it to Senior Principal Staff Engineer they'll bring coffee to you.
      - deleted 7y ago
        [deleted]
- gbacon 7y ago
  Will that expose the company to accusations of age discrimination? They aren’t even interested in applications from developers with more than ten years of experience!
acdha 7y ago
> it's highly unlikely that anyone's been coding go or rust services for 20 years in any case. (To be honest, it's even unlikely that anyone's been coding go or rust services for 5.) So any of those applicants, as long as their references check out, will do. This is a common misunderstanding: yes, Rust is new but prior experience with everything else is not capped at 5 years and it matters a lot. Over my career, I’ve had to fix or replace a number of those “any warm bodied techie” apps where they had incorrect results, security issues, unusable performance, etc. because the developers had been marginally proficient in a popular tool but lacking more general skills and, most importantly, the ability to recognize that they were out of their league.
Spooky23 7y ago
I hired a guy with a masters in EE who is crazy smart as a help desk tech. He’s since moved up. Our job was his first interview in a year.
crispyambulance 7y ago
> ...the dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff No. I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. It simply is not true. I think folks are just extrapolating from "Pet-shop" or "Northwind" examples that they've seen in tutorials/docs and assume that that is what, say, enterprise developers actually do at the same level of complexity. It's not and it has never been the case.
- scarface74 7y ago
  CRUD apps are simple. You need one or two architects and seniors to make sure that things don’t go off the rails and to gather the requirements and once you have that, some boot camp grads can do the grunt work. When I was a team lead, I wouldn’t overpay for a crud developer. I call myself an “enterprise developer/architect” on HN for context - meaning I don’t work for the cool hip startups but let’s call a spade a spade, I’ve spent the last 10 years working on yet another software as a service crud app or bespoke internal apps. Yeah I spend some time in meetings, dealing with “cloud native” infrastructure and I can hold my own up and down the stack.
- ThrowawayR2 7y ago
  > I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. Nah, it's true. For the average small to medium size company, CRUD apps are mostly "plug library A into framework B, with a dash of glue logic" and you're done. The most difficult part is the yak-shaving needed to get things to work together. Things like embedded systems or scaling to FAANG levels are much more difficult.
PorterDuff 7y ago
"If I have a low level, quasi hardware layer service that I need coded in C or C++? Fine, yes, experience matters. It matters a lot in those instances, and I'd be foolish to hire some kid to do that. But there is less and less of that kind of work. " You know, that could be. Dunno why you got the downvote so here's an up. Offshoring of manufacture probably has something to do with the dearth of work. Development was bound to follow mass production.

rfrey 7y ago

Isn’t that solved by specifying “junior developer” or “intermediate developer”? Or by including the salary range?

bilbo0s 7y ago
Well, as a rule, I never included salary range. I ask for salary requirements. Then only proceed down the evaluation and hiring path with applicants where the salary matches what is available in the budget. Better chance you get an employee who's happy with the pay that way. I always specified entry level, intermediate, etc, but as times get harder, what you start to realize out here in flyover country is that everyone is applying for all positions. They don't really care about the title or labels. (At least, I suspect it's because times are getting harder? I don't know of any other reason highly experienced people would be applying for some of these kinds of positions.)
commandlinefan 7y ago
It should be - but I’m positive that everybody with over 10 years experience is calling themselves a “senior developer” by now. There’s no level after that, so most everybody over 35 is a senior developer.
- scarface74 7y ago
  There are “principal developers” and architects, but just like with products and the “Innovator’s Dilemma” at some point, your skillset overserves the market. After a certain level of competence, experience doesn’t add value if you’re applying to be a developer for yet another software as a service crud app. Either be happy with salary stagnation and cost of living raises (if that) or move on to greener pastures.
  - commandlinefan 7y ago
    Well, I’d be way happy if I could spend the next 20 years making what I’m making now (adjusted for inflation) doing what I’m doing now, but it seems like there’s a certain age where your salary expectation is $0 - IF you’re in software. I don’t get why this doesn’t happen to doctors, lawyers, accountants, etc.
    - scarface74 7y ago
      I keep reading that. But from what I’ve seen from corporate America and outside of the startup culture, if you keep your skills and network current, there are still opportunities. That being said, I’m 45 and the oldest ICs that I know are late 40s early 50s. One has started only applying for remote work.
  - PorterDuff 7y ago
    If you make it to Senior Principal Staff Engineer they'll bring coffee to you.
    - deleted 7y ago
      [deleted]
gbacon 7y ago
Will that expose the company to accusations of age discrimination? They aren’t even interested in applications from developers with more than ten years of experience!

acdha 7y ago

> it's highly unlikely that anyone's been coding go or rust services for 20 years in any case. (To be honest, it's even unlikely that anyone's been coding go or rust services for 5.) So any of those applicants, as long as their references check out, will do. This is a common misunderstanding: yes, Rust is new but prior experience with everything else is not capped at 5 years and it matters a lot. Over my career, I’ve had to fix or replace a number of those “any warm bodied techie” apps where they had incorrect results, security issues, unusable performance, etc. because the developers had been marginally proficient in a popular tool but lacking more general skills and, most importantly, the ability to recognize that they were out of their league.

Spooky23 7y ago

I hired a guy with a masters in EE who is crazy smart as a help desk tech. He’s since moved up. Our job was his first interview in a year.

crispyambulance 7y ago

> ...the dirty secret of the tech industry however, is that most work is just CRUD equivalent stuff No. I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. It simply is not true. I think folks are just extrapolating from "Pet-shop" or "Northwind" examples that they've seen in tutorials/docs and assume that that is what, say, enterprise developers actually do at the same level of complexity. It's not and it has never been the case.

scarface74 7y ago
CRUD apps are simple. You need one or two architects and seniors to make sure that things don’t go off the rails and to gather the requirements and once you have that, some boot camp grads can do the grunt work. When I was a team lead, I wouldn’t overpay for a crud developer. I call myself an “enterprise developer/architect” on HN for context - meaning I don’t work for the cool hip startups but let’s call a spade a spade, I’ve spent the last 10 years working on yet another software as a service crud app or bespoke internal apps. Yeah I spend some time in meetings, dealing with “cloud native” infrastructure and I can hold my own up and down the stack.
ThrowawayR2 7y ago
> I see this a lot on HN, the idea that "CRUD" applications are trivial, but it's a myth. Nah, it's true. For the average small to medium size company, CRUD apps are mostly "plug library A into framework B, with a dash of glue logic" and you're done. The most difficult part is the yak-shaving needed to get things to work together. Things like embedded systems or scaling to FAANG levels are much more difficult.

PorterDuff 7y ago

"If I have a low level, quasi hardware layer service that I need coded in C or C++? Fine, yes, experience matters. It matters a lot in those instances, and I'd be foolish to hire some kid to do that. But there is less and less of that kind of work. " You know, that could be. Dunno why you got the downvote so here's an up. Offshoring of manufacture probably has something to do with the dearth of work. Development was bound to follow mass production.