That's a terrible take. Programming is often a rarer and more difficult skill to hire for them many of the domains programming jobs touch. Most places will hire you just based on programming knowledge, and will train you in the domain knowledge.
All of the jobs you've listed are highly technical fields, and unusually specialized among programming jobs. A general SWE position doesn't often require much more than just programming.
I have not been able to find a place like that, most have a long list of requirements. Can you suggest any?
The problem is, the employer is probably wrong (they did not do the correct requirement analysis on this), and actually don't want a "just a Programmer", they want a "Requirement Analyst"/"Functional Analyst"/"Design Analyst", and those are the rarer and more difficult skill to develop and find at all.
Based on my observations, biased due to my specific niche, most people who program just ... well ... shouldn't. If there were doctors practicing medicine as bad as some people who call themselves programmers program, then we'd have riots!
Really curious, what counts as "programming knowledge"?
In my opinion Python's strength does not lie in the language itself but rather in its third party package ecosystem. Libraries such as NumPy, Requests and PIL/Pillow provide optimized (and often native) black-box implementations of common tasks and wrap them into simple APIs, turning Python into basically the modern equivalent of shell scripting. You can usually "pipe" data from one library to the other and create complex pipelines in just a few lines of code, without sacrificing too much performance since most of the magic happens within the packages' DLLs. I guess this is what made it popular for data analysis in the first place.
I would strongly recommend OP to familiarize themselves with NumPy and other popular packages, including the data-science-oriented ones, as they might come in handy when writing nontrivial scripts. Writing simple command line tools is also useful for getting used to the standard library.
When you see a list like "processors, memory, motors, sensors, etc" the first thought might be "Oh no I don't know any of that", but that's not a problem. Nobody starts off knowing it. You just pick a problem you want to work on and you start reading and trying things, usually failing over and over along the way until it works.
I only knew a little programming when I started on a web development career, and I just learned a lot along the way.
I'm surprised this comment even showed up on HN.