51–60 of 265 posts
the benefits go both ways. 30-50 year old engineers don't like working for 40-60 year old career-management dipshits who have never done their jobs before.
I'm thankful to work in for the federal govt. where mid 30s to 60s is the age range. Also, the pay for fed govt work is comparably to what engineers in Silicon Valley make, but the cost of living is way lower in this Mid-Atlantic city/area. Though if your single and like to mingle with co-workers and make friends your not going to find that working for the fed; most are married and or recently arrived in the US.
I'm a grey beard who applied to a company specifically advertising for young developers. Got the job without mentioning my vintage. That was six years ago and they still haven't seen my face. I waited a while to gently break the news to them. If you're a technological senior citizen remote work is your friend.
How did they "specifically advertise for young developers" without running afoul of age discrimination laws?
Earlier quoted context omitted.
how do you work for someone without them knowing your age? Do you keep that out of your CV? How about credentials and signing your contact? Seems very strange to me.
Your age or birth date probably shouldn't be on your CV. Unless you think it's relevant to the job somehow, but it probably isn't. Not only should it not matter, but it's illegal for employers to ask about it or consider it in their hiring decision, so having it right there on your CV puts them in a bit of a tight spot. I think some recruiters will actually remove that type of thing before forwarding it on to the int…
Earlier quoted context omitted.
That you exist isn't the problem. The problem is discrimination based on age.
Naturally. All I'm saying that it IS possible to find someone in their 20's with 8+ years of experience.
Earlier quoted context omitted.
Tech fields have an inherent disuse for seniority. Beyond five years, no one gives an f how long you have worked with a given toolchain/language. It's the hunger games. Medicine, finance, law, accounting...rightly or wrongly respect decades of experience. Tech is Logan's Run. Plan accordingly.
Knowing a language or toolchain isn't all you need to be a good developer. Knowledge of how to build maintainable, secure, reliable, scalable and usable systems is something that you get with years of experience (and frequently comes from making mistakes).
Earlier quoted context omitted.
You are more likely to die soon, and if you have some unique understanding of how the company works, that would be lost.
By that logic people under 30 shouldn't be hired either, because they're more likely to jump ship to another company. TBH, if a single person leaving (for any reason) can tank the company, it's probably doing a person a favor not to hire them. Sounds like a mess.
Just because there is also a reason younger people might leave unexpectedly doesn't invalidate my assertion.
And, having someone leave unexpectedly doesn't have to "tank" the company without still causing damage.
Like I said, black and white terms...