Defines algorithmic competency standards for engineering teams: performance benchmarking practices, algorithm selection review processes, technical interview rubrics for algorithmic skills. Facilitates cross-team knowledge sharing on algorithmic optimization.
Roles · Engineering Manager · Lead
What a Lead } should know
35 core skills, 50 in total. Expectations per skill, and what changes at the next level.
This page lists what a Lead } 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.
Core skills for a Lead
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Programming Fundamentals · 5
Defines code quality standards across engineering organization: review process design, quality metric targets, refactoring investment planning. Conducts organizational reviews of team practices and tool adoption. Establishes quality culture through hiring standards and onboarding programs.
Defines data structure standards at team management level: evaluates data model proposals in technical designs, ensures team follows proper data structure practices, includes data structure competency in hiring criteria. Facilitates data architecture decisions across team projects.
Defines design pattern standards at the organizational level: establishes architectural review processes for pattern governance, creates guidelines balancing pattern consistency with team autonomy, conducts assessments of pattern competency across engineering teams.
Defines OOP/SOLID competency standards for engineering teams: design pattern review processes, architectural fitness function criteria, technical interview rubrics for OOP skills. Facilitates cross-team knowledge sharing on design principles and refactoring practices.
API & Integration · 1
Defines API strategy at product level for engineering teams: API governance processes, cross-team API contract standards, API developer experience requirements. Conducts API architecture reviews and establishes API design review processes for the team.
Cloud & Infrastructure · 4
Defines AWS infrastructure strategy for engineering organization workloads spanning multiple teams and environments. Establishes IaC standards for multi-account governance and shared service platforms. Conducts architecture reviews of team infrastructure patterns and drives FinOps accountability across engineering departments.
Defines Docker strategy for engineering organization: container adoption standards, base image governance, container CI/CD pipeline architecture. Conducts architecture reviews for containerized service deployments and optimizes FinOps for container infrastructure across teams.
Defines Kubernetes infrastructure strategy for engineering organization workloads. Establishes IaC and cluster governance standards across teams. Conducts architecture reviews of deployment patterns and optimizes FinOps practices for organizational cloud spending on Kubernetes.
Defines infrastructure strategy and IaC standards across engineering organization. Establishes Terraform module registry, versioning policies, and contribution guidelines. Drives FinOps practices: cost allocation tagging, budget alerts, and resource optimization through IaC. Conducts architecture reviews for infrastructure changes across teams.
DevOps & CI/CD · 2
Defines enterprise feature flag strategy aligned with release management and product delivery goals. Establishes flag hygiene standards with automated stale flag detection and cleanup enforcement. Drives adoption of progressive delivery culture across engineering teams and measures its impact on deployment frequency.
Defines DevOps strategy with GitHub Actions at organizational level: establishes CI/CD standards and platform engineering approaches, implements internal developer platform capabilities, drives engineering excellence through deployment automation and reliability.
Security · 2
Defines security strategy for engineering organization development practices. Establishes security policies for SDLC integration, security champion programs, and vulnerability remediation timelines. Coordinates incident response processes and trains engineering teams on security-first development culture.
Defines secrets management standards for engineering teams. Establishes policies for credential lifecycle management, rotation schedules, and access review cadences. Drives adoption of centralized Vault infrastructure across services. Coordinates incident response for credential compromise scenarios. Creates training programs on secure secrets handling.
AI-Assisted Development · 1
Defines GitHub Copilot strategy at the organizational level: establishes enterprise-wide adoption policies and usage guidelines, designs ROI measurement frameworks for AI-assisted development, drives cultural change for responsible AI tool adoption across engineering teams.
Architecture & System Design · 9
Defines product architectural strategy with Architecture Decision Records. Shapes architecture guidelines. Conducts architecture reviews.
Defines fitness function strategy for engineering organization: establishes architectural governance through automated fitness functions, designs fitness function frameworks covering performance budgets, dependency rules, and security compliance. Coordinates cross-team architectural quality standards.
Defines product architectural strategy with Capacity Planning. Shapes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Disaster Recovery Design. Shapes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with High Load Architecture. Shapes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Microservices Decomposition. Shapes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with System Design Fundamentals. Shapes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Technical Debt Management. Shapes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Technology Radar. Shapes architecture guidelines. Conducts architecture reviews.
Observability & Monitoring · 4
Defines on-call management strategy for product organization: SLO-based approach to incident management, on-call sustainability metrics, and cross-team incident coordination processes. Establishes post-mortem culture and tracks systemic improvements. Optimizes MTTD/MTTR across services.
Defines observability strategy at the organizational level with Prometheus & Grafana: establishes SLO frameworks aligned with business metrics, coordinates cross-team incident management, optimizes MTTD/MTTR through organizational reliability programs.
Defines product observability strategy across engineering teams — establishes SLO-based reliability culture, coordinates cross-team incident management processes, and optimizes MTTD/MTTR metrics through tooling and process improvements. Drives error budget policy adoption and blameless post-mortem practices.
Defines observability strategy at the organizational level: establishes SLO frameworks aligned with business metrics, coordinates cross-team incident management practices, optimizes MTTD/MTTR through organizational reliability programs and on-call processes.
Version Control & Collaboration · 4
Defines code review strategy for engineering organization: review process standards, review quality metrics and KPIs, cross-team review practices. Establishes review culture focused on constructive feedback and continuous improvement.
Defines documentation-as-code strategy for the engineering organization. Establishes documentation standards, review processes, and quality metrics across teams. Drives developer portal adoption for centralized documentation discovery. Ensures documentation practices support compliance and audit requirements.
Defines Git strategy at the organizational level: selects branching models aligned with team topology and delivery cadence, establishes branch protection and review policies at scale, drives adoption of Git best practices across multiple engineering teams.
Defines InnerSource strategy at product/department level: establishes governance models, community management practices, and success measurement frameworks. Coordinates InnerSource adoption across multiple teams with stakeholder alignment.
Documentation · 3
Defines architecture documentation strategy at the team and product level. Establishes mandatory C4 and arc42 documentation standards for all new services and major refactors. Conducts architecture reviews ensuring documentation quality covers context, containers, components, and deployment views. Integrates ADR practices into the development lifecycle with clear ownership and review cadences across teams.
Defines diagramming strategy for team communication, process documentation, and roadmap visualization. Establishes standards for org chart maintenance, workflow diagrams, and stakeholder reporting visuals. Conducts reviews of diagram quality across the product area.
Defines runbook strategy at the product level: establishes operational readiness standards requiring runbooks for all production services, creates runbook maturity models, drives cultural adoption of documented operational procedures across engineering teams.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
What changes at Principal
35 skills get a higher expectation or become core when moving from Lead to Principal. The biggest jumps first.
- Algorithms & Complexity: Advanced → Expert
- Architecture Decision Records (ADR): Advanced → Expert
- Architecture Documentation: C4, arc42: Advanced → Expert
- Architecture Fitness Functions: Advanced → Expert
- AWS: Advanced → Expert
- Capacity Planning: Advanced → Expert
- Code Quality & Refactoring: Advanced → Expert
- Code Review: Advanced → Expert
- Data Structures: Advanced → Expert
- Design Patterns: Advanced → Expert
} in the open competency matrix: 50 skills across 5 levels. The matrix is free for individuals and stays free.