1. Get the Job
  2. Get Ahead
  3. Office Life
  4. Work-Life Balance
  5. Home Office
Product and service reviews are conducted independently by our editorial team, but we sometimes make money when you click on links. Learn more.
Build Your Career Get Ahead

How to Become a Cloud Architect

How to Become a Cloud Architect
Credit: winui/Shutterstock

While architecture sits at the heart of all things IT, it's not the same kind of architecture that produces palaces, museums and bowling alleys. Rather, it's a formal discipline within the field of computing that concerns itself with how systems are designed, composed and orchestrated.

Much like the other kind of architecture, IT architecture is both an art and a science. It's as much about understanding and accommodating the people who make use of computing and the services it can deliver as it is about the systems used to run them and the networks that tie them together. IT architecture also concerns itself with best practices and with making sure that technology remains the servant of the organization that owns or operates it, rather than becoming an end in and of itself.

Over the years, as IT has become vastly more complex, numerous types of IT architect job roles arose. Today you can find jobs that include enterprise architect, application architect, storage architect, database architect and so on, with the cloud architect as one of the most important in that entire class.

Cloud architecture is a relatively new discipline, with its roots in software development. Today's cloud architect plans and designs cloud environments, and typically provides guidance throughout the life of a development or deployment project. A cloud architect must understand the concepts and moving parts involved in continuous integration and continuous delivery, and provide expertise on infrastructure and build-and-release to development teams.

But cloud architects do much more than design systems or IT environments. They must also take ownership of such systems or environments throughout their lifecycles. Architects get involved with initial requirements analysis and see things through all the way to retirement and replacement much further down the road.

On the business side, cloud architects seek to understand what kind of functionality is needed, what it's supposed to do, what kinds of competitive advantages it might deliver and so on. From the technology side, cloud architects decide what kinds of systems might be needed, which vendors to do business with, how to integrate pieces and parts from different suppliers, and which APIs and standards to adopt. It's a big job.

Cloud architects must possess or develop a sizable collection of skills. Surprisingly, this is one role where soft skills play a crucial role alongside technical skills. Here's a short laundry list of the kind of things a cloud architect should know or be able to do to excel in this field.

  • Strong general background in enterprise computing: Ideally, this means one or more degrees in computer science, MIS, informatics or something similar, with a good working understanding of how enterprises use information technology for a wide range of purposes and applications.
  • Strong technical skills in enterprise computing: Cloud architects must understand the building blocks of IT. These include client systems and applications, networking, infrastructure, data centers, programming languages, web tools and technologies, databases and big data, and ERP. In fact, cloud architects are usually experts in one or more of these technology areas or disciplines. But their expertise is intended to create a vision of what is needed and how it might be put together, not necessarily to get involved in construction or maintenance work. In the literature, this is sometimes described as a "T-shaped skill profile." Broad but shallow skills apply to most technical areas (the vertical line in the T) with one or more sets of deep skills and knowledge in one or two technical areas (the top of the T).
  • Communication: Communicate clearly, directly and persuasively in writing and in person. Cloud architects must also be able to run meetings and manage all kinds of people, including C-level executives, managers, technical experts, and end users or customers.
  • Leadership: Cloud architects need strong, effective leadership skills because they must convince different groups and stakeholders to believe in a vision and a blueprint for how a cloud environment works within their organizations.
  • Asking the right questions: Arguably, the most important skill is a combination of analytical skill and insatiable curiosity. Cloud architects must ask the right questions and listen carefully to the answers (even if they think they know those answers in advance). Designing the right system or solution means understanding and formulating what users and stakeholders really want, in a way that provides proper performance, security and integrity.
  • Planning and organizing: Architects must possess strong planning and organizing skills because they must make and manage plans of action for projects that can take years to complete.
  • Strategy/business sense: Cloud architects must understand what is really important to a business or organization and focus on technologies and solutions most likely to provide competitive advantages or to improve productivity or profitability. Thus, they must understand business strategy and prioritize accordingly.

To become a cloud architect, one must add to the mix a deep knowledge and understanding of cloud computing and its roles and uses in the marketplace. This means digging into a host of important technologies that include virtualization, software-defined networking, network infrastructures, physical and virtual storage, data center computing, backup and recovery technologies, disaster recovery, and business continuity technologies. It also means working on the non-negotiable soft skills outlined above.

Cloud architect jobs generally go to those in the middle and later stages of their careers. People who aspire to and actually fill those positions usually have at least 8-10 years of prior on-the-job experience, often with a mix of jobs involving work as a strong technical contributor or technical expert, team lead, or first- or second-level manager. The job calls for a mix of hard technical and soft people and leadership skills that is hard to acquire and develop without some time in the workforce.

Ed Tittel

Ed is a 30-year-plus veteran of the computing industry, who has worked as a programmer, a technical manager, a classroom instructor, a network consultant and a technical evangelist for companies that include Burroughs, Schlumberger, Novell, IBM/Tivoli and NetQoS. He has written and blogged for numerous publications, including Tom's Hardware, and is the author of over 140 computing books with a special emphasis on information security, Web markup languages and development tools, and Windows operating systems.