One of the first things you notice when you move from developer to architect is that the skills that made you successful as a developer are necessary but no longer sufficient. Technical depth still matters — probably more than you expected — but it is now only one dimension of the job.
This post covers the full skill spectrum of the architect role, how to think about gaps versus strengths, and what to focus on first. There is also a free self-assessment tool at the end that lets you rate yourself across 30 skills in six categories.
The six skill dimensions
1. Technical depth
Architects need to understand distributed systems, data architecture, API design, security, observability, and cloud infrastructure at a level that lets them make credible trade-off decisions and earn the trust of engineering teams. You do not need to be the best coder in the room, but you need to understand the problems deeply enough to know when a proposed solution is naive.
The engineers you work with will test your technical judgment constantly — not maliciously, but because they need to know whether your guidance is worth following. Technical credibility is the foundation everything else is built on.
2. Design thinking
The ability to decompose complex systems into understandable parts, apply architectural patterns appropriately, and think about quality attributes systematically. This includes knowing when not to apply a pattern — microservices make sense for some teams and systems; they create complexity without benefit for others.
Design thinking also covers diagramming: communicating structure to different audiences at the right level of abstraction. A C4 context diagram for a non-technical stakeholder is different from a sequence diagram for a development team.
3. Decision-making
Architects make consequential decisions under uncertainty with incomplete information. The skill is not making perfect decisions — it is making good-enough decisions at the right time, documenting them properly, and knowing which decisions need stakeholder buy-in versus which can be made and communicated.
This includes writing Architecture Decision Records (ADRs), structuring trade-off analyses, and knowing when to decide, when to defer, and when to escalate.
4. Communication
The most underestimated skill on this list. Architects write RFCs, proposals, and design docs. They present to executives who need to understand cost and risk without getting lost in implementation details. They run architecture reviews. They write documentation that stands alone without a meeting to explain it.
Poor communicators rarely last long in architect roles, regardless of how technically capable they are. The job requires translating between audiences constantly.
5. Governance
Running architecture reviews, creating standards and guidelines teams actually follow, managing technical debt, and building reference architectures. Governance is the organisational infrastructure of architecture — it is how architectural thinking scales beyond a single person.
Many architects find governance uncomfortable because it requires saying no, pointing out problems, and holding a line on quality standards. This is also where a lot of the real leverage is.
6. Leadership
Influencing without authority, mentoring engineers, managing stakeholders, and navigating organisational politics without compromising technical integrity. Architects typically have responsibility without direct management authority, which means leadership style matters more than title.
How to use these dimensions
Most engineers entering the architect role are strong in technical depth and weak in communication and governance. That pattern is so common it is almost a cliché. The useful exercise is to rate yourself honestly, identify your two or three biggest gaps, and make those the focus of deliberate development over the next 6–12 months.
The goal is not to be uniformly excellent across all six dimensions. It is to be strong enough across all of them that no single weakness becomes a consistent liability.
Strengths are worth identifying too — not to rest on them, but because they are where your initial credibility and influence will come from. If you are known for clear written communication, use that. If you are the person who understands the data layer better than anyone, lead with that.
Free Skills Self-Assessment
Rate yourself across 30 skills in six categories and see a personalised breakdown of where to focus.