System Architecture Designer Skill Framework: Identify What You’re Missing

Overview

The article explains that the knowledge tested in certification exams covers only the "visible" part of a system architect’s competence, while real‑world work demands a broader set of "invisible" abilities.

Iceberg Model

┌─────────────────┐
          │   Explicit Ability      │ ← Knowledge, skills (exam‑tested)
          │   (visible)             │
          └─────────────────┘
          │                         │
          │   Implicit Ability      │ ← Integrated abilities, personal traits
          │   (invisible)           │
          └─────────────────┘

This model visualises the gap between exam content and the full skill set required on the job.

Hard Skills (Exam‑Assessed)

The exam focuses on three areas with their weight and importance:

Computer Systems – 20% (★★★★★)

Software Engineering – 20% (★★★★★)

Database Design – 15% (★★★★☆)

System Architecture – 20% (★★★★★)

Other Knowledge – 25% (★★★☆☆)

These constitute the "explicit" knowledge that can be measured by tests.

Soft Skills (Not Exam‑Assessed)

Communication (★★★★★)

Architects act as bridges between leaders, developers, product owners, and customers. Effective communication includes reporting designs, explaining decisions, understanding business needs, and presenting technical solutions.

Improvement methods: more reporting, storytelling practice, and applying the Pyramid Principle.

Documentation (★★★★☆)

Architects must produce various documents such as architecture design specs, technical solution docs, project plans, and API specifications.

Improvement methods: write more documents, study exemplary docs, and learn tools like Markdown and PlantUML.

Presentation (★★★★☆)

Frequent speaking occasions include architecture review meetings, tech sharing sessions, and training talks.

Improvement methods: give more talks, practice PPT creation, and learn presentation techniques.

Project Management (★★★★☆)

Key tasks are effort estimation, resource coordination, and schedule control.

Improvement methods: study PMP, participate in projects, and use project‑management tools.

Comprehensive Abilities

Learning Ability (★★★★★)

Because the IT field evolves rapidly, continuous learning is essential. The article stresses staying curious, building a knowledge system, and mastering new technologies quickly.

Analysis Ability (★★★★★)

Core analyses include business‑requirement analysis, technical feasibility, risk assessment, and performance evaluation.

Improvement methods: conduct more case studies, learn thinking models, and develop logical reasoning.

Decision‑Making Ability (★★★★☆)

Architects regularly decide on technology selection, architecture solutions, and resource allocation.

Improvement methods: accumulate experience, study decision‑making methods, and take responsibility for outcomes.

Innovation Ability (★★★☆☆)

Innovation involves applying new technologies, creating novel architecture patterns, and devising original solutions.

Improvement methods: follow industry trends, broaden technical horizons, and dare to try new ideas.

Personal Traits

Responsibility (★★★★★) – owning decisions and risks.

Big‑Picture View (★★★★★) – considering current needs, future expansion, and technical debt.

Stress Resistance (★★★★☆) – handling tight schedules, technical challenges, and multi‑party coordination.

Curiosity (★★★☆☆) – exploring new technologies and continuously growing.

Self‑Assessment and Gap Analysis

The article provides a self‑rating table (1–5) for each ability, the target level (5), and the gap. Example entries: Computer Foundations 4→5 (gap 1), Communication 2→5 (gap 3), Decision‑Making 3→5 (gap 2), etc.

Improvement Plan

Short‑Term (1‑3 months)

Fill knowledge gaps.

Enhance communication techniques.

Practice document writing.

Mid‑Term (3‑6 months)

Participate in projects to gain hands‑on experience.

Accumulate architecture practice.

Boost decision‑making skills.

Long‑Term (6‑12 months)

Become an independent architect.

Mentor team members.

Contribute reusable architecture assets.

Advice for Different Career Stages

Exam Preparation: Master theory, understand concepts deeply, and develop good study habits.

Early Career: Join projects, learn from senior colleagues, and take on technical responsibilities.

Growth Phase: Design small architectures independently, improve communication and documentation, and build a personal knowledge base.

Mature Phase: Lead large‑scale designs, coach the team, and create reusable architecture patterns.

Conclusion

The framework distinguishes hard (exam‑tested) and soft (on‑the‑job) competencies, emphasizes continuous learning, and provides concrete self‑assessment and development steps to help architects progress from certification to real‑world expertise.