Defines algorithmic standards for the embedded platform. Establishes optimized algorithm library, conducts critical path reviews.
Roles · Embedded Developer · Lead
What a Lead } should know
22 core skills, 56 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, Testing & QA, Version Control & Collaboration.
Core skills for a Lead
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Programming Fundamentals · 6
Defines async patterns for the embedded team. Establishes interrupt handling standards, event-driven design, DMA strategy.
Defines code quality strategy for the embedded team. Establishes MISRA compliance process, conducts architecture reviews.
Defines data structure standards for the embedded platform. Establishes statically-allocated container library, conducts reviews.
Defines memory management standards for the platform. Establishes memory budgeting approaches, leak detection, MPU protection.
Defines concurrency standards for the embedded team. Establishes inter-task communication patterns, conducts review of concurrency-critical code.
Testing & QA · 1
Defines testing strategy for the embedded team. Establishes coverage requirements, test pyramid for firmware, CI integration.
Version Control & Collaboration · 2
Defines code review standards for the team. Establishes review checklist for safety-critical embedded, conducts architecture reviews.
Defines Git strategy for the embedded team. Establishes branching model, release tagging, submodule management guidelines.
Embedded & IoT · 10
Defines bare-metal standards for the product line. Establishes approaches to boot security, hardware abstraction, porting between MCU families.
Defines BLE strategy for the product line. Establishes GATT profile standards, security model, conducts BLE architecture reviews for devices.
Defines C coding standards for the embedded team. Introduces static analysis (PC-lint, Polyspace), establishes platform porting strategy.
Defines C++ subset for the embedded team. Establishes guidelines for STL usage, templates, memory management on resource-constrained platforms.
Defines debug strategy for the product line. Establishes fault handling standards, logging, remote diagnostics for field devices.
Defines analog peripheral standards for the platform. Establishes calibration procedures, conducts analog subsystem reviews.
Defines MQTT strategy for IoT platform. Establishes topic naming conventions, QoS policy, security standards for device fleet.
Defines real-time requirements for the product line. Establishes timing constraint verification methodology, conducts review of time-critical systems.
Defines RTOS strategy for the product line. Establishes task decomposition standards, inter-task communication, conducts architecture reviews.
Defines communication protocol standards for the platform. Establishes unified driver architecture for SPI/I2C/UART, conducts driver reviews.
Performance Engineering · 3
Defines CPU profiling standards for the embedded team. Establishes performance budgets, automated regression alerting.
Defines latency optimization standards. Establishes timing budgets for critical paths, worst-case latency analysis methodology.
Defines resource optimization strategy. Establishes resource budgets (Flash/RAM/power) for embedded products, 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: 56 skills across 5 levels. The matrix is free for individuals and stays free.