The grass is always greener. I've been doing embedded for 13 years and it's not peachy. You use C mostly, or C++ that looks like C. You write bootloaders and sa

The grass is always greener. I've been doing embedded for 13 years and it's not peachy. You use C mostly, or C++ that looks like C. You write bootloaders and same drivers over and over. There's constant diagnostics and same arguments - is it SW issue or HW issue? How can we work around HW issue with SW patch? Embedded development is more about engineering than about software development. Memory and space constraints are harder, shipping errors is so much more expensive and you spend about 50% of time in datasheets and schematics. I see no reason why you couldn't make the switch. It is I think less lucrative than some other branches, and far fewer people apply for embedded position. As long as you demonstrate that you are reliable and interested, you should have no problem getting the position with no previous experience. Of course, this depends on your location. There are far less job offers for remote work, and it would complicate the learning process.