Curated for this specific career level.
Level path
Software Architecture Practitioner
Software Architect
Own features and services with solid implementation judgment across neighboring layers.
Concepts explicitly listed in this level.
Concepts span multiple tracks and layers.
Job description signalsTypical responsibilities↓
- Define software structures, boundaries, quality attributes, and evolutionary architecture decisions.
- Guide teams through architecture trade-offs, design reviews, documentation, and technical governance.
- Connect implementation constraints with reliability, scalability, security, and long-term maintainability.
- Own features end to end from design through implementation, testing, release, and support.
- Make local technical tradeoffs and explain them clearly to teammates.
- Improve reliability, maintainability, and observability of the systems you touch.
- Collaborate with product, design, QA, operations, and adjacent engineering teams.
Track / layer masteryConcept coverage by layer↓
Software
6 concepts
Software
153 concepts
Product
23 concepts
Management
19 concepts
Operations
17 concepts
Data
3 concepts
Theory
3 concepts
Learning scopeConcepts by learning area↓
Specific to this level
Concepts introduced by this level
Level concepts
Application Architecture
Design maintainable application boundaries and interaction models.
Level concepts
Integration Architecture
Design interfaces and asynchronous interactions across services.
Cumulative level expectation
All concepts expected at this level
Inherited path
Coding Foundations
Developers begin by learning to translate requirements into working, readable code.
Inherited path
Developer Tooling
Daily development depends on version control, language tooling, static checks, and repeatable local workflows.
Inherited path
Testing & Debugging
A developer owns not only writing code, but proving that it behaves as intended.
Inherited path
Employment Basics
Technical candidates benefit from understanding who employs them, how they are paid, and which terms govern the working relationship.
Inherited path
Programming Foundations
Learn the basic building blocks used to express behavior in code.
Inherited path
Software Design
Structure code so it remains readable, testable, and maintainable as it grows.
Inherited path
Data & Persistence
Understand how applications store, retrieve, and protect durable state.
Inherited path
Architecture & Systems
Design systems that handle growth, latency, failure, and multiple communicating components.
Inherited path
Production Awareness
Know how software is built, deployed, observed, and recovered in production.
Inherited path
Web & APIs
Understand how clients and servers communicate through stable service interfaces.
Inherited path
Databases
Store, query, and reason about persistent data correctly and efficiently.
Inherited path
Backend Design
Organize service code and boundaries so backend systems can evolve safely.
Inherited path
System Design
Design backend systems that handle scale, latency, state, and failure.
Inherited path
Production Backend
Understand how backend services are packaged, deployed, observed, and operated.
Inherited path
Architecture Foundations
Understand architecture intent, quality attributes, and foundational structural patterns.
Inherited path
Architecture Communication
Document and communicate design decisions with clear context and trade-offs.
Inherited path
Application Design
Mid-level developers own complete features and make local design choices inside an established architecture.
Inherited path
Runtime & Data
Feature ownership requires practical knowledge of runtimes, memory management, and relational persistence.
Inherited path
Delivery & Collaboration
Professional development includes the complete implementation loop, not only editing source files.
Inherited path
Service Development
Build the capabilities needed for this area.
Path concepts
Application Architecture
Design maintainable application boundaries and interaction models.
Path concepts
Integration Architecture
Design interfaces and asynchronous interactions across services.