Defines Java platform performance strategy. Designs solutions for processing millions of events in real-time via Kafka Streams/Flink. Balances throughput, latency and GC pauses at the architecture level.
Roles · Backend Developer (Java/Kotlin) · Principal
What a Principal } should know
45 core skills, 67 in total. Expectations per skill, and what changes at the next level.
This page lists what a Principal } 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 Principal
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Programming Fundamentals · 9
Designs Java platform async architecture: event bus (Kafka), message broker (RabbitMQ), stream processing (Kafka Streams/Flink). Makes decisions on transitioning to virtual threads (Loom).
Defines Java platform technical debt strategy. Makes decisions on legacy system migration (Java 8 → 21). Establishes metrics and processes for maintaining codebase quality.
Designs platform-level data models: Protocol Buffers for inter-service communication, Apache Arrow for analytics, off-heap structures for low-latency services. Defines serialization strategy.
Defines Java platform architectural patterns: DDD, Hexagonal Architecture, Event-Driven. Shapes reference architecture on Spring Boot/Spring Cloud. Evaluates approach trade-offs for business context.
Designs platform-level generic frameworks and libraries: type-safe query builders, generic repository patterns, plugin systems. Evaluates type erasure limitations and designs workarounds.
Designs Java platform concurrency model: virtual threads vs reactive, lock-free algorithms for hot path, LMAX Disruptor for ultra-low-latency. Defines scaling strategy under load.
Shapes Java platform object model. Determines where OOP is optimal (domain layer) vs functional approach (data pipelines). Designs shared kernel and domain events between services.
Shapes Java platform typing standards. Evaluates type system evolution (pattern matching, sealed classes, value types/Valhalla) and plans adoption. Designs type-safe inter-service contracts.
Backend Development · 6
Designs organizational event-streaming platform: multi-cluster Kafka, cross-datacenter replication (MirrorMaker 2), Kafka Connect for integrations. Defines governance for event contracts and schema registry.
Shapes enterprise caching strategy for Java platform: CDN + Spring Cache + Hibernate L2 cache layers, cache budgets per service. Defines data freshness requirements for business domains and establishes caching governance across microservices.
Designs organizational search platform: multi-tenant indexes, cross-cluster search, ML-based ranking. Defines indexing standards and governance for schema evolution.
Defines Java Spring Ecosystem strategy at company level. Evaluates new technologies and approaches. Shapes enterprise standards and reference architectures.
Designs organizational messaging platform: multi-protocol broker, integration patterns, event-driven communication standards across domains. Defines SLA for message delivery.
Designs organizational caching platform: shared Redis infrastructure, data partitioning strategy, cross-service cache coherence. Defines governance for cache keys and TTL policies.
Database Management · 7
Designs platform data model: bounded context → database mapping, shared entities via domain events, data mesh principles. Defines schema evolution strategy without breaking changes.
Designs platform indexing strategy: cross-service search indexes, index maintenance automation, capacity planning for I/O. Defines trade-offs between read and write performance.
Designs platform migration strategy: coordinating schema changes between services, database-per-service migration, data versioning. Defines backward compatibility policy.
Designs organizational MySQL data strategy: multi-master replication, sharding (Vitess), migration from monolithic DB to database-per-service. Defines backup and disaster recovery standards.
Designs organizational PostgreSQL platform: logical replication, Citus for distributed queries, TimescaleDB for time-series. Defines migration strategy and backward compatibility.
Designs platform-level data access strategy: CQRS for read/write model separation, materialized views for analytics, polyglot persistence. Defines SLA for query latency.
Designs platform consistency model: which operations require strong consistency, where eventual is acceptable. Defines distributed transaction strategy between services.
API & Integration · 4
Shapes documentation platform: unified developer portal for all organizational APIs, automated SDK generation, interactive sandbox. Defines documentation governance.
Shapes organizational versioning strategy: unified rules for all APIs, deprecation governance, cross-team migration coordination. Defines SLA for backward compatibility.
Shapes organizational GraphQL platform: supergraph from microservices, schema governance, query analytics. Determines when GraphQL is optimal vs REST vs gRPC.
Shapes organizational API strategy: API Gateway, developer portal, API governance. Defines standards for public and internal APIs. Designs API platform with self-service provisioning.
Cloud & Infrastructure · 3
Shapes organizational cloud strategy: multi-cloud/hybrid approach, landing zone, platform services. Defines standards for Java workloads: compute strategy, data services, observability.
Shapes organizational container strategy: container registry, image governance, base image management. Defines standards for Java-specific optimizations (GraalVM, CRaC).
Designs organizational K8s platform: multi-cluster management, platform engineering (internal developer platform), cost optimization. Defines standards for Java workloads in Kubernetes.
DevOps & CI/CD · 1
Shapes organizational CI/CD platform: shared runners, reusable pipeline library, deployment governance. Defines DORA metrics targets and continuous improvement process.
Testing & QA · 4
Shapes integration testing platform: shared Testcontainers images, test environment orchestration, end-to-end testing across services. Defines quality gates for deployments.
Shapes organizational testing culture: TDD/BDD standards, testing frameworks, shared test infrastructure. Defines quality metrics and acceptance criteria for releases.
Shapes organizational testing infrastructure: custom Testcontainers modules for platform services, remote container registries, shared test infrastructure. Defines standards for integration testing across teams.
Shapes organizational testing framework: shared test libraries, testing best practices, automated quality reporting. Defines standards for different types of Java services.
Security · 3
Shapes organizational identity platform: centralized IAM, federation, zero-trust architecture. Defines auth standards for all services: token format, scoping model, audit requirements.
Shapes organizational security program: OWASP SAMM assessment, security champions program, bug bounty. Defines security governance for all Java services.
Defines organizational secure development lifecycle: security requirements, threat modeling, security testing, incident response. Shapes security engineering culture.
AI-Assisted Development · 1
Defines organizational AI-assisted Java development strategy. Evaluates and selects AI tools. Shapes governance policies: compliance, IP protection, quality gates for AI-generated code.
Architecture & System Design · 2
Shapes architectural culture: reference architecture for Java services, domain/application/infrastructure layers. Designs shared kernel between services. Determines when clean architecture is justified.
Defines organizational architecture strategy: reference architecture on Spring Boot/Cloud, inter-service communication standards (gRPC, Kafka), data mesh. Plans platform evolution.
Observability & Monitoring · 3
Shapes organizational OpenTelemetry platform: collector infrastructure, backend (Tempo/Jaeger), correlation with metrics and logs. Defines observability budget and governance.
Shapes observability platform: metrics and dashboard standards for all Java services, SLO framework, cost management for metrics. Ensures end-to-end visibility.
Shapes observability strategy: unified logging standards for all Java services, centralized log platform (ELK/Loki/Datadog). Defines SLI/SLO based on logs.
Version Control & Collaboration · 2
Defines organizational review standards: cross-team review for shared components, architectural review board, automated quality gates. Shapes engineering excellence culture.
Defines organizational versioning strategy: mono vs multi-repo, release management, dependency management via Maven BOM/Gradle platform. Coordinates releases between services.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
} in the open competency matrix: 67 skills across 5 levels. The matrix is free for individuals and stays free.