What Makes a Good IT Systems Engineer?
In today’s IT-enabled world, a good systems engineer, or administrator for that matter, is one of the lynchpins of any enterprise because they ensure technology works as it is intended.
They ensure all systems in an organization work well together. They are responsible for streamlining those systems, but also developing and implementing new technology. They are also the ones that are called upon when there are problems.
Let’s take a closer look at what an IT systems engineer is and what they do.
What Is an IT Systems Engineer and What Do They Do?
An IT systems engineer develops, tests, implements, and evaluates software, servers, network computers, workstations, and more. They develop and implement new software, improve existing processes, upgrade hardware, and do whatever else is necessary to ensure that the organization has streamlined and functional s that can meet the business needs. Systems engineers are generally very knowledgeable in mathematical analysis, computer science, and engineering.[i]
Systems engineers understand technology beyond merely engineering it. They understand the role it plays in the larger picture of the organization’s and the individual’s ultimate objectives.
In terms of the actual job description, some of the responsibilities of a systems engineer may include, but not be limited to[ii]:
· Installing and configuring hardware and software
· Managing servers
· Setting up workstations and accounts
· Maintaining and operating systems
· Troubleshooting
· Ensuring security
· Upgrading systems
· Training staff and customers on new technology
However, that’s not all. Different companies will have differing requirements in terms of their systems, which means that a systems engineer’s day-to-day duties might differ significantly from one organization to another.
For example, a manufacturing firm might require unique inventory tracking systems. On the other hand, a cybersecurity firm might require their systems engineer to consult with clients on hardware necessary to support the security system being developed.
Therefore, a systems engineer might also consult with clients on what the right software and/or hardware they need to make certain that their IT system meets their requirements. They might also have direct involvement in the purchasing, installation, testing, and implementation of a project.
Systems Engineers will also evaluate the existing infrastructure to determine how effective it is and advise on how scalable said infrastructure is. Of course, they will also be responsible for resolving any problems that occur when the system is being used.
As the internet now plays a massive role in most companies’ operations, a systems engineer will also review and recommend security measures that will allow the enterprise to operate online safely.
In other words, without a good IT systems engineer, an organization is likely to crumble like a tower of cards when one removes the vital foundation.
What Is Expected of a Good IT Systems Engineer?
Systems engineering is a relatively young discipline compared to other engineering fields. There are no clear-cut rules or formulas to designing and maintaining effective systems.
An architect will only know if the public likes the building they’ve designed only after it has been built. Likewise, a systems engineer won’t know how effective or useful their system is until it has been implemented and people are using it. Can someone say — validation?
While a systems engineer has access to a wide range of incredibly helpful tools to assist them, they still have to rely on their own knowledge, skills, and a dash of intuition when they are developing and enhancing a system.[iii]
A good IT systems engineer requires knowledge of different disciplines, such as computer science and mathematics. However, while a strong technical background is necessary, they also need a series of “soft” skills such as leadership and communication.
Let’s take a more in-depth look at some of the skills and traits that a good systems engineer should have.
Ownership — You Build It, You Own It, You Monitor It
Traditionally, the development team would design and develop software, which they would then pass on to operations. They’d never see it again, unless it breaks. However, things have changed significantly and now the accepted best practice is “you built it, you own it, and you monitor it.”[iv]
This works because it creates accountability but also because the developer can gain a far greater understanding of the software they have created in its “natural habitat.” Something might look great in controlled conditions, like lab tests, but once its out in the wild with “regular” people using it, it can look far different.
This approach also forces the team responsible for development to take a far greater level of responsibility for the work they have done.
This also applies to a good systems engineer. They need to fully embrace the YBYOYM concept. They need to live it and breathe it because it is essential to a company’s smooth and continuous operation.
Instead of just implementing changes without concern for the bigger picture, a good IT systems engineer understands that everything they do has an impact on the entire organization. So, they will work with those who would be affected by the changes they want to make.
“The two words ‘information’ and ‘communication’ are often used interchangeably, but they signify quite different things. Information is giving out; communication is getting through.” — Sydney J. Harris
They will not pass responsibility onto someone else for the system they designed and implemented. They will be right there, all the time, working to make it better and to ensure that it meets the needs of their organization.
A great IT systems engineer will accept that they aren’t infallible and the system they built is unlikely to be perfect, in fact, it should always be expected to fail. They will solve problems without letting ego get in the way. They will accept failure is a part of life and will quickly move on without feeling the need to point fingers. Of course, they will also closely monitor their system to ensure that it is performing as desired.
Results-Driven
A good IT systems engineer is driven by results, therefore metrics is a second language to them. They are able to see both the small and big picture[v], which allows them to acknowledge the fact that the system itself isn’t the goal, but what the system does for the organization.
In other words, while they certainly should be detail-oriented so that errors don’t slip through, their ultimate goal isn’t to create a “sexy” system, but one that does the job it’s supposed to do.
They understand the concept that features don’t “sell” a product. It’s the benefits that matter. People don’t buy a drill because they want the drill. They buy it because they need to make a hole.
Likewise, a system shouldn’t be built for the system itself but for the benefits it offers, and all “features” need to support this idea.
A particular architecture might seem new, exciting, and sexy, for example, but if it doesn’t support the goals of the organization, it has no place in the system being developed. One must start with the customer needs and work backwards.
Technically Well-Rounded
A good systems engineer is technically well-rounded. They don’t just know concepts related to systems engineering or obtain a certification for the sake of having it. Instead, they expand their knowledge in other topics related to their field. They know that the more knowledgeable they are, they more effective they can be in analyzing and finding potential problems.[vi]
They are also dedicated to expanding their knowledge and skills constantly. They love to learn and are excited about working with all sorts of technologies. They also have no problem admitting their weaknesses and take measures to improve those areas.
Understands Business Continuity and Recovery Planning
As IT systems are central to many company’s operations, it is essential for a good systems engineer to understand business continuity and recovery planning.
Businesses face potential disruptions all the time, though many only discover the value of planning after a disaster has occurred.
A good systems engineer will not only understand how important it is to ensure business continuity, but is also adept at developing, testing, and implementing plans to this effect. They also understand that their plans must be effective, so they don’t create a plan just to have something. They do it with the idea that something “will” happen, rather than something “might” happen.
Great Communicator
Systems engineers need to be great communicators because they interact with a lot of people, from internal users to clients. They need to understand how to communicate with people that don’t have a technical background.
Unfortunately, communication is not often seen as an important skill, and some systems engineers are not quite as well-versed as they should be. While this is a skill that requires practice and time to improve, it’s necessary because no systems engineer works in a vacuum.
A systems engineer has to communicate with users to understand the problem they might have to solve, but they also need to translate customer and user requirements into something engineers can use. In other words, systems engineers need to be skillful communicators on both sides of the spectrum since they work with the technically proficient and those with limited technical understanding.
Religious About Documentation
Writing documentation might not seem all that important, but it is vital to the smooth running of a system and organization. A good systems engineer needs to understand the importance of documentation. They need to enjoy writing it because they are aware that it is valuable and an important part of their job.
Of course, this doesn’t mean that a systems engineer has to be a novelist. They simply need to write documentation with their audience in mind while ensuring that it is well organized. They create documentation that is accessible and useful, ensuring that if they were to depart, they person who came after them would have no problems because they had all the information they needed.[vii]
“If documentation is not actionable, it’s simply information, not communication”
Automation Expert
A good systems engineer is an automation expert. They know automation can save time and streamline processes so they are adept at identifying where and what can be automated.
They look at manual processes that they (and others) do frequently, but also analyze complex tasks that can be streamlined. They also have the skills to design and implement the automation necessary. This is particularly important as we move to a Cloud transformation where there is absolutely no human hands touching systems in a production environment.
They certainly never waste their time on processes that can be automated just because automation might seem a little more complicated.
Strong on Security Best Practices
As previously stated, businesses face many potential disruptions, but few are quite as problematic as security issues. A data breach, for example, can have far-reaching consequences and can lead to problems some businesses will have a hard time recovering from.
A damaged reputation and lack of consumer trust are just the tip of the iceberg. Then one has to consider the legal ramifications, the fines, and so on.
A good IT systems engineer will be very well-versed on security best practices because they are the company’s first and best line of defense. They are fully aware of the damage bad actors can cause and work tirelessly to ensure the company is inline with the latest in security best practices.
Validates Everything
A good systems engineering will validate everything because they see the big picture and understand that without validation, there is no successful implementation.
They aren’t developing software or hardware systems for the fun of it. They understand that every component needs to meet the purpose and function the system was designed for. To that end, they constantly validate to ensure that the system performs as it was meant to do.
Fluent in AWS, Azure or Google Cloud
With an increasing number of companies transitioning their critical IT infrastructure to the cloud, it is mandatory for a systems engineer to be fluent in AWS, Azure or Google Cloud.
A good systems engineer will never rely on an external party’s knowledge and skillset. Considering that a large part of their system will be in the cloud, it is therefore mandatory for them to be skilled and knowledgeable of that end of the system as well. After all, a systems engineer is responsible for the entire system and not just what is on-site.
It’s No Longer About Systems but the End-to-End Solution
The key to being a good IT systems engineer is to understand that it is no longer just about the system, but about the end-to-end solution. It’s about delivering the results the company needs to operate effectively and efficiently, which means an IT system that is streamlined and that fulfills its purpose and function. It also means working with others to ensure the system delivers.
Changing the title from Systems Administrator or Engineer to Solutions Engineer has been trending, at least for the past ten years it seems. This reflects the need to refocus the systems driven scope of work to design, build and maintain systems, to a solutions-driven one that produces tangible, verifiable results.
Conclusion
An IT systems engineer is akin to a conductor in an orchestra. They are in charge of ensuring that each component works well and that they all come together to create a beautiful piece of music, or a highly efficient IT system that supports the company’s operations and objectives.
For this reason, a good IT systems engineer will be technically well-rounded but also have a range of “soft” skills, such as communication and leadership.
They need to see the bigger picture to ensure the system is delivering in line with its purpose, but they also need to be detail-oriented so they don’t miss errors.
They also need to be able to think outside of the box, because systems engineering is often just as much science as it is art.
[i] “What Does a Computer Systems Engineer Do? ‐ CareerExplorer.” https://www.careerexplorer.com/careers/computer-systems-engineer/.
[ii] “System Administrator Job Description | Workable.” Recruiting Resources: How to Recruit and Hire Better, April 21, 2017. https://resources.workable.com/system-administrator-job-description.
[iii] “Traits of a Brilliant Systems Engineer (This Should Be Your Next Hire) | LinkedIn.” https://www.linkedin.com/pulse/traits-brilliant-systems-engineer-should-your-next-andy/.
[iv] “You Build It, You Own It!” http://aronatkins.github.io/2014/12/23/you-build-it-you-own-it.html.
[v] “10 Qualities That Make a Good Systems Engineer — Specinnovations.” https://specinnovations.com/10-qualities-that-make-a-good-systems-engineer/.
[vi] “System Administrators: 10 Best Practices for Career Success & Happiness.” The Devolutions Blog. /2018/02/system-administrators-10-best-practices-for-career-success-happiness.
