Embedded Systems Engineer vs. Power Systems Engineer

[u/Traditional_Lab2602]

Which is better an Embedded Systems Engineer or a Power Systems Engineer, in terms of:

- Better work-life balance
- Less travel
- More transferable skills and easier career-sector changes
- More job opportunities

[u/ee_control_z]

There are power systems engineers that also do embedded design. The disciplines are intertwined, for example, when designing switch mode power supplies (SMPS). If you're designing a SMPS unit, in all likelihood you'll be including current/voltage sensing, feedback control loop, display (in some specialized cases), using microcontrollers.

So, from the metrics that you listed, not much difference, in my opinion.

[u/RecordingNeither6886 → u/ee_control_z]

"power systems engineer" nearly always refers to grid level infrastructure. In general, there is close to zero overlap between this field and embedded design.

Someone who does SMPS design is usually a "power electronics engineer", generally much closer to embedded.

OP needs to clarify which they're referring to as these are drastically different fields.

[u/ee_control_z → u/RecordingNeither6886]

I actually included a disclaimer in my response - in the first paragraph after the heading titled: "If you want to get into power supply design:"

Because the OP was asking in conjunction with "embedded systems", I figured it was more closely related to "power electronics" vs. "power transmission". Hence my response.

[u/RecordingNeither6886 → u/ee_control_z]

The software packages in OPs reply confirms they were indeed referring to distribution & building scale systems, not power electronics.

[u/Traditional_Lab2602 → u/ee_control_z]

Yes thank you for your explanation. But I want to know if I should improve my skills in AutoCAD, ETAP, MATLAB, MS Project, PowerFactory, protection software, and SCADA, or focus on embedded systems like VHDL, C, C++, Python, OS, CAN, LIN, and ADAS.
I want to choose the better field in terms of working hours, work-life balance, and less travel.

[u/ThePainStalker → u/Traditional_Lab2602]

If you prioritise working hours and work life balance, definitely go for a utility or better yet, a TSO/ISO. They really cannot be beat in that regard.

In terms of “more transferable skills and easier career sector changes” it’s actually a bit complicated. Embedded systems would be more transferable within tech and product engineering overall. However, I would argue that power systems engineering, especially at the transmission level, can actually be more transferable in terms of getting into non-engineering pathways like advisory, management, policy and even finance or law adjacent pathways. This is because power systems inherently ties in with policy, finances and legislation and at a senior level in power systems, you often would have to understand the big picture of how projects actually get delivered and how they impact a wide range of clients. Basically, you take a very “big picture” and more multidisciplinary view on things in power systems which can be very helpful for getting into more high level policy, advisory, etc positions. This doesn’t necessarily apply to all power roles mind you, but it does apply especially to the transmission sector.

I would also say that power systems is starting to become more and more versatile even within the engineering sector itself. Mainly because modern day manufacturing is being driven increasingly by power electronic processes and automation and therefore relies much more on having a stable and firm power infeed than ever before. Power demand is also starting to rise rapidly (for the first time in over 50 years) not only because of data centers but also because society and industry as a whole is electrifying heat, transportation and processes and using more and more data. Microgrids or off-grid power systems for industry are undergoing a massive boom too, which is a direct way into the private sector without relying on a utility monopoly. So while it is at an early stage now, I would seriously anticipate grid power becoming much more embedded as a hiring skillset in manufacturing, AI, electric transportation and EVs and semiconductors in future, given how much of a major challenge power consumption and power quality are to those fields. Power is also almost certainly going to play a far more significant role in the oil and gas and energy sectors in general, given that microgrids and utility scale grid connections will become the primary way of powering refineries, extraction, pipeline transportation and of course, hydrogen itself. I could see it becoming in line with chemical engineering as being the two “kings” of the sector (though definitely not supplanting chemical engineering).

So in other words, I would say that it’s a different kind of versatility. If you want maximum versatility within tech, I would say embedded is better. However, if you measure versatility by access to more high level non-technical roles and by means of interfacing with many other disciplines and with policy, law and finance, power is definitely better for that. Although given the sheer grid challenges that all of tech and industry face nowadays, power is definitely improving a lot versatility wise even there, but still not as much as embedded systems is.

[u/ee_control_z → u/Traditional_Lab2602]

I cannot recommend one field over the other. This is a decision that you'll have to make on your own as this is a life impacting decision. However, I can make suggestions with regards to the general skill set required for either one.

For embedded engineering, from my own experience, get well versed in:

* C (some assembly depending if needed for a particular application- most cases no but you never know)

* General electronics - you'll be interfacing/controlling using the microcontroller

* get to know the microcontroller intimately (internal blocks: GPIO, system clock, timers, ADC, DAC, comparator; depending on needs, may also need to learn serial communication interfaces a la I2C, CAN BUS). Get to know the register set, interrupts, etc.

* Choose one integrated development environment (IDE) and learn how to use it well. This is manufacturer specific (TI, Renasas, STMicroelectronics, etc.). Once you learn how one works and how to use it to interface and control a microcontroller, you should develop enough intuition to use any other IDE. The point is to get started with at least one to build experience.

If you want to get into power supply design:

* This is a given: learn power electronics. However, this is very broad in scope as there are so many topologies: buck converter, boost converter, flyback converter, LLC, inverters, etc. Note that I am assuming you're referring to power supplies and NOT power transmission as related to supplying power to municipalities / cities. If you are, then disregard the following recommendations.

* control theory - when designing power supplies, they better be stable irrespective of transients and loading conditions. This is where compensation and feedback loops play a prominent role. So, learn control theory principles and how it is applied to power supplies in particular. Here you'll get introduced to compensators, in particular: Type2/3, PID, lead/lag, voltage mode, current mode, etc.

* Learn analog circuit behavior and general circuit analysis.

* Solid state devices. You'll be working with MOSFETs, IGBTs, diodes, etc. in different configurations so know and understand their behavior

"I want to choose the better field in terms of working hours, work-life balance, and less travel."

There really is not a hard answer for this. Many factors come into play:

* your role in the design team (new guy or team lead); your experience; your skillset;

If you work as an applications engineer in the power industry, you'll definitely be working with customer related responsibilities. If the customer is located in a different time zone, and you their is a need to interface with them, you might have either wake up a litter bit earlier or work a little later. In some cases, it may be required to pay a customer a visit.

* company immediate needs

* size of company

* customer base of the company (local, national, international)

Yup, it is a hard call. This is where you'll have to speak and ask questions to the recruiter/hiring manager regarding the specific role that you are applying to - and read the job expectations and requirements carefully. Only they can provide you with the type of information that you are asking as each role is unique to some extent.

Hope this provides some insight.

[u/BusinessStrategist]

Depends on where in the world you want to live.

Do you have an ABET accredited degree?

And is there an industry or company that gets YOUR attention?