Roles · Engineering Manager · Junior
What a Junior } should know
0 core skills, 15 in total. Expectations per skill, and what changes at the next level.
This page lists what a Junior } 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 Junior
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 / ClaudeCursor IDEGraphQL DesignIntegration TestingMultithreadingNetwork FundamentalsOpenTelemetryPostgreSQLPrompt Engineering for CodeRedisSecure Coding PracticesType Safety & Type SystemsUnit Testing
What changes at Mid-level
50 skills get a higher expectation or become core when moving from Junior to Mid-level. The biggest jumps first.
- Algorithms & Complexity: — → Awareness
- API Documentation: Awareness → Working
- Architecture Decision Records (ADR): — → Awareness
- Architecture Documentation: C4, arc42: — → Awareness
- Architecture Fitness Functions: — → Awareness
- Async Programming: Awareness → Working
- AWS: — → Awareness
- Capacity Planning: — → Awareness
- ChatGPT / Claude: Awareness → Working
- Code Quality & Refactoring: — → Awareness
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.