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.
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.
I think there is only 1 person on my team under 40.
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.
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.
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.
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.
checker659•3h ago