To the optimist, the glass is half full. To the pessimist, the glass is half empty. To the Systems Engineer, the glass is twice as big as it needs to be. – Anonymous
I’ve observed how the role of systems engineering and their utilization vastly differs across industries over the course of last couple decades. This post is to share my experience, observations, and thoughts.
To clarify, when I say “systems engineering”, I’m not referring to the role related to IT.
Traditionally, systems engineers were predominantly mechanical and electrical engineering background. However, as software systems started to become exponentially larger and complex (software intensive systems), people with software engineering background have stepped in to fill the responsibilities. I happen to be one of those software systems engineers.
One important point to highlight is that software SEs are not (and should not) be different than traditional systems engineers. Software SEs follow the same principles, methodologies, and techniques, but rather a specialization for software intensive systems.
In some organizations, I’ve noticed software systems engineer team is separately formed under the software function. In addition they are tasked with non-SE activities such as managing JIRA tickets and grooming. I believe this is a misutilization of SW SEs, at least it’s not what I would label with a “systems engineering” title.
Systems engineers, regardless what type of systems they specialize in need to be involved across the entirety of the system end-to-end spanning inception, planning, design and build, V&V, release/installation, sustaining, and decomissioning. A software SE shouldn’t just be focused on “software development”.
Do you need experience as an SE?
This topic has come up numerous times over the course of my career. There are always exceptions, but what I share here are my general views and opinion.
Systems engineering is largely about having the proper “breadth” and “depth” that are obtained over the years. This experience is not something which a person can gain from “reading a book”.
Experience is not everything, but it’s not something we should overlook. I view experience as one of many “ingredients” needed for an SE. Only having gone through each stepping stone does one gain the deep understanding of the challenges, risks, pitfalls, dependencies, and mitigation techniques.
How do you expect somebody to create an Italian recipe book if they’ve never even cooked pasta before? – Vanilla Rice
School nowadays offer a systems engineering degree and system engineers are hired into entry level positions. This in my opinion goes against the very nature of systems engineering and the source of why many modern organizations have underperforming systems engineering teams.
I strongly feel for someone to be an effective SE, they need to have come from preferably a STEM discipline who has experience creating such products/systems. Without this, It is likely there will be gaps between SE and development teams.
Final thoughts
There are many reasons why an organization may have underperforming SE teams. While each organization may have their reasons, I think it may be worth looking into making systems engineering a career path.
Leave a Reply