What Makes Someone a Good Cloud Architect?

The Technical Foundation: What You Must Know

Deep Platform Expertise

You need deep, hands-on experience with at least one major cloud provider (AWS, Azure, GCP). You don't need to be the deepest expert in every service—you need to know enough to make the right choice, understand the tradeoffs, and defend your decisions.

What good looks like:

• You know when to use EC2 vs. Lambda vs. ECS vs. EKS without consulting a decision matrix
• You understand the limitations and failure modes of every service you recommend
• You've actually used the services you design with—you've deployed them, monitored them, and debugged them when they failed

Networking and Security

This is where most architects get exposed. You need to understand VPCs, subnets, routing, IAM, encryption, firewalls, VPNs, and compliance. Security isn't an afterthought—it's embedded in every design decision you make.

What good looks like:

• You design for defense-in-depth without making systems unusable
• You can explain security boundaries in plain language to non-technical stakeholders
• You understand that IAM is the most important thing to get right in any cloud architecture

Infrastructure as Code

Terraform is the industry standard for provisioning cloud infrastructure. You need to be comfortable writing IaC—it's how modern teams deploy and manage cloud resources at scale.

What good looks like:

• You write Terraform modules that are reusable, documented, and tested
• You understand the difference between good IaC and "working" IaC
• You can review Terraform changes and spot potential issues before they're merged

System Design

You need to understand how to design systems that scale, handle failure, and remain maintainable. This means knowing distributed systems patterns, load balancing, caching, databases (both SQL and NoSQL), and how to think about performance at scale.

What good looks like:

• You can design a system that fails gracefully and recovers quickly
• You think about the "blast radius" of failures
• You design with observability in mind—you can monitor, debug, and improve what you build

Cost Awareness

Cost optimization is an engineering capability, not a quarterly budget ritual. Good architects design for cost from day one.

What good looks like:

• You can estimate the monthly cost of a design before it's built
• You understand where costs accumulate and how to optimize them
• You can explain cost tradeoffs to business stakeholders in terms they understand

The Soft Skills: The Real Differentiator

Technical skills get you noticed. Soft skills get you hired. This is the foundation for success in this role.

Communication

A good architect is a storyteller who can translate technical complexity into business language. You must be able to explain complex designs in plain language to non-technical stakeholders.

What good looks like:

• You adjust your communication style to match your audience's technical level
• You can explain why you chose a particular design in terms your audience cares about
• You listen as much as you talk—you understand the business problem before proposing a technical solution

Strategic Thinking

Good architects align designs with long-term business goals. Every architecture must balance security, resilience, performance, and cost. Which pillar takes priority depends on the situation. A good architect balances these concerns for every solution.

What good looks like:

• You think about the 3-5 year roadmap, not just the current sprint
• You understand the business context and constraints that drive architectural decisions
• You know when to build a custom solution and when to use a managed service

Stakeholder Management

You're the bridge between business needs and technical implementation. This means working closely with developers, security teams, and business leaders.

What good looks like:

• You can manage expectations and say "no" when necessary
• You help stakeholders understand tradeoffs without being condescending
• You build trust by delivering on your commitments

Leadership and Mentoring

Good architects help engineers grow and drive team quality. You're not just designing systems—you're shaping how teams build them.

What good looks like:

• You mentor engineers and help them become better architects
• You create guardrails, not gates—you empower teams to make good decisions
• You share your knowledge freely and build a culture of learning

What Good Architects Do Differently

They Design for Change, Not Just for Now

The best architects design systems that can evolve. They anticipate that requirements will change, traffic patterns will shift, and the cloud itself will evolve. They build systems that can adapt.

What good looks like:

• You minimize vendor lock-in where it hurts and embrace it where it helps
• You use patterns that allow for incremental migration and evolution
• You build abstractions that hide complexity without hiding intent

They Think in Tradeoffs, Not Absolutes

There is no "right" architecture—only architectures with different tradeoffs. Good architects are comfortable with ambiguity and can articulate the tradeoffs of every design decision.

What good looks like:

• You can articulate the tradeoffs of any design decision in business terms
• You know when to trade off perfection for speed
• You can pivot when circumstances change

They Write Architecture Decisions Down

Good architects maintain architecture decision records, runbooks, and documentation that others can understand and use. If it's not documented, it's not a decision—it's just a thought.

What good looks like:

• Your documentation is clear enough that others can maintain it without you
• You document not just what was decided, but why
• You treat documentation as part of the work, not an afterthought

They Stay Close to Implementation

The best architectures are usually built by people who still deploy to production—they understand the "why" because they're still intimate with the "how."

What good looks like:

• You write Terraform, debug incidents, and review pull requests
• You understand the pain points of the people implementing your designs
• You can prototype and validate your designs before committing to them

They Embrace AI Tools

Good architects use AI to accelerate their workflow without losing their critical thinking. They recognize that AI is the biggest shift in cloud architecture since cloud computing itself.

What good looks like:

• You use AI to generate architecture diagrams from descriptions, document decisions, and review designs
• You understand the limitations of AI tools—you review and validate their output
• You use AI to offload mechanical work so you can focus on high-value thinking

What Good Architects Avoid

• Designing in a Vacuum. The best architecture is useless if it doesn't meet business needs. Constant collaboration with stakeholders is essential.
• Chasing Certifications Without Experience. Certifications validate knowledge; experience builds judgment. The best architects have both.
• Letting Diagrams Stagnate. Architecture diagrams are living documents. If they're not updated, they're worthless.
• Over-Engineering. Good architects know when to build a simple solution and when to add complexity.
• Saying "Yes" to Everything. Good architects know when to push back on bad ideas. They manage expectations and help stakeholders understand tradeoffs.

How to Assess Your Own Growth

External Resources

• AWS Well-Architected Framework — foundational guidance for making key design decisions
• Google Cloud Architecture Framework — Google's framework for building reliable and cost-effective systems
• Azure Well-Architected Framework — Microsoft's framework for optimizing Azure workloads
• AWS Certified Solutions Architect — official certification page
• Google Cloud Professional Cloud Architect — official certification page

Final Thoughts

Being a good cloud architect is about making sound decisions under uncertainty. You need deep technical knowledge, but you also need the judgment to use that knowledge appropriately. You need to think strategically, communicate clearly, and build systems that enable your team to succeed.

A good architect doesn't just create beautiful diagrams. They create frameworks and guardrails that empower their engineering teams to build safely, quickly, and cost-effectively. They bridge the gap between business needs and technical reality. They think in tradeoffs, build for change, and never stop learning.

If you're on this path, you're not just building systems. You're shaping the future of how your organization uses technology. That's what makes this career so rewarding.