Considering making a move to software dev. I’ve heard a lot about ageism. Also that the market for jr devs is brutal. Am I wasting my time?
Comments (11)
fjfaase · 3h ago
At your age, I guess it is rather important what you have to offer besides your software development skills. Do you have experience working in teams, a track record with working with people, or extensive knowledge in an adjacent field, such as electronics, IT, or one of the other sciences? Or do you have extensive knowledge of certain safety/security/medical regulations?
Is there some specific area in software engineering that you are drawn to or some application are? There are many applications fields of software development and I think in some large fields it will not be worth trying to compete with junior developers.
fzwang · 3h ago
I second this. If you're trying to signal just on "I can code", then there will be fewer differentiating factors between you and younger people.
Typically, I don't think of software dev as an "industry" in itself, unless you're talking about dev tools etc, but that many industries depend on strong software. Your best bet is to target software problems related to your prior job. This way, your skillsets complement each other. You may not be the best at either side, but your ability to integrate the two could be a strong pt.
codingdave · 3h ago
No, there are many of us with grey hair in the software industry.
42 is probably too old for the startup world, which is where the discussions on HN tend to focus, but that is really just one slice of the industry. There are a ton of jobs at larger non-tech companies, where ageism is not as much of a problem. It is slower-paced, lower-paid, more boring... and perfectly acceptable if all you are looking for is a solid stable job.
The bigger challenge is the "junior dev" problem. There is some harsh reality there. But you can probably fight through that if you look for software work in whatever industry you are coming from, so that your couple decades of prior experience is relevant to the work being done by any team you would join.
codegeek · 2h ago
Age is not the main issue. I mean it may make it more difficult but you have a bigger challenge. "Making a move to Software Dev" sounds like you will be entry level in Software world which is really hard right now especially with AI etc.
So the question is "why you if I can hire a 23 year old with possibly more energy, less baggage (most likely they can work longer hours and not have family/kids to worry about etc). That's possibly ageism but when there is a choice b/w an entry level Software Dev who is 23 vs who is 42, who do you think will get priority ?
Now, if you can differentiate yourself where your age becomes a plus and not minus, then we are talking. For example, one can assume you have a lot of real world experience, you have worked in tough conditions with real customers (whatever industry). Can you use that to your advantage and make a better case ? Then you can do it.
codingdave · 1h ago
> when there is a choice b/w an entry level Software Dev who is 23 vs who is 42, who do you think will get priority ?
Seems pretty ageist to even put the question that way. One could absolutely build up a list of specific criteria that often are more true with younger people, but if you don't articulate those criteria and base decisions upon them, and not the age of the candidate, that is straight-up ageism.
comprev · 2h ago
During interviews I make a point about flexibility due to not having my own family, and can also dedicate significantly more time to learning outside of work that perhaps many candidates of a similar age (40-45 bracket) are unable to. I have the same "free time" as a junior dev in their 20s... but with 20yrs Ops experience on top.
It does pay off though and I am delighted when colleagues approach me with a difficult problem to crack. I never take on formal ownership of the problem though, but if I do crack it, my input is well documented (and bonus points: I learned something new).
Cracking some hard problems has earned me a good reputation among the senior engineers & engineering management, and hopefully my future career will benefit from these relationships.
Tony_Delco · 2h ago
It’s never too late to learn something new, not even to start in software. Age can bring a different way of looking at problems, shaped by past experiences in different situations and environments.
The path can be tough at the beginning, but if you truly enjoy it, you’re not wasting your time, you’re investing in a new stage of your life.
And this is just my personal opinion: I believe a team should be as diverse as possible. The more different perspectives, the better. A 22-year-old junior doesn’t see things the same way as a 42-year-old junior, and both are valuable and perfectly compatible.
jleyank · 3h ago
I'm way older, but I had the impression that 30-35 was already too old for casual consideration for software development outside specific fields? Which is depressing as science PhD's enter industry at the 26-30 age range...
checker659 · 4h ago
What are you transitioning from?
al_borland · 3h ago
I’d probably stay out of startups. A lot of companies need code written and most of them aren’t “tech” companies in the valley.
I think there is only 1 person on my team under 40.
JustExAWS · 3h ago
I’m not going to give you the BS “you can do an anything if you put your mind to it” answer that many are going to give you here.
If you are in your 40s and 50s and have the experience “you should” for your age, up to date on technology and have built a great network, the world is your oyster.
If none of that is the case, getting a job as a junior developer at any age is a shit show right now. Hell it’s a shit show for people with experience when every job opening gets hundreds of applications within the first day.
Is there some specific area in software engineering that you are drawn to or some application are? There are many applications fields of software development and I think in some large fields it will not be worth trying to compete with junior developers.
Typically, I don't think of software dev as an "industry" in itself, unless you're talking about dev tools etc, but that many industries depend on strong software. Your best bet is to target software problems related to your prior job. This way, your skillsets complement each other. You may not be the best at either side, but your ability to integrate the two could be a strong pt.
42 is probably too old for the startup world, which is where the discussions on HN tend to focus, but that is really just one slice of the industry. There are a ton of jobs at larger non-tech companies, where ageism is not as much of a problem. It is slower-paced, lower-paid, more boring... and perfectly acceptable if all you are looking for is a solid stable job.
The bigger challenge is the "junior dev" problem. There is some harsh reality there. But you can probably fight through that if you look for software work in whatever industry you are coming from, so that your couple decades of prior experience is relevant to the work being done by any team you would join.
So the question is "why you if I can hire a 23 year old with possibly more energy, less baggage (most likely they can work longer hours and not have family/kids to worry about etc). That's possibly ageism but when there is a choice b/w an entry level Software Dev who is 23 vs who is 42, who do you think will get priority ?
Now, if you can differentiate yourself where your age becomes a plus and not minus, then we are talking. For example, one can assume you have a lot of real world experience, you have worked in tough conditions with real customers (whatever industry). Can you use that to your advantage and make a better case ? Then you can do it.
Seems pretty ageist to even put the question that way. One could absolutely build up a list of specific criteria that often are more true with younger people, but if you don't articulate those criteria and base decisions upon them, and not the age of the candidate, that is straight-up ageism.
It does pay off though and I am delighted when colleagues approach me with a difficult problem to crack. I never take on formal ownership of the problem though, but if I do crack it, my input is well documented (and bonus points: I learned something new).
Cracking some hard problems has earned me a good reputation among the senior engineers & engineering management, and hopefully my future career will benefit from these relationships.
The path can be tough at the beginning, but if you truly enjoy it, you’re not wasting your time, you’re investing in a new stage of your life.
And this is just my personal opinion: I believe a team should be as diverse as possible. The more different perspectives, the better. A 22-year-old junior doesn’t see things the same way as a 42-year-old junior, and both are valuable and perfectly compatible.
I think there is only 1 person on my team under 40.
If you are in your 40s and 50s and have the experience “you should” for your age, up to date on technology and have built a great network, the world is your oyster.
If none of that is the case, getting a job as a junior developer at any age is a shit show right now. Hell it’s a shit show for people with experience when every job opening gets hundreds of applications within the first day.