Yep. I passed the technical screen with flying colors. But the the hiring manager gave feedback to the recruiter that he wanted someone "more current". That's codespeak for "younger".
I had a recruiter post to DICE for someone who's "fresher". I complained to DICE and they took down the job listing and I hope banned the recruiter who himself identifies as "fresher".
I leave the date of graduation off my resume and any requesting info. That, in and of itself, is a sign. I don't need to dye my hair but I have friends that do. And I made the mistake of mentioning that I recently paid off my mortgage. Again the manager refused to interview me despite one of their team who I worked with giving me a stellar recommendation.
I keep asking recruiters if I should take off experience going back to the mid-90s and they all say to keep it. This thread is telling me otherwise.
I've been in an interview that was going pretty well but ultimately went over the allotted time. I agreed to go over and they asked me to write a script. I drew a complete blank on how to do it and said so. I'd have to do some research to figure out the best way to do it. That ended the interview.
Afterwards, I did a simple google search and there's UNIX command that does most of the work. But I didn't know that command, so I couldn't solve the problem in the moment.
I supposed I might have been successful and done well at that job, but not if I had to work with the guy interviewing me. So it all worked out.
A musician friend of mine is married to a Sysadmin. Don't laugh. It works.
She equates an interview with an audition, which totally different from playing in an orchestra.
Pre-COVID, I'd get pre-screening questions that required some research and an essay that would have taken 4-6 hours to do thoroughly. I turned those down. Short questions like "What's the difference between a hard and soft link?" are fine, but I'm not going to write an essay describing in detail at the network level what happens when I type a URL into a browser.
I've had a python coding pre-screen for DevOps gig which was minimally specified. I had to guess how they wanted the output. I'd never really coded a full python program, only on-line exercises, so I took the challenge to do it in 24 hours while I was cooking for a dinner party. I got it running and turned it in.
They didn't like my output or how I coded it. It reminded me of a similar situation with past manager -- I was supposed read his mind as to what he wanted. When I got it wrong, we had meeting where I asked all sorts of questions about what he wanted and how he wanted it, much to his distaste. He really wanted someone who'd "do what I ask and don't ask questions". I think it was a culture thing.
Ultimately, I could have fixed the code to do what the pre-screener wanted, but I told the recruiter I wasn't interested.
The biggest difference between time and space is that you can't reuse time. -- Merrick Furst