Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
This is very sad, but I can't say I'm surprised. As someone approaching 40, this scares me slightly. I don't have the capacity even now to keep on top of the pace of change in how we develop. My current thinking is that I will be forced into more architectural/team lead/managerial/consulting type roles rather than dedicated programming.
-
I recruit in my position and I have interviewed many devs in your position. Hopefully I can impart some knowledge that can help you.
Almost all of the older devs I've interviewed recently are touting old skills.
As someone above me mentioned, the pace at which our industry is changing is phenomenal. If you can confidently sell yourself on newer technologies (languages, frameworks and architecture) then you will be fine.
I would rather hire a guy who is familiar with AWS, Swift, React... AND has 30 years experience any day of the week.
However if you have 30 years experience using 20 year old technologies then yeah... you will be passed over. -
Thank you so much guys. I'll pass your tips on to him.
I think he never made the leap to managing or projects positions, or he just like to write code.
I also think that he will eventually get there with some experience in the interview process. Which there was many tips during wk61.
With his new skills I'm confident he will be attractive as an experienced developer with updated knowledge ;) -
@yiancar Agreed, but experience does not necessarily equal ability (we all know).
A bit late for wk61 but here goes:
Does anyone have any advice for an older dev (just turned 50) during job hunting?
One of the devs on my current project was let go some years a go, and hasn't found a new job yet.
He keeps applying to positions, but keeps getting rejected and being told "we went with another candidate".
Choosing the young buck who will leave in a year over a older dev who still can contribute for ten years seems like the most common descicion.
I hired him on the current project I'm doing for a client, which is on iOS, and I've thought him swift and the general process of development on ios. And he's taking to it really well :)
I hope this will better his chances, but the current client won't have the resources to hire someone full time now.
undefined
wk61