Slide contents

1. 1. How to grow when you're already a Senior System Analyst

2. 2. Alexander Polomodov

   Technical Director · Client Interfaces, Marketing and Engagement

   Responsible for architecture

   Responsible for delivery management

   Worked through mobile-bank and team evolution

3. 3. From context to a trajectory choice

   Why this experience is relevant

   System analyst competency matrix

   Employee growth process

   Career paths · summary

4. 4. Mobile banking became a platform for business

5. 5. One queue gave way to product and platform teams

6. 6. One team cuts across SuperApp, APIs, and Backends

7. 7. One universal role split into four specializations

8. 8. 02. Competency Matrix

   My version: 5 axes and 4 grades

9. 9. Growth expands the whole five-axis shape

10. 10. A strong Senior grows on every axis

    Requirements

    Software development lifecycle

    Software Design and Architecture

    Operational concerns · Soft skills

11. 11. 03. Employee Growth Process

    8 steps from matrix to feedback

12. 12. Promotion is an evidence cycle, not one conversation

13. 13. 04. Career Paths

    Four distinct roles open after Senior

14. 14. Senior is a choice point, not the summit

15. 15. 01. Profession Lead

    Deepens and scales a profession

16. 16. A Profession Lead develops people and technology

    People

    Hiring · goal setting

    Development · promotion

    Performance · retention · DevRel

    Technology

    Profession standards

    Shared tools

17. 17. 02. Technical Product Manager

    A product with high technical complexity

18. 18. A Technical PM connects product and system design

19. 19. Grade follows scope, not tenure

20. 20. 03. Teamlead

    The whole cross-functional team

21. 21. A Teamlead owns the team across the lifecycle

22. 22. Teamlead is the first management step

23. 23. Interviews assemble a complete Teamlead profile

24. 24. Three interviews carry the core evaluation

25. 25. 04. Architect

    A Staff+ role with broad technical influence

26. 26. Architect is one of four Staff+ archetypes

27. 27. We attest analysts like architects

    Promotion request with architecture artifacts

    Artifacts come from real work

    System Design Interview

    Architecture and development-process interview

28. 28. →. Choose the Kind of Influence

    Product, profession, team, or architecture

29. 29. Four tracks differ by object of responsibility

30. 30. Materials from the original

    Will Larson — Staff Engineer

    Depth × Breadth: four Staff+ archetypes

    Full collection: t.me/book_cube/1552

31. 31. Thank you!

    polomodov.tech

    Slides, notes, and other talks are available on the site

    Alexander Polomodov, Technical Director, Tinkoff

    @book_cube