So many reasons
There are a lot of reasons we don't see EEs that much (well, you do if you are in the right place).
When someone who fixes a washing machine using a fault finding handbook calls themselves an 'engineer' it rather colours the perception of young people. I had an amusing altercation when my washing machine broke (in warranty) some years ago.
Me: Washing machine pops the breaker
Them: We will arrange for an engineer to visit
Me: I need it fixed, not redesigned
Them: <silence>
That aside, universities don't give enough hands on experience and unless they get a decent mentor they are lost and drift away from the EE side.
Universities don't give analogue the attention it needs; it is an analogue world and if you want to interface sensors, you will very probably need skills in this arena. Want to do high speed (multi gigabit links)? You will need all manner of analogue skills. Mixed signal (fast digital and sensitive analogue) is challenging and needs in depth analogue skills.
At the physical layer, every signal is analogue (until you get to Planck quantities anyway) as EMC testing proves on a daily basis.
I have met many EE graduates who think EE is a matter of getting a RPi or Arduino and flashing LEDs.
A microcontroller is used more often than is strictly necessary, in my view (ymmv) and I blame the Universities for that.
A lack of 'getting them young'. The spark starts early and it has to be interesting enough to keep them engaged. Talking about engineering (of any description) only after they are 13 or 14 is way too late.
There is a lot of electronics design done and built in the UK where I have been a part of it. I can't trust the Chinese suppliers to use the correct grade of PCB material (the glass transition temperature matters a lot in some designs and when it comes to controlled impedance forget it).
I do electronics hardware and usually write my own software for embedded stuff (often bare metal) - RTOS's are overused and where you need deterministic behaviour they suck.
In "The Art of Electronics" the authors say that electronic design is "a few laws of physics, a few rules of thumb and a large bag of tricks" (might be paraphrased)..
Sticking around long enough to learn those tricks and rules of thumb can be daunting when young grads don't have decent mentors or managers to say nothing of an inadequate education.
Software is often seen as the cool area, but software needs something to actually run on and it usually is not a desktop or laptop in many many cases. To echo someone else on this thread, digital sampling of signals is a science in its own right and is totally different to continuous time (analogue) techniques and it is not simple at all. Why that is not made clear is beyond me (unless the lecturers / professors don't know. of course).
I do not have a degree; I look at my career as a self directed apprenticeship. It also helped that I went to the USA after leaving the Royal Navy where the attitude (in stark contrast to the UK at the time which could be very elitist) was 'can you do the job'
Yes, there is a lot to learn, but that is part of the attraction for me; not sure how youngsters see it in a world where instant gratification and 'everyone should get a prize' seems to be the expectation.