Domain
Architecture & System Design
Skill Profile
Ports & Adapters, dependency inversion, testability, domain isolation
Roles
3
where this skill appears
Levels
5
structured growth path
Mandatory requirements
6
the other 6 optional
Architecture & System Design
Architecture Patterns
3/17/2026
Choose your current level and compare expectations. The items below show what to cover to advance to the next level.
The table shows how skill depth grows from Junior to Principal. Click a row to see details.
| Role | Required | Description |
|---|---|---|
| Technical Writer | Understands the fundamentals of Hexagonal Architecture. Applies basic practices in daily work. Follows recommendations from the team and documentation. |
| Role | Required | Description |
|---|---|---|
| Technical Lead | Applies Hexagonal Architecture when designing components. Understands trade-offs. Participates in architectural discussions. | |
| Technical Writer | Documents Hexagonal Architecture projects: describes ports, adapters, domain model, use cases. Creates architecture guides explaining design decisions. Helps developers understand boundaries between layers. |
| Role | Required | Description |
|---|---|---|
| Solutions Architect | Required | Designs bounded contexts and port/adapter boundaries using Hexagonal Architecture. Defines integration contracts between domain and infrastructure layers. Documents architectural decisions in ADRs with hexagonal rationale. |
| Technical Lead | Required | Enforces Hexagonal Architecture principles across team codebases. Reviews pull requests for proper port/adapter separation. Mentors developers on isolating domain logic from external dependencies. |
| Technical Writer | Creates comprehensive Hexagonal Architecture documentation: mapping business capabilities to ports, adapter implementation patterns, testing strategies. Ensures coherence between architecture docs and the codebase. |
| Role | Required | Description |
|---|---|---|
| Solutions Architect | Required | Defines product architectural strategy with Hexagonal Architecture. Establishes architecture guidelines. Conducts architecture reviews. |
| Technical Lead | Required | Defines the product's architectural strategy with Hexagonal Architecture. Establishes architecture guidelines. Conducts architecture reviews. |
| Technical Writer | Standardizes documentation of architectural patterns (Hexagonal, Clean, Onion) in the organization. Creates reference documentation and template projects. Coordinates consistency of approaches across teams. |
| Role | Required | Description |
|---|---|---|
| Solutions Architect | Required | Defines organization-wide reference architectures based on Hexagonal Architecture patterns. Establishes governance for port/adapter contracts across distributed systems. Drives adoption of domain-centric design at enterprise scale. |
| Technical Lead | Required | Shapes the organization's architectural strategy around Hexagonal Architecture and clean boundaries. Designs reference implementations for domain isolation patterns. Establishes architecture review processes ensuring hexagonal compliance. |
| Technical Writer | Shapes corporate software architecture documentation standards. Defines how architecture documentation supports system evolution and onboarding of new engineers. Ensures architecture knowledge preservation. |