WJHat are you thinking of when you say "embedded systems"? It's a pretty broadly applied phrase.

In my view - and in the non-industrial/hobbyist/prototyping end of that space, I kinda divide things into "micro controller projects" where Arduino is king (but with other no-OS hardware platforms like ESP32/ESP8266 and many others, and other IDEs like Platform.io all playing catchup in market share) - and "embedded linux projects" where Raspberry Pi is similarly king but with many alternative linux capable SOC boards available too.

The Arduino/microcontroller path uses a form of C/C++ mostly (if you stick with Arduino IDE) but also MicroPython and CircuitPython. I consider this a "bottom up" approach to building computer controlled projects. You don't get Linux along with all the standard tools and utilities, you start from the event loop and write or import everything you need. This is often better for simple projects (blinky lights, PID controllers, simple automation, those are the sorts of things I've build that way), and for real time critical projects (like quad copter flight controllers) where linux on RaspberryPi can't guarantee you get the code paths running exactly when you need them. (RTOS on SOC board like RasPi solve those problems, but are a much smaller community and hence have fewer easily findable resources and examples, and also I haven't got any real experience with those (yet?))

The Linux/Raspberry Pi path - at least for me - usually gets taken when I've got ideas about some code I'd normally run on Linux, but want to do on a small machine or in a remote location with battery power. Probably 80+% of what I've built using Raspberry Pi starts out as some python or perl code (yeah, I'm old...) that I want to either run in a weird location (like in my garage, on the top of a mountain with a solar panel, on a camper van), or that I want to run as a low power inexpensive single use linux system (like my Pi Hole and my small media server).

When things get complicated, those two approaches often merge. A Raspberry Pi running python ro similar connected to an Arduino doing GPIO is a super common thing. Raspberry Pi (and most other Linux SoCs have 3.3v and fairly fragile gpio pins - it's easy to zap a Pi dead by being clumsy with connecting things to it). Arduino gpio pins are almost indestructible - they don't let the smoke out instantly of you short them to ground or Vcc/5V (you even get away with accidentally connecting them to 12V sometimes). The last hardware startup I was involved in was a product prototyped using RaspberryPi and Arduino boards, and manufactured using IMX233 SoC (very similar to a RasPi) and an ATmega328 (the micro controller on a Arduino Uno) on a circuit board we d4esigned - that ran almost unchanged code to the prototype. (I think we even shipped with the Arduino boot loader from memory? We could certainly flash new firmware to the AT328 over serial just like an Arduino.)

There is though, an entire universe of "embedded" out there I'm only fleetingly familiar with.

Cars are chock full of "embedded systems" these days, The anti lock brakes, the fuel injection, the airbag sensors - things like that are likely to be Arduino-style no-OS systems (but running on Motorola 68000 or something instead of ATmega grade microcontrolers). The dashboard and entertainment system and climate control are likely to be linux (or Android for entertainment systems?) more similar to a RasPi.

Industrial controllers are often decades old tech like SCADA, often with linux gateways more or less securely connecting their pre-security designed control planes to the internet...

Whitegoods all have microciontrollers in them these days. If I had to guess I'd say mostly Arduino-like rather than linux-based, but I din't _really_ know.