Defines algorithmic standards at solution architecture level: distributed algorithm selection criteria, caching strategy evaluation frameworks, data partitioning algorithm guidelines. Conducts cross-team reviews of algorithmic decisions with system-wide performance implications.
Roles · Solutions Architect · Lead
What a Lead } should know
45 core skills, 61 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, Backend Development, Database Management.
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 at solution architecture level: reference implementation quality criteria, proof-of-concept code guidelines, architectural fitness function enforcement. Conducts cross-team reviews for design-implementation alignment. Establishes quality gates for architectural compliance.
Defines data structure standards at solution architecture level: domain model design conventions, event sourcing schema patterns, cross-system data model alignment. Conducts architectural reviews of data structure decisions across teams. Establishes guidelines for data model interoperability and evolution.
Defines design pattern standards across multi-team architectures: establishes cross-service pattern governance and architectural review practices, creates guidelines for integration and resilience pattern selection, conducts architecture forums on strategic pattern application for distributed systems.
Defines OOP/SOLID standards at solution architecture level: domain model abstraction guidelines, cross-service interface contract principles, bounded context class design patterns. Conducts cross-team reviews of architectural decisions with system-wide OOP implications.
Backend Development · 2
Defines Kafka strategy for enterprise: event-driven architecture standards, schema governance with Schema Registry, and multi-cluster management policies. Evaluates Kafka vs alternatives (Pulsar, Redpanda, cloud-native messaging). Conducts architecture reviews for event-driven systems across teams.
Defines Redis caching strategy across the product ecosystem — establishes standards for multi-tier caching, distributed lock patterns, and cache consistency across microservices. Conducts design reviews of caching architectures and defines technical roadmap for enterprise caching infrastructure evolution.
Database Management · 1
Defines PostgreSQL data strategy for multi-service architectures: establishes standards for database technology selection per service, designs cross-service data consistency patterns, drives adoption of PostgreSQL architectural best practices across platform and product teams.
API & Integration · 4
Defines API gateway strategy across products: establishes gateway topology standards, designs multi-tier gateway architectures for microservices, implements API versioning and deprecation policies. Conducts gateway architecture reviews and coordinates cross-team API governance.
Defines enterprise GraphQL API strategy spanning business domains and organizational boundaries. Establishes federated schema governance, API gateway standards, and cross-team schema composition policies. Conducts architectural reviews of GraphQL implementations and coordinates API platform evolution across engineering teams.
Defines enterprise gRPC API strategy spanning product domains — establishes organizational proto governance, schema registry management, and cross-team backward compatibility policies. Conducts API design reviews and coordinates unified gRPC standards across engineering teams.
Defines API strategy at enterprise architecture level: cross-team API governance framework, enterprise API gateway standards, API lifecycle management policies. Conducts cross-team API architecture reviews and establishes enterprise API design principles.
Cloud & Infrastructure · 4
Defines enterprise AWS infrastructure strategy spanning multi-account architectures and cross-region deployments. Establishes IaC standards for organizational landing zones, shared services, and compliance frameworks. Conducts architecture reviews of cross-team infrastructure patterns and drives FinOps at organizational scale.
Defines Docker infrastructure strategy at solution architecture level: enterprise container platform standards, multi-environment deployment governance, container security compliance frameworks. Conducts cross-team architecture reviews and optimizes FinOps for container infrastructure.
Defines enterprise Kubernetes platform strategy spanning multiple clusters and cloud providers. Establishes IaC standards for multi-tenant cluster management, federation, and GitOps workflows. Conducts architecture reviews of cross-team deployment patterns and drives FinOps optimization across the Kubernetes estate.
Defines infrastructure strategy for client engagements and internal platform. Establishes IaC standards and module governance across the organization. Evaluates and drives adoption of Terraform alternatives where appropriate (Pulumi, Crossplane, CDK). Designs multi-cloud landing zones and account vending machines. Conducts architecture reviews for critical infrastructure changes.
Security · 2
Defines secure cloud architecture strategy based on zero-trust principles and the Well-Architected Framework security pillar. Establishes security policies for multi-cloud deployments. Coordinates incident response at the infrastructure level and trains engineering teams on secure cloud design and compliance requirements.
Defines enterprise secrets management architecture strategy. Evaluates Vault vs cloud-native solutions (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager) for different use cases. Designs multi-tenant secrets infrastructure with isolation guarantees. Establishes standards for secrets management in client-facing architectures.
AI-Assisted Development · 1
Defines GitHub Copilot strategy for multi-team architectures: establishes standards for AI-assisted development aligned with architecture governance, designs consistency validation for AI-generated code across services, drives Copilot adoption with focus on architectural pattern adherence.
Architecture & System Design · 17
Defines product architectural strategy with Architecture Decision Records. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Capacity Planning. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Clean Architecture across enterprise systems. Establishes guidelines for bounded contexts, technology-agnostic domain modeling, and integration patterns. Conducts architecture reviews at organizational level.
Defines product architectural strategy with CQRS. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with DDD Strategic Patterns. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with DDD Tactical Patterns. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Disaster Recovery Design. Establishes architecture guidelines. Conducts architecture reviews.
Defines product-wide event sourcing strategy including event catalog governance and schema registry integration. Establishes architecture guidelines for saga/choreography patterns and eventual consistency SLAs. Conducts reviews of event-driven systems ensuring idempotency, ordering guarantees, and replay safety.
Defines product architectural strategy with Hexagonal Architecture. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy for high-load systems. Drives adoption of horizontal scaling patterns, CQRS/event sourcing, and distributed caching across the organization. Establishes CDN and edge computing strategies to meet throughput and latency SLAs at scale.
Defines product architectural strategy with Microservices Decomposition. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Modular Monolith. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Saga Pattern. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy with Serverless Architecture. Establishes architecture guidelines. Conducts architecture reviews.
Defines product architectural strategy: establishes architecture principles, design patterns catalog, and technology radar for the organization. Conducts architecture reviews for critical system changes. Creates architecture governance framework with clear decision-making processes. Drives adoption of architectural best practices across teams.
Defines product architectural strategy with technical debt management focus. Establishes guidelines for architectural debt assessment and modernization roadmaps. Conducts architecture reviews ensuring strangler fig patterns and migration strategies reduce systemic debt.
Defines product architectural strategy with Technology Radar. Establishes architecture guidelines. Conducts architecture reviews.
Observability & Monitoring · 4
Defines enterprise observability strategy with OpenTelemetry spanning product portfolios. Establishes SLO-based approach for multi-service architectures. Coordinates cross-organizational incident management and drives MTTD/MTTR optimization through platform observability tooling.
Defines observability strategy for distributed architectures with Prometheus & Grafana: establishes SLO-based approach aligned with architecture tiers, coordinates cross-team incident management through monitoring standardization, optimizes MTTD/MTTR through architectural observability patterns.
Defines enterprise observability strategy spanning product portfolios — establishes SLO-based approach for multi-service architectures, coordinates cross-organizational incident management, and optimizes MTTD/MTTR through platform observability tooling. Drives reliability engineering culture and error budget governance.
Defines observability strategy for distributed architectures: establishes SLO-based approach aligned with architecture tiers, coordinates incident management across platform and product teams, optimizes MTTD/MTTR through architectural observability patterns and tooling standardization.
Version Control & Collaboration · 3
Defines code review strategy at architecture level: architectural review standards for system design decisions, cross-team review governance, design pattern review practices. Establishes review culture for architectural consistency across teams.
Defines documentation strategy for consulting/architecture practice. Establishes standards for architecture deliverables, solution documentation, and client-facing technical content. Creates documentation templates and frameworks for repeatable engagements. Drives adoption of documentation-as-code across client projects.
Defines Git strategy for multi-team architectures: establishes repository topology standards for microservices and platform teams, designs cross-repository dependency management and versioning policies, drives adoption of Git workflows aligned with architectural decision records.
Documentation · 2
Defines architecture documentation strategy at the product and portfolio level using C4 and arc42 as canonical frameworks. Establishes documentation governance including review gates, freshness policies, and cross-team consistency standards. Conducts architecture reviews ensuring solution documentation captures integration points, quality attribute scenarios, and deployment constraints. Drives ADR adoption as the primary mechanism for capturing and communicating architectural decisions.
Defines diagramming strategy for system architecture, C4 model adoption, and integration pattern documentation at the product level. Establishes standards for deployment diagrams, infrastructure visuals, and architecture decision records. Conducts reviews of architectural diagram consistency.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
What changes at Principal
45 skills get a higher expectation or become core when moving from Lead to Principal. The biggest jumps first.
- Algorithms & Complexity: Advanced → Expert
- Apache Kafka: Advanced → Expert
- API Gateway: Advanced → Expert
- Architecture Decision Records (ADR): Advanced → Expert
- Architecture Documentation: C4, arc42: Advanced → Expert
- AWS: Advanced → Expert
- Capacity Planning: Advanced → Expert
- Clean Architecture: Advanced → Expert
- Cloud Security: Advanced → Expert
- Code Quality & Refactoring: Advanced → Expert
} in the open competency matrix: 61 skills across 5 levels. The matrix is free for individuals and stays free.