# Skills Self-Assessment for Aspiring Architects

**Companion resource for Developer to Architect by Shameel Ahmed**
**Appendix C | devtoarch.com/resources**

---

Rate yourself honestly on each skill. This is for your own use.

**1** = I am not familiar with this  
**2** = I have read about it but have little hands-on experience  
**3** = I have applied this in a real project  
**4** = I am confident and have applied this in multiple contexts  
**5** = I could teach this and have led others in applying it  

**Date:** ___________________________
**Revisit date:** ___________________________ (recommended: every 6 months)

---

## Technical Depth

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Distributed systems fundamentals (CAP, consistency models, failure modes) | | |
| Data architecture and storage selection | | |
| API design and versioning | | |
| Scalability and performance design | | |
| Security architecture and threat modeling | | |
| Cloud architecture and managed services | | |
| Observability: logs, metrics, traces, SLOs | | |
| Containerization and orchestration | | |
| Event-driven architecture | | |
| CI/CD pipeline design | | |
| AI/ML integration architecture | | |
| Legacy modernization strategies | | |

---

## Architectural Decision-Making

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Framing problems before jumping to solutions | | |
| Evaluating trade-offs between quality attributes | | |
| Writing Architectural Decision Records (ADRs) | | |
| Making decisions under uncertainty and incomplete information | | |
| Recognizing when to reopen a past decision | | |
| Pattern selection and pattern misuse avoidance | | |

---

## Communication

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Drawing clear architectural diagrams (C4 or equivalent) | | |
| Writing technical proposals for engineering audiences | | |
| Presenting architecture to non-technical stakeholders | | |
| Facilitating technical discussions and design sessions | | |
| Writing clear ADRs and RFCs that non-authors can act on | | |

---

## Governance and Organization

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Architecture review facilitation | | |
| Establishing lightweight governance processes | | |
| Defining and maintaining reference architectures | | |
| Building a technology radar | | |

---

## Leadership and Influence

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Influencing engineering decisions without direct authority | | |
| Handling technical disagreement productively | | |
| Identifying and developing architectural thinking in others | | |
| Saying no effectively, with reasons | | |

---

## Stakeholder Management

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Stakeholder identification and mapping | | |
| Managing competing priorities between stakeholders | | |
| Navigating organizational politics | | |
| Building coalitions for architectural changes | | |

---

## Career and Visibility

| Skill | Rating (1-5) | Notes / Evidence |
|-------|-------------|-----------------|
| Maintaining a visible technical portfolio | | |
| Contributing to external technical communities | | |
| Mentoring other engineers | | |
| Articulating architectural value in business terms | | |

---

## Summary

**Highest-rated area:** ___________________________

**Lowest-rated area:** ___________________________

**Top 3 skills to develop in the next 6 months:**
1.
2.
3.

**How I will develop them:**
1.
2.
3.

---

*From Developer to Architect by Shameel Ahmed | devtoarch.com | leanpub.com/devtoarch*
*E-Book ISBN: 978-93-6068-417-4*