Roles · Engineering Manager · Senior

What a Senior } should know

35 core skills, 50 in total. Expectations per skill, and what changes at the next level.

This page lists what a Senior } 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: Programming Fundamentals, API & Integration, Cloud & Infrastructure.

35core skills
15additional skills
10skill areas
30%at Advanced or Expert
Assess myself as Senior Full role matrix

Core skills for a Senior

Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.

Programming Fundamentals · 5

Evaluates algorithmic decisions in team's system designs. Understands computational complexity implications for scaling and cost. Facilitates discussions on algorithm selection trade-offs during architecture reviews. Ensures team competency in algorithms through hiring and mentoring practices.

Designs organizational code quality strategy: defines team-wide review standards, establishes quality metrics dashboards, balances technical debt reduction with feature delivery. Drives adoption of automated quality tools across teams. Makes data-driven decisions on refactoring investments based on defect density and velocity impact.

Data Structures Working

Evaluates data structure decisions in system designs and technical proposals. Understands performance implications of data structure choices for team's projects. Facilitates architectural discussions on data modeling trade-offs. Ensures team has proper knowledge of data structures through hiring and training decisions.

Design Patterns Working

Has deep expertise in evaluating design pattern usage across teams: reviews architectural decisions for pattern appropriateness at scale, identifies systemic over-engineering or under-abstraction patterns, designs training programs for pattern competency. Mentors leads on balancing pattern rigor with pragmatic delivery.

Evaluates OOP/SOLID application in team's architecture decisions. Ensures proper use of design patterns in system designs. Reviews architectural proposals for clean abstractions and dependency management. Facilitates team discussions on trade-offs between design pattern complexity and pragmatic simplicity.

API & Integration · 1

REST API Design Working

Designs API strategy for engineering teams: API governance frameworks, cross-team API contract standards, API versioning and deprecation policies. Defines API review processes and developer experience requirements. Mentors team leads on API architecture decision-making.

Cloud & Infrastructure · 4

AWS Working

Designs AWS infrastructure solutions for engineering organization workloads — multi-account strategies, shared services platforms, and centralized monitoring. Optimizes cost through organizational Savings Plans, reserved instances, and FinOps dashboards with team-level accountability. Implements security hardening with AWS Organizations SCPs, centralized logging, and compliance automation frameworks.

Docker Working

Designs Docker strategy for engineering teams: container adoption roadmaps, standardized base image governance, container CI/CD architecture. Implements best practices for team development environment consistency and container security compliance across projects.

Kubernetes Core Working

Designs Kubernetes infrastructure strategy for engineering organization workloads. Implements cost optimization through resource quotas, cluster autoscaling, and spot instance management. Applies security hardening best practices and establishes multi-team cluster governance policies.

Terraform Working

Designs infrastructure architecture with Terraform for multiple team products. Implements security hardening: least-privilege IAM, encryption at rest/transit, network segmentation. Optimizes cloud costs through right-sizing and reserved capacity planning via IaC. Establishes Terraform code review standards and CI/CD pipelines for infrastructure.

DevOps & CI/CD · 2

Feature Flags Working

Designs organization-wide feature flag governance including ownership policies, lifecycle management, and audit trails. Implements flag-driven release coordination across multiple teams and services. Establishes metrics-based automated rollback triggers and progressive delivery standards.

Designs CI/CD architecture for engineering organization: optimizes pipeline speed and reliability across teams, implements progressive delivery strategies, architects deployment automation for multi-service environments. Mentors leads on CI/CD best practices and platform engineering.

Security · 2

Designs security practices integration into team SDLC — implements threat modeling workshops, security champion programs, and automated security gate enforcement. Conducts organizational-level threat modeling for product architectures. Mentors team on security-first development culture and vulnerability management processes.

Designs secrets management architecture for multiple team services: centralized Vault cluster configuration, policy hierarchy for service-to-service authentication, and automated rotation for database/API credentials. Conducts threat modeling for credential flows. Implements monitoring for secret sprawl and expiration compliance. Mentors team on zero-trust credential patterns.

AI-Assisted Development · 1

GitHub Copilot Working

Designs GitHub Copilot adoption strategy for engineering organization: defines team-level policies and usage guidelines, measures productivity impact through development metrics, implements guardrails for code quality and IP compliance. Mentors leads on balancing AI-assisted development velocity with engineering standards.

Architecture & System Design · 9

Designs ADR governance framework for engineering organization: defines ADR templates, review workflows, and lifecycle management processes. Implements metrics for decision quality tracking and ensures ADRs inform capacity planning and technical roadmaps.

Designs architecture fitness functions for production systems: defines measurable architectural characteristics, implements automated compliance checks for modularity and coupling metrics, integrates fitness functions into deployment gates. Evaluates trade-offs between strictness and team velocity.

Designs capacity planning processes aligned with business growth projections. Evaluates infrastructure investment ROI and makes budget allocation decisions. Collaborates with architects on scalability requirements and non-functional constraints.

Designs DR processes aligned with business continuity requirements and compliance mandates. Evaluates DR investment ROI and negotiates RPO/RTO targets with stakeholders. Establishes regular DR testing cadence and post-mortem review practices.

Designs system architecture with high-load considerations, making capacity planning decisions documented as ADRs. Drives SLA management across teams, builds incident response playbooks for load spikes, and plans team scaling aligned with system growth projections.

Strategically manages microservices decomposition across multiple teams: aligns service boundaries with team cognitive load (Team Topologies), drives Conway's Law-aware organizational design. Manages cross-team dependencies during Strangler Fig migrations. Establishes platform team to provide service mesh, observability, and deployment infrastructure for decomposed services.

Designs system architecture for team products: defines service decomposition strategy, makes technology selection decisions, and ensures architecture supports business scalability goals. Creates ADRs and architecture documentation. Evaluates build-vs-buy decisions. Conducts architecture reviews with focus on non-functional requirements.

Designs team processes with technical debt management as a core practice. Makes decisions on sprint allocation for debt reduction and documents trade-offs via ADR. Evaluates velocity impact of tech debt and builds stakeholder communication plans for remediation efforts.

Designs Technology Radar process for engineering organization: defines assessment criteria, evaluation cadence, and cross-team technology alignment workshops. Implements radar-driven technology investment planning and tracks ROI of technology adoption decisions.

Observability & Monitoring · 4

Designs on-call management strategy for multiple team services: SLO-based alerting architecture, automated incident response workflows, and on-call sustainability practices (burnout prevention, fair rotation). Implements observability-driven incident detection. Conducts post-mortem reviews and drives systemic improvements. Defines MTTD/MTTR targets and tracks reliability metrics.

Designs observability strategy for engineering teams with Prometheus & Grafana: implements organizational monitoring standards, defines SLI/SLO frameworks aligned with business objectives, drives post-mortem culture and reliability improvements. Mentors leads on building observability-driven engineering practices.

SLI / SLO / SLA Working

Designs observability strategy for engineering organization services — implements distributed tracing across team boundaries, defines multi-service SLI/SLO frameworks, and establishes cross-team incident response processes. Conducts blameless post-mortems and drives reliability improvement initiatives.

Designs observability strategy for engineering organization: implements organizational logging and monitoring standards, defines SLI/SLO frameworks aligned with business objectives, drives post-mortem culture and incident learning processes. Mentors leads on building reliability practices within their teams.

Version Control & Collaboration · 4

Code Review Working

Designs code review culture for engineering teams: review process optimization, review quality metrics, feedback communication guidelines. Mentors team leads on building constructive review culture and reducing review cycle times while maintaining quality.

Designs documentation architecture for engineering teams: developer portals (Backstage, Docusaurus), automated doc pipelines, and documentation quality metrics. Ensures documentation coverage tracks with feature delivery. Establishes doc review processes and ownership models. Mentors team on effective technical writing.

Git Advanced Working

Designs Git workflows for engineering organizations: selects and implements branching strategies aligned with team structure and release cadence, configures branch protection and code review policies at scale, optimizes merge queue and CI integration. Mentors leads on balancing workflow rigor with developer velocity.

Designs InnerSource program for engineering organization: defines Trusted Committer roles, contribution workflows, and incentive structures. Implements metrics for measuring cross-team collaboration effectiveness and knowledge transfer impact.

Documentation · 3

Designs architecture documentation standards for multiple teams using C4 and arc42 as core frameworks. Establishes ADR workflows integrated into code review and pull request processes. Mentors team leads on effective documentation practices that balance thoroughness with developer productivity. Drives adoption of diagram-as-code tooling (Structurizr, Mermaid) to keep docs versioned alongside source code.

Designs comprehensive process flow systems and roadmap visualizations using Mermaid, PlantUML, or D2. Creates standardized org chart and communication templates. Mentors the team on effective diagramming for stakeholder presentations and cross-team alignment.

Designs runbook systems for cross-team engineering operations: multi-service incident coordination, disaster recovery orchestration, capacity planning response procedures. Optimizes runbook adoption through integration with CI/CD pipelines and automated validation of playbook steps.

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 Lead

50 skills get a higher expectation or become core when moving from Senior to Lead. The biggest jumps first.

See the Lead page →
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.
Start a team trial (14 days free) Send to my manager

} in the open competency matrix: 50 skills across 5 levels. The matrix is free for individuals and stays free.