What are the high-level differences between an architect and an engineer?
This is a general knowledge question intended to identify candidates that have a solid understanding of the roles that are typical within a technologically mature organization. Many technical program managers work closely with these two roles, and it is important for candidates to be knowledgeable about what to expect from architects and engineers respectively.
Remember to include a comparison of the scale of the work for architects and engineers. For example, architects work at a higher level to set standards and the framework for large solutions while engineers make code-level decisions that are focused on the lower-level details that make up larger solutions.
"The difference between architects and engineers can vary depending on the company, team, and implementation of the role. However, generally speaking, architects are typically responsible for planning, design, standards, frameworks, research, and high-level quality control. They are senior technologists that have a depth of engineering experience. They partner with roles such as business consultants, senior user experience designers, senior engineers, product managers, and clients to understand high-level requirements and translate them into strategic technology plans. They help to define the technology stack that will be used and how the various components will work together. Architects research the latest technology and assess new tools for their ability to integrate into current solutions. Finally, architects often mentor development teams to resolve complex technical issues and ensure that quality standards are met.
Engineers take the plans that are developed by architects and put them into practice. They help translate business requirement-based designs into functional and technical requirement-based solutions. Engineers use the tools available to them to develop integrated and extensible solutions that meet the lower-level and specific needs of their users. They continually review their code for quality improvement opportunities and research ways to improve tactically. They provide insight to more senior-level resources on the feasibility of high-level standards and change requests."
