HN is dominantly a web/SW crowd plus some mobile frontend, and "it uses a Snapdragon" gives many a wrong idea. In embedded device projects a lot of time is spent planning and designing around a heavy compute element running Linux like this, especially if the device has a safety concept or other mixed criticality concerns. It will have a substantial moat around it.
On HN if you say "systems architecture" most folks go "Oh you mean like, whether we use microservices?". In embedded, while there is a lot of overlap and analogues, it's also all of the above, plus power state management and other aspects. It's not very shiny, but that profession makes all your cars, airplanes and alien planet multicopters.
"It's not very shiny, but that profession makes all your cars, airplanes and alien planet multicopters."
If you have a good head for it, it's a pretty darn good career. You might not make $500k/year like you would at google, but the money is still decent and reliable.
HN is dominantly a web/SW crowd plus some mobile frontend, and "it uses a Snapdragon" gives many a wrong idea. In embedded device projects a lot of time is spent planning and designing around a heavy compute element running Linux like this, especially if the device has a safety concept or other mixed criticality concerns. It will have a substantial moat around it.
On HN if you say "systems architecture" most folks go "Oh you mean like, whether we use microservices?". In embedded, while there is a lot of overlap and analogues, it's also all of the above, plus power state management and other aspects. It's not very shiny, but that profession makes all your cars, airplanes and alien planet multicopters.