Plenty of work in the field, and in your area.
Skills wise, I'd expect you to demonstrate a good knowledge of "to the metal" programming - i.e. assembler, poking registers, dealing with hardware issues (handling/using interrupts, synchronisation primitives, managing performance and latencies, many other things). It's not just a case of "limited memory". Debugging using extremely primitive, often ad-hoc, tools is vital. Maybe you've only got a serial-port and printf. Maybe you've only got an LED to blink. Can you fix the code? Can you be certain it's good?
As others have pointed it, it's not just about programming, but about knowing exactly what how the hardware will execute your code, and what the implications and side-effects are.
Having said that, I know plenty of people who are both brilliant at it, and also largely self-taught.
So if you haven't done so already, get going on this kind of stuff in your spare time so that you can go into an interview with solid examples. Plenty of interesting platforms around you can hack around on now - ARM especially might be a good thing to know, so pick up a raspberry pi or similar and get stuck in.
Combine a solid engineering background combined with demonstrable knowledge and skill in low-level stuff, and you'll be in.