Photo: Marián Hubinský (CC BY-SA 4.0)
Job description
Engineers start by talking with staff or clients to pin down exactly what a system needs to do, then investigate whether specific components actually suit that purpose before recommending them. The job includes directing the installation of operating systems, network software, or hardware, and providing implementation teams or customers with guidelines for building the system securely. Once a system is running, engineers monitor its operation to catch potential problems early and identify what data, hardware, or software components are still needed to fully meet user needs. Dealing with frustrated staff or clients when something isn't working as expected is a regular part of the job.
Pros
- Much faster than average projected job growth (8.2% over the next decade)
- Pay can reach $188k without requiring a four-year degree
- Standard 40-45 hour weeks keep work-life balance more predictable than many tech roles
Cons
- Regularly dealing with frustrated clients or installation teams when systems don't work as expected
- Entry-level pay starts well below the ceiling, near $56k
- Requires staying current on a constantly shifting landscape of systems and components
A typical day
A client kickoff opens the day: their order system crashes weekly and nobody knows why, so the engineer asks questions for an hour — traffic patterns, hardware age, what changed before the crashes started — before touching anything. The middle of the day is design: evaluating whether the fix is new servers, a re-architected database layer, or both; pricing components; testing a candidate configuration in a sandbox to see if it holds under simulated load. Then comes the write-up: an implementation guideline the client's own team can follow, with the security settings spelled out because defaults get people breached. Two smaller projects need check-ins before the day ends — an OS migration mid-rollout and a hardware install next week.
Tasks at the job
- Communicate with staff or clients to understand specific system requirements.
- Investigate system component suitability for specified purposes, and make recommendations regarding component use.
- Provide customers or installation teams guidelines for implementing secure systems.
- Direct the installation of operating systems, network or application software, or computer or network hardware.
- Monitor system operation to detect potential problems.
- Identify system data, hardware, or software components required to meet user needs.
Workplace & working conditions
Work happens indoors in a climate-controlled setting, and most of the day is spent sitting at a desk.
There's a regular, moderate amount of time pressure, and you're expected to exercise significant independent judgment day to day. You'll regularly deal with frustrated or upset people as part of the job.
Education necessary or common
Vocational training, apprenticeship, or associate's degree
Common college majors
Licenses & certifications
- CompTIA A+/Network+/Security+
- Microsoft or Linux system administration certs
- Cloud architect certifications (AWS/Azure) as careers advance
Career path
Related fields
Courses to take
- AP Computer Science A — build the technical core
- AP Computer Science Principles — networks and systems overview
- Physics — hardware behavior is physical
- Algebra II/Precalculus — capacity and performance math
- Public Speaking — you present recommendations for a living
Clubs, activities & competitions
- CyberPatriot — systems hardening under competition pressure
- Coding club or robotics
- Home-lab hobby: virtual machines, old servers, network experiments
- School IT volunteer work
First steps you can take now
- Install Linux on an old machine and run one real service on it
- Learn virtualization free with VirtualBox — build a three-machine lab
- Take a systems administration intro course online
- Diagram the full system behind an everyday action, like ordering food on an app
