Saying all embedded will get so fast that you can always use Python ignores the side that is focused on smaller footprint and power consumption. Saying that embedded is only hard-core C or C++ stuff that must be compiled is ignoring the Arduino/Pi world where devices that used to be clearly embedded are now powerful but still very small.

However, in either case, we do still regularly deal with a lot of issues such as constrained resources, real-time needs, etc. Grabbing a random engineer who knows Python and saying they're going to be good at that is silly. In many, many cases you'll still need to learn how the system truly works top to bottom to be effective.

1. Mid-level engineers (I consider 2-5 years of experience) are very hard to find. 2. Entry/Junior engineers are much easier to find, but finding good ones[1] is still difficult. 3. I suspect it is the shortage that has caused the following discrepancy in applications: 100% of Program Manager respondents include a well-thought out cover letter, less than half of our software developer candidates do the same. With a frantic hiring of software developers (i.e. shortage), you don't need to put in so much effort and still find something.

[1] We consider good software developer candidates someone in the area or willing to relocate, who is sharp at coding and who has done some independent work.

Someone else commented about not having time to do independent work. In life, you have time or money. Is there someone out there like the protagonist in "The Pursuit of Happyness"? Yeah, probably. But you can't tell me that's the case for 90% of engineering candidates. If you love what you do, you find a way -- in fact, wild horses couldn't keep you away from building something.

It's not that there isn't a deep talent pool, it's just that the demand is deeper than the supply.