3 ms·
Oh, heck. I didn't even see the reply. Probably right. Depends on the question, I guess. You know what I mean, use questions straight out of textbooks that ha
by ChrisMarshallNY 7y ago
Oh, heck. I didn't even see the reply.
Probably right. Depends on the question, I guess.
You know what I mean, use questions straight out of textbooks that have only been in circulation in the last five or ten years.
I've found that it's easier all around if I simply don't hide that I'm over 40. It means a lot fewer responses to inquiries, but also a lot less wasted time. Avoids that crestfallen look when you walk in the door.
Apparently, the industry is crawling with folks that are under 35, but have the judgement and expertise you get from 30 years' of programming.
I'm also puzzled why folks would think they can learn more about me from a twenty-minute test, than by looking at ten years' worth of code in dozens of repos.
I was a hiring manager for many years. I would have drooled to see that kind of background on any one of my candidates. Still, I generally found that I was able to accurately judge their competence after about a half-hour chat (at least, I never seemed to get it wrong), and it was all about cultural fit, after that.
I suppose being an up-to-date engineer, myself, helped.