Today I am a developer, sort of... In my career I have programmed frontend and backend systems and everything in between. I've written 6303 assembler for embedded systems and racked servers in a datacenter. I would definitely consider myself a generalist with a broad knowledge of IT systems.
The things I liked doing 25 years ago are different to the things I like now. People change over time, yet this change is deemed a bad thing.
"Jack of all trades and master of none."
No matter what I have been hired to do I have always given 100% and managed to master the technology at hand in order to deliver the project.
So this isn't simply a matter of getting to use the newest "shiny" either. I have the ability to pivot in order to cope with the unexpected. This has significantly benefited several of my employers over the years.
One example I could give was when I joined a company as a Perl developer. I didn't necessarily think I was an amazing Perl developer and I was honest about this during the interview, but I demonstrated through previous experience and Perl projects that I did in my free time that I was willing to learn and improve.
It was a "foot in the door" moment for me as this job was in a new country and I was happy that they'd decided to give me a chance.
Shortly after I started I found myself developing Java, C#, XSLT and a whole host of other diverse projects. Whilst nobody else in the IT department could pick up these other projects, I could.
I did what needed to be done without the company having to go and hire individual specialists. They saved time and money interviewing and on-boarding and the work got done.
So come on interviewers, maybe give generalists a bit more of a chance in the future.