-
Phase 1. Where to start
Why this course exists and who it fits: the problem it solves, how phases, quizzes, tests and trainers work, and how to go through it without dropping off.
- Зачем этот курс required
-
Phase 2. The role and stepping into it · 17 questions
What changes after the promotion, how to step into a team, and how the lead role differs from the architect role.
-
Phase 3. The team: structure, ownership, people · 35 questions
Who owns what, how to delegate decisions along with tasks, how to grow engineers, what to do when the conversation gets hard, and how all of it changes once you lead several teams.
- Структура и владение required
- Делегирование и рост required
- Трудные разговоры required
- Почему уходят инженеры required
- Руководство направлением required
- Phase test in the cabinet
-
Phase 4. Hiring and onboarding · 11 questions
The profile before the search, three evaluation stages, perception traps, and a new hire's first thirty days.
-
Phase 5. Commitments: deadlines, flow, stakeholders · 36 questions
Why estimates miss, how an estimate differs from a commitment, how to manage inbound requests and outside expectations, how the process scales to several teams, and how to choose between portfolio initiatives by money.
- Оценки и сроки required
- Стейкхолдеры и ожидания required
- Development Models: From Waterfall to Agile
- Scrum: Roles, Events, and Artifacts required
- Estimation and planning: story points and velocity
- Kanban: Flow, WIP Limits, and Pull required
- Scaling Agile: SAFe and LeSS
- Prioritization: the smallest valuable slice
- Портфель и ROI required
- Phase test in the cabinet
-
Phase 6. Engineering norms and quality · 29 questions
What code the team considers acceptable: review norms, technical debt in money and time, the standard as executable rules, engineering practices, requirements artifacts, and security and regulatory obligations.
- Нормы код-ревью required
- Технический долг required
- Executable engineering standard: an AI agent is your ESLint for architecture
- Pull requests and code review required
- Extreme Programming: the Engineering Practices of Agile
- Артефакты и требования required
- ИБ и регуляторика required
- Phase test in the cabinet
-
Phase 7. Reliability and operations · 12 questions
What happens when things break: blameless reviews, a living action plan, on-call rotation and alerts worth reacting to.
-
Phase 8. Decisions and recording them · 33 questions
How to make and record decisions that outlive the team roster: ADRs, the design doc, the architecture committee, evaluating forks by criteria, technology through a manager's eyes, and choosing a vendor with an import substitution plan.
- ADR: how to record architecture decisions required
- How to write and defend a system design: design doc, C4, review
- Архитектурный комитет required
- Architecture choice
- Choosing your starting architecture: monolith, modular monolith, microservices required hands-on code
- Технологии для менеджера required
- How to Split a System into Services: A Marketplace Map
- Вендоры и импортозамещение required
- Phase test in the cabinet
-
Phase 9. Measurement and the business conversation · 28 questions
Delivery metrics that show process health, the harm of individual metrics, outcome metrics that answer whether the work was useful, the IT budget and cloud cost, and talking to executives about technical risk in terms of money.
- Метрики команды required
- Outcome Metrics, Not Output Metrics
- Shipping and the Metrics Loop, Solo hands-on code
- Бюджет ИТ: CAPEX и OPEX required
- Деньги
- Руководство и бизнес-риски required
- Phase test in the cabinet
Программа обучения v2.1.12
Engineering manager
A program for the engineer taking over a team: what changes after the promotion, how to assign system ownership, how to keep commitments to the business, which engineering norms to set, and what to do with people — from hiring to parting ways, then how to run a department of several teams: portfolio and budget, vendors and import substitution, regulation, the architecture committee and talking to executives in terms of risk and money. The technical articles here are only the ones a lead uses as a management tool: decision records, the standard, observability, outcome metrics.
The program has 201 self-check questions in total.