Finally found a definition that explained the difference between a IT Engineer & Architect:
Network Architect
Network Architects plan and design computer networks.
![]()
Not to be confused with Network Administrators who manage and support the network, or Network Engineers who build and repair it, Network Architects are responsible for the planning and design of data and communications networks. The responsibilities of these roles will overlap in some organizations, especially in startups and SMBs, however most enterprises and government agencies employ specialized professionals (or teams of professionals) in each position.
In addition to hard technical skills, network architects need to understand the company’s business needs in order to design an efficient, secure and scalable network that aligns with strategic goals. With a firm grasp on the business issues, the network architect can begin to craft the network blueprint, carefully considering aspects like which hardware, software and cable infrastructure will be best suited to the project at hand. A high-level position, most network architect jobs require 5 - 10 years of relevant experience, strong business acumen, and at least a bachelor’s degree in computer networking or a related field of study.
Looks like you can add IT Architect to your title/resume.
Engineer titles = people who build
Architect titles = people who plan and design.
Architects have technical knowledge but dont do the actual work. They are usually a level higher than Engineers and they focus at the strategic level of what needs to be done. Engineers do some planing/design but they are usually concern doing it at the project level. Some times Architects may be the managers of Engineers too. What ol boy is doing isn't Architect work if he is the person fixing things.
What's supposed to be the higher level job, IT Admin or IT Engineer? I was watching this video from a IT hiring manager & I'm kinda not sure anymore:
These two career categories are often confused but have important, discrete meanings that we need to understand as IT Pros or as managers.


type of post since I didn't take off career wise until mid 2014.