Roles · Solutions Architect · Mid-level
What a Mid-level } should know
0 core skills, 15 in total. Expectations per skill, and what changes at the next level.
This page lists what a Mid-level } is expected to know and do, skill by skill. Core skills are the ones a manager and peers assess in a review cycle; the rest count only in self-assessment. Main areas: .
0core skills
15additional skills
0skill areas
0%at Advanced or Expert
Core skills for a Mid-level
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
API DocumentationAsync ProgrammingChatGPT / ClaudeDatabase IndexingE2E TestingGitHub Actions / GitLab CIIntegration TestingJWT / OAuth2 / OIDCMultithreadingOWASP & Application SecurityPrompt Engineering for CodeQuery OptimizationSecure Coding PracticesType Safety & Type SystemsUnit Testing
What changes at Senior
62 skills get a higher expectation or become core when moving from Mid-level to Senior. The biggest jumps first.
- Network Fundamentals: — → Advanced · becomes core
- Algorithms & Complexity: — → Working · becomes core
- Apache Kafka: — → Working · becomes core
- API Gateway: — → Working · becomes core
- Architecture Decision Records (ADR): — → Working · becomes core
- Architecture Documentation: C4, arc42: — → Working · becomes core
- AWS: — → Working · becomes core
- Capacity Planning: — → Working · becomes core
- Clean Architecture: — → Working · becomes core
- Cloud Security: — → Working · becomes core
Run this with your whole team
Self-assessment plus manager and peer reviews against the same matrix, gap analysis and next-level readiness for every engineer. Team Pro is free for 14 days; individual tools stay free forever.
} in the open competency matrix: 15 skills across 5 levels. The matrix is free for individuals and stays free.