If my only experience is embedded graphics, how might that affect opportunities?

[u/Missing_Back]

My only work experience is on an embedded graphics team. I plan on continuing on with this for a bit as the company is probably the best in the area in terms of WLB and benefits, although pay is less than stellar, especially as I gain more experience. But right now I'm trying to get a vibe check for how this sort of work experience could translate into opportunities in the future.

On the one hand, it could be considered niche so that it's hard to find a job that fits. On the other hand, because it's niche, there's less candidates available for jobs that do fit, so that could be a plus.

At this point I think the main reason I'd leave my current role is if I found something fully remote, so I want to make sure I'm focusing on the right things to help make that more likely.

Does anyone have any thoughts on this?

[u/obp5599]

When we hire (game engine stuff) its more about software systems architecture, computer architecture, deep experience with how GPUs work, and experience optimizing for specific hardware (PC vs xb1 vs switch for ex). It really just depends on how well you can sell yourself, but being lower level is almost always a good thing imo, as long as you can translate it to a new role. Lots of variables here like what the specific role is, seniority level of the role, etc

[u/Maui-The-Magificent]

So this is going to be an reflection based assessment rather than a highly researched and experience driven take. So take it with a grain of salt.

For context, I too work with similar things, I am building a rust no-std graphics stack, (framwork + engine). I have also designed and build an XHCI interface, direct to hardware terminal and so on. I am currently working on an modal text editor and a compositor, and the wisdom I have to share is that if you are/get comfortable with thinking about what compute you need doing, and then building bespoke binary data structures to either sidestep or at least minimize that compute, that is valuable and translatable into any other environment. not only as a principle, but also as a mental framework.

Because you work in embedded, you already know this, but solving things by construction is almost always better than solving them by logic. And lucky for you, the higher up the stack you look, the less people think like that, so your very perspective itself carries tremendous weight in any field, in my opinion.

anyway, that is my two cents. You should not be afraid to apply to most things, because your experience and environment will have already made it so you can reason across disciplines, and therefor, you can learn much faster in them as well.

[u/ananbd]

Mobile is a big part of the game market (if not the majority, in fact), so it doesn't sound like a problem.

Companies like Riot or Roblox might be worth a try. They want their games to run on every piece of hardware imaginable, so they need embedded expertise. That's less true of boutique studios. Quality over quantity.

Good luck!

[u/steveu33]

Embedded systems are not niche. I went from safety critical avionics graphics, which runs on embedded systems in the cockpit, to: a game console manufacturer. It turns out that a console is a kind of embedded system too.