Unfortunately, due to the economy, I there haven't been too many potential new hires for me to be involved in interviewing them. But when I did have some involvement, your observation was correct. The CS grads of today can barely code their way out of a wet paper bag, and they don't know any other language than Java when they even try. Like "write a file copy subroutine, and why did you make the choices you did". Yeah, computer science grads, they don't even understand how to do a buffered copy, much less how to determine your buffer size, which is one of the basic concepts of Computer Science. Nor do they seem to understand how to work with linked lists. (Were they asleep through their sophomore year data structures class, or what?) The EE grads actually knew how to program.
I was a CS grad of the '80s, but I already knew how to program and hook up TTL chips from my teen years, when it was all 8-bit, and from disassembling a Z-80 MS-BASIC. (That was MY "summer of code" from Bill Gates, with zero cultural bullshit.) For me, CS filled in a lot of the things I didn't know, like data structures class. The uni's equivalent of "Computer Engineering" was too hard to get through (mostly because low participation meant that the classes weren't taught every semester), but what classes from that major that I took as electives were for the FUN of it. Build a serial transmitter from TTL chips? No sweat, and then watch me flip those switches to make messages, since I knew the entire ASCII code chart in hexadecimal. Again, zero cultural bullshit, just me against some chips and wires.
Actually the main reason I didn't go EE was that I only wanted to mess with digital electronics. I didn't fucking care what the beta of a transistor was, or even why it mattered. Just give me a handful of 2N2222, some 220ohm, 1K, and 5K resistors, and LEDs. I know to respect transmission line characteristics because they will bite you in the ass, but beyond that "There be dragons here". Maybe that's why I'm so big on encapsulation in my code.
These days I'm doing embedded systems programming. Not much ageism in this part of the industry. I'm 49, and I have the least gray hair of the half a dozen or so programmers where I work. I'm the whippersnapper who actually figured out how C++ could make my code better. Just this past week I got an Ethernet chip working for the first time (which was kind of a bucket list thing for me), on a system with no OS. (So is there a pull-string Barbie that says "interrupt handlers are hard"?)