Conducts algorithmic reviews for Electron projects. Defines performance standards. Mentors on TypeScript optimization.
Roles · Desktop Developer (Electron/Tauri) · Lead
What a Lead } should know
39 core skills, 54 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, Frontend Development.
Core skills for a Lead
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Programming Fundamentals · 8
Defines async strategy for the Electron platform. Establishes async coding standards. Coordinates error handling strategy.
Establishes code quality standards for the Electron team. Defines metrics, coordinates tech debt. Introduces quality gates in CI.
Defines data structure standards for the Electron team. Coordinates data layer architecture. Mentors on data structure selection.
Defines architectural patterns for the Electron team. Conducts design review. Establishes pattern catalog for desktop development.
Defines process model for the Electron platform. Establishes multi-process standards. Coordinates parallel processing strategy.
Defines OOP standards for the Electron team. Conducts design review. Establishes TypeScript coding guidelines.
Defines TypeScript strategy for the Electron team. Establishes type safety guidelines. Conducts reviews focused on typing.
Backend Development · 1
Defines Node.js strategy for the Electron team. Coordinates native module management. Establishes backend architecture standards.
Frontend Development · 8
Defines build and bundle strategy for the Electron team. Establishes size budgets. Coordinates build infrastructure.
Defines component testing strategy. Establishes component quality standards. Coordinates component library testing.
Defines CSS strategy for the Electron team. Establishes design tokens and style guidelines. Coordinates CSS architecture.
Defines React standards for the Electron team. Coordinates component library. Establishes React best practices for desktop context.
Defines state management strategy for the Electron platform. Establishes state design patterns. Coordinates state architecture across modules.
Defines Tailwind strategy for the Electron team. Establishes component conventions. Coordinates design system evolution.
Defines Vite strategy for the Electron team. Coordinates build tooling standardization. Establishes Vite best practices.
Defines Web API strategy for the Electron platform. Establishes guidelines for Web vs Node.js API choice. Coordinates API abstraction layer.
API & Integration · 2
Defines API strategy for the Electron product. Coordinates API contracts with backend. Establishes API client standards.
Defines real-time strategy for the Electron platform. Coordinates WebSocket infrastructure. Establishes message protocol standards.
Cloud & Infrastructure · 1
Defines Docker strategy for Electron CI. Coordinates container infrastructure. Establishes Docker best practices.
DevOps & CI/CD · 1
Defines CI/CD strategy for the Electron team. Coordinates release automation. Establishes deployment standards.
Testing & QA · 3
Defines E2E strategy for the Electron product. Coordinates E2E infrastructure. Balances coverage and cost.
Defines integration testing strategy. Coordinates test infrastructure. Establishes integration testing standards.
Defines testing strategy for the Electron team. Establishes coverage targets. Coordinates test infrastructure.
Security · 2
Defines security strategy for the Electron team. Establishes security review process. Coordinates security audits.
Defines secure coding standards for the Electron team. Establishes security review process. Coordinates security training.
AI-Assisted Development · 2
Defines LLM strategy for the Electron team. Establishes AI policies. Coordinates AI-assisted development.
Defines AI-assisted development strategy. Establishes Copilot guidelines. Evaluates productivity impact.
Observability & Monitoring · 1
Defines logging strategy for Electron. Establishes GDPR-compliant logging standards. Coordinates observability.
Version Control & Collaboration · 2
Defines code review process for the team. Establishes review checklist for Electron. Coordinates review workflow.
Defines Git strategy for the Electron team. Establishes branching model. Coordinates release process.
Desktop Development · 8
Defines update strategy for the Electron product. Coordinates update pipeline with CI/CD. Establishes SLAs for update delivery.
Defines distribution strategy for the Electron product. Coordinates packaging with CI/CD. Establishes signing and notarization standards. Plans store distribution.
Defines technical strategy for Electron development. Establishes security standards (CSP, sandbox). Plans migration between Electron major versions. Coordinates with Chromium/Node.js upgrades.
Defines security strategy for the Electron platform. Establishes security checklist and review process. Coordinates penetration testing and CVE response.
Defines IPC strategy for the Electron platform. Establishes IPC patterns and security guidelines. Coordinates cross-process architecture.
Defines architectural patterns for the Electron team. Establishes coding guidelines for separation of concerns. Conducts architecture review.
Defines offline-first strategy for the Electron product. Coordinates sync protocol with backend. Establishes data standards.
Defines plugin ecosystem strategy. Establishes plugin API standards and review process. Coordinates plugin developer community.
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: 54 skills across 5 levels. The matrix is free for individuals and stays free.