9 ms·
I'm 38. I know 40 seems to be the cut off, but in the Boston area no problems finding a job. I will say that I interview devs at my current position. I have no
by joeyb164843 6y ago
I'm 38. I know 40 seems to be the cut off, but in the Boston area no problems finding a job.
I will say that I interview devs at my current position. I have noticed that a lot of the older people who come in and have years and years of experience at one place don't seem to have the breadth of knowledge we are looking for.
For example, recently before the lockdown I interviewed a guy with over 20 years experience, most mainly at one company for a .net role. He didn't know any of the latest features of the language, including Linq and async/await, never used .net core, no NoSQL experience at all.
We didn't hire him and it's not because of his age. We have several "older" new hires in my engineering department, but it seems like a lot of the "older" people have lots of experience, but at the same company where they fall into complacency and don't keep up with what is happening in the industry.
Not saying this is the case here, but when interviewing this guy I mentioned, this site popped into my head because this is not the first time I've heard people complain about age discrimination in tech here. I have to say from my personal experience, I haven't seen it. Not once has anyone on our interview team said anything about an interviewees age, only the amount of experience someone has. And even that is treated as a positive as we just assume they know their stuff if they've been around for 20+ years.
- deleted 6y ago[deleted]
- speby 6y agoThis. I have also interviewed a handful of people that had 20, 30 years of experience building software. In some cases, they had resumes pages long dating back into the late 80s. One tip I would stress to anyone who has been doing software engineering that long? Don't list all of the history you've ever had. Go back maybe 10 years. If you're worried someone might miss something you built from 15 years ago, just put "more job experience history available upon request" or something like that. The simple truth is having built something in Delphi in the 90s just isn't going to 'help' you working with today's frameworks, even though the underlying core software engineering skills will almost certainly be relevant regardless of language, toolset, or framework du jour.