As a former game dev turned regular old swe, I highly recommend just going the indie route (i.e. nights and weekends). Game dev is just doing software engineering, just harder (oh those trig classes matter! calculus has a purpose! linear algebra all day! ), that pays less,with the same or worse politics (studio bosses instead of eng/prod directors), and in most cases doesn't result in a playable game. Sorry, I'm jaded, left that industry at 27 and never looked back. One of my old bosses once told me that new 22 year old CS grads were "meat" for the grinder, and after even 3 years I knew why that's true.
This is the first time I’ve heard someone be optimistic about embedded. Better than game dev or EE but that’s only one step up on the work/pay ladder. I find my work interesting but I would have made a lot more optimizing the search bar on the Facebook android app or whatever.
Few weeks back, others were talking about embedded getting paid less than web app development. What would you say, true? I understand that they aren't getting laidoff, there's a big gap in high demand and low number of experts in this field.
Definitely true. You’re not gonna starve, if you doing embedded at $BIGTECH probably 200-300k TC, but there will be a discount compared to the regular software engineers wherever you’re working.
I think a lot of big tech companies are getting into hardware in order to diversify and help build a platform to support future online components. Meta has AR and VR, Google has Nest and Fitbit, Apple obviously makes tons of hardware, Amazon with Alexa and warehouse robotics. All of the above make custom servers which require firmware. Even Netflix has some embedded devs working on supporting streaming devices.
What’s nice is that embedded swe equals regular swe salaries at these companies! I am an embedded dev at a big tech company and interviewed at most of the FAANGS recently.
Any FAANG. But take a look at square for example because they’ve posted more reasonable salary ranges than most. Senior android engineer, 222-272k. Expired now but they had a senior firmware engineer for 202-247k.
Unclear if those are base or TC, if it’s base then you’d definitely be over $300k with RSUs, but even if it’s TC a good year in stocks pushes that over.
The stories about embedded I've heard is that they've got outsourcing partners in India and China delivering shit-tier code and hardware that they need to fix themselves, on top of their actual jobs. YMMV though.
(Mobile) game jobs aren't a more work less pay environment in the least, the successful ones make so much money that the companies want to keep the teams who made the game at all costs. The companies also recognise that it's the people who make the games, so the pay and bonuses reflect that.
And because the successes are so big €€€-wise, most companies can afford to spend time making the next big game instead of forcing people to crunch and sleep under their desks.
PC/Console gaming is a whole different world, don't know much about that.
My experience in embedded was great except for the: more work, less pay, more irrational management part. I doubled my salary moving to web backend services.
As another ex-gamedev let me pile into this thread and concur with the parent. There's a very high chance that even if you break in you won't work on the game types that brought you there(I didn't) and pay/work life balance will be hell.
If you really want to do it, side projects are the way to go. There's a ton of good engines out there and way more resources than when I was in the industry.
What would you recommend for someone who thinks the math part is interesting (and yes I know in normal game project Unity or Unreal Engine would handle it), but isn't that interested in in promoting their indie project?
Oh, yeah, game mechanics or game physics engineering is amazing, but understand it's about 1% (if that) of what makes a successful game. I was watching my nephew play Fortnite over thanksgiving and thinking to myself "gee, the graphics are shit, essentially low-poly with some nice shaders!". And CoD Black Ops puts the physics to shame (and thinking that old timers used to tell me the physics of that were bad compared to e.g. PubG/Battlefield). But Fortnite is super colorful, and for a kid just coming off Roblox, it's accessible enough to play. So the HUDs and UIs and leveling and map dev and a million other admin tasks are where the majority of your game dev experience will be. Even doing some (gasp!) web dev, for things like in game stores and so forth. The gameplay mechanics and physics math of particle engines or calculating missile intercepts or inverse kinematics (jacobian matrices anyone?) for skeletal animations are mostly solved problems, but they can still be interesting to reimplement.
Back when there was no commoditization of game engines, every team starting a game had to do their own engine, tools etc.
Now that you have unreal and unity etc, you can actually concentrate on game design and gameplay instead of worrying about the engine and tooling.
I agree though writing a game engine and physics engine is very interesting. I used to work for the R&D team of a casino games manufacturer. We created our own in house game engine. It was fun, but adding any new feature would take a very long time. In the end we shifted to unity.
To me it sounds like someone's still making a living from R&D even though the big money is at casual games and selling diamonds or hats in in-game stores. The question is just how to get that job.
More accurate to say that fortnite is developed alongside unreal engine, they make unreal engine in house so they make their own engine. For example unreal engine 5.0 was very buggy, since they made it to work with fortnite first so only fixed the features that game used.
Exploration geophysics, remote sensing, satellite navigation, etc.
Fugro, Siemens, et al - Earth visualisation, medical imagery, etc.
The emphasis in these fields is getting visualisations and computations correct rather than convincing.
ie. The math part is interesting.
In remote sensing you might find yourself doing a continous pipelined SVD reduction of 500+ dimensions from a spectrum sensor to some three axis RGB like space to create a viewable image from a non visible part of the EM spectrum.
Sure, I spent most of my career working for small nimble outfits that ultimately sold product to large crappy companies while moving on to other challenges.
The pipelined SVD reduction mentioned was written while working with a small company with 13 airframes (fixed wing and helicopters) that did full spectrum rad+mag+grav+lidar surveys of small country sized areas (Fiji, Mali, other similar sized regions) and eventually sold to Fugro.
Sometime before that there was something that was aquired and became [1]
If you think that the math part of game engines is interesting but aren't that interested in promoting an indie project, then you should look for jobs in robotics or computer vision applications. There isn't a large supply of jobs for replicating what can be handled by Unity or Unreal Engine.
What is it like to work in computer vision these days? I did some courses back in the day and it was interesting, but to me it seems that it's now devolved to looking up convolutional DNN architectures and trying which one works best for the problem at hand.
Actually there’s still quite a bit of math involved implementing gameplay mechanics and it can be quite a bit more off the cuff and experimental which people might find fun. The equivalent of writing shaders rather than a rendering pipeline.
I've made my own simple physics engines and used linear algebra to do things like projecting from 3d to 2d space. None of it was any good but it was a lot of fun. This was back when I was most comfortable in Java and the performance was horrible. I don't know what methods of collision detection real engines use but Runge–Kutta is not a good option for real time games.
I don't know how to do it and make money but I would recommend playing with the math. It's like magic, you setup the formulas and things just start moving on the screen. It was so much fun.
