3 ms·
SWE doesn't have to be boring and repetitive. There are lots of interesting problems in embedded and HW system design/scoping (software engineers can be really
by ironman1478 5y ago
SWE doesn't have to be boring and repetitive. There are lots of interesting problems in embedded and HW system design/scoping (software engineers can be really useful for providing requirements to these systems). I work on cameras, specifically on dynamic controls (designing the algorithms + implementing in firmware) and it's so much more fun for me than writing web services, regardless of the scale. There are lots of jobs like this that make programming by, it's just that getting your foot in the door is hard because you have to have the experience. But what you don't have to do is grind Leetcode to get those jobs. You might just have to be willing to take a more junior position, since embedded is different. It took me 3 years to get here from a regular backend c++ job where I wrote the network backend for a database.
The only downside to these jobs is that they tend to pay less, despite them being very challenging.
- the_only_law 5y ago> There are lots of interesting problems in embedded and HW system design/scoping Every job I see in these sort of areas are very senior level of staff/principal and want significant domain experience in whatever the hell it is they’re doing. The exception being the lowest rung which always seem to exclusively target university pipelines.
- ironman1478 5y agoYou're right, but the jobs do exist. I'd look for jobs that are embedded linux based. If that's what they want, then they need somebody who knows how to write user space applications and are willing to learn a bit about HW registers. It's a way to get a foot in the door.