Brief
The essential idea
At Techlead Conf X, moderator Maxim Vishnevsky of Mindbox joined Gleb Mikheev of Sber, Alexander Beloturkin of Delimobil, and Alexander Polomodov of T-Bank to compare technical-leadership and individual-contributor career systems. A Tech Lead shapes the technology landscape and dependencies, while an IC can drive system change without formal people management.
The market often blurs these roles through the playing-coach model and poorly defined grades. The panel proposes evaluating ICs through Scope, Impact, Leadership, and Improvements, with Staff, Principal, and Fellow representing progressively wider responsibility—from roughly dozens of engineers to company-wide and industry-recognized influence.
Context makes internal Staff+ development especially valuable, although hiring should still test systems thinking and influence. RFCs, engineering guilds, and early communication coordinate initiatives without suppressing ownership, avoiding both central approval bottlenecks and unaligned guerrilla change.
Decision lens
Key takeaways
An IC track needs explicit zones of influence, not only grade names.
Tech Lead and Staff+ responsibilities overlap but should not remain ambiguous.
Scope, Impact, Leadership, and Improvements provide a broader evaluation model than skill checklists.
Staff, Principal, and Fellow differ primarily by the scale and durability of their influence.
Internal growth preserves organizational context that is critical at Staff+ level.
RFCs and guilds coordinate technical initiatives without requiring people-management authority.
Technical careers can reach strategic company influence without moving into management.
Workplace experiment
Apply it at work
- 1
Define Tech Lead and Staff+ ownership boundaries for one organization and publish examples of expected decisions.
- 2
Rework an IC evaluation rubric around Scope, Impact, Leadership, and Improvements.
- 3
Create an RFC and peer-review mechanism for cross-team initiatives before implementation begins.
- 4
Design one internal development assignment that gives a senior engineer broader organizational context.
Choose one action, define the observable effect, and keep the first test small enough to reverse.
Evidence
Sources and further reading
Primary source
Additional sources
Channel, aggregator, and commentary links confirm the work; they are not the primary source.