When selecting a cloud architect, proven experience with comparable architectural challenges is crucial. You should ensure that previous projects match your situation in terms of size, complexity, level of regulation, and technology stack, and that the resume details clear, verifiable results such as stable platforms, reduced downtime, or improved deployment speed.
Equally important is the depth of expertise in the relevant hyperscalers. For AWS, Azure, or GCP, certifications should be just a starting point; what matters most are concrete architectures, reference implementations, landing zone designs, network setups, and clear security concepts that the cloud architect can explain and justify.
Strong communication skills and stakeholder management should not be underestimated. A good cloud architect facilitates decisions among development, operations, security, data protection, and functional areas; explains technical risks in an understandable way; and still makes clear decisions. Warning signs include, for example, arguments based purely on tools with no connection to business goals, or a lack of willingness to work pragmatically with existing teams.