The Complete Guide to Becoming A Computer Systems Engineer/Architect

Chapter 1: What Does a Computer Systems Engineer/Architect Actually Do?

Let's cut through the title and get to the truth. A Computer Systems Engineer/Architect is the person who designs the blueprint for how an organization's computers, servers, storage, and networks fit together, and then makes sure that blueprint actually gets built and keeps working as the organization grows. You are not the person replacing a broken hard drive at a help desk. You are not the programmer writing the code for the company's main app. You are the person who decides, "We need 200 new virtual servers in the next year, we'll host them in the cloud on Amazon Web Services, and here is the security firewall configuration that will keep them safe." It's a role that sits between pure business goals and pure technical execution.

To understand the day-to-day, you need to picture the work in three overlapping layers. The first is design and planning. A manager from the finance department comes to you and says, "We're buying a new accounting system and it needs to handle 10,000 transactions an hour." Your job is to figure out what kind of servers are needed, how much memory and storage they require, what network bandwidth will be necessary, and whether the system will run on physical hardware in the company's own server room or on rented cloud services from a provider like Amazon, Microsoft Azure, or Google Cloud. You'll draw a diagram of how all these pieces connect, estimate the