Defines algorithmic standards for the systems team. Establishes library of optimized primitives, conducts critical path reviews.
Roles · Systems Programmer (C/C++) · Lead
What a Lead } should know
39 core skills, 92 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, Cloud & Infrastructure, Testing & QA.
Core skills for a Lead
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Programming Fundamentals · 12
Defines async strategy for the systems team. Establishes async runtime guidelines, conducts async architecture reviews.
Defines code quality strategy for the systems team. Establishes sanitizer policy, fuzzing targets, coverage requirements.
Defines data structure standards for the systems team. Establishes library of concurrent/cache-optimized containers.
Defines pattern catalog for the systems team. Establishes reference implementations with benchmarks, conducts architecture reviews.
Defines Functional Programming Principles standards at team/product level. Conducts architectural reviews. Establishes best practices and training materials for the team.
Defines Generics and Parametric Polymorphism standards at team/product level. Conducts architectural reviews. Establishes best practices and training materials for the team.
Defines Graph Algorithms standards at team/product level. Conducts architectural reviews. Establishes best practices and training materials for the team.
Defines memory management strategy for the systems team. Establishes allocator selection guidelines, NUMA policy.
Defines memory profiling standards at team level: mandatory profiling gates in CI, kernel allocator benchmarks, page fault budgets per component, and memory-mapped I/O usage policies. Ensures consistent methodology across system-level projects.
Defines concurrency strategy for the systems team. Establishes lock-free primitives library, conducts concurrent code reviews.
Defines type safety standards for systems programming teams — establishes unsafe code review policies, type-safe FFI boundary requirements, and compile-time verification standards. Conducts architectural reviews ensuring consistent type patterns across kernel interfaces, hardware abstraction layers, and performance-critical paths.
Cloud & Infrastructure · 1
Defines Docker strategy for systems development: build environment container standards, kernel testing infrastructure governance, cross-compilation container policies. Conducts architecture reviews for containerized systems development infrastructure and optimizes build resource costs.
Testing & QA · 1
Defines testing strategy at product level for systems software: sanitizer integration standards, kernel testing governance, safety-critical testing certification frameworks. Establishes shift-left testing culture with automated quality gates for systems code including memory safety verification.
Architecture & System Design · 1
Defines system architecture for the product platform. Establishes architectural decision records, conducts system design reviews, coordinates cross-component interfaces.
Version Control & Collaboration · 1
Defines code review process for the systems team. Creates checklists for kernel code, drivers, and safety-critical module reviews, trains the team on effective review practices.
Compilers & Languages · 9
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Defines compiler architecture. Establishes development standards. Coordinates the compiler team.
Embedded & IoT · 6
Defines Bare Metal Programming strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Defines C for Embedded strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Defines C++ for Embedded strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Defines Real-Time Systems Design strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Defines RTOS Fundamentals strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Defines Rust for Embedded strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Performance Engineering · 8
Defines benchmarking strategy and performance culture at the team and product level. Establishes standards for benchmark design, statistical analysis, and result interpretation across systems projects. Conducts reviews of performance-critical changes ensuring benchmarks validate real-world impact before release.
Defines CPU profiling strategy for systems programming teams. Establishes standards for profiling in CI/CD pipelines with regression detection on kernel and driver workloads. Drives adoption of continuous profiling tools across the product. Conducts architecture reviews focused on CPU efficiency.
Defines I/O profiling standards and disk performance policies at team level. Establishes practices for continuous I/O tracing using eBPF, ftrace, and perf in production. Conducts reviews of filesystem selection, I/O scheduler tuning, and storage drivers. Drives io_uring adoption across the codebase.
Defines latency optimization strategy for systems infrastructure. Establishes deterministic latency requirements and real-time processing guarantees. Conducts architectural reviews of kernel-level and userspace critical paths. Creates standards for latency measurement, benchmarking, and hardware qualification for latency-sensitive deployments.
Defines memory profiling strategy at the team and product level for systems software. Establishes mandatory profiling gates in CI/CD — memory regression thresholds, leak-free certification for releases, and periodic deep profiling with Valgrind, heaptrack, and eBPF. Standardizes memory budget policies across subsystems, conducts architecture reviews focused on allocation patterns, and drives adoption of memory-safe practices and custom allocator frameworks across the codebase.
Defines performance budget strategy at the team and product level for systems software. Establishes SLA-driven budgets for latency (p50/p99/p999), throughput and resource consumption across kernel modules and system services. Creates budget allocation processes, review gates and automated dashboards. Drives cross-team alignment on performance contracts between subsystems.
Defines resource optimization strategy for systems-level software products. Establishes standards for memory budgets, CPU quotas, and I/O limits across the platform. Conducts reviews of resource-critical subsystems and drives FinOps culture in the team.
Defines Throughput Optimization strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
What changes at Principal
0 skills get a higher expectation or become core when moving from Lead to Principal. The biggest jumps first.
} in the open competency matrix: 92 skills across 5 levels. The matrix is free for individuals and stays free.