Video summary

IT-направления будущего / Куда перекатываться в IT 2026 году

Main summary

Key takeaways

News and Commentary

Summary of the video’s main points

  • Motivation to switch IT directions (survey-based): The speaker references results of a large survey. Many people feel stagnation in their current roles—such as fewer job postings, slower salary growth, and more responsibility without clear career momentum.

    • Most current specialties: end-to-end/full-stack, front-end, and testing.
    • Thinking about switching: over 80% consider changing direction, but only a small fraction actually act.

  • Why people want to change: The main drivers cited are:

    1. Prospects in another direction
    2. Salary size
    3. Lack of growth in the current role

  • How to interpret salary data correctly: Career-site salary “ratings” can be misleading because they aggregate different stacks/locations and include outliers. The speaker advises:

    • Use these stats only for relative comparisons (e.g., backend tends to pay more than front-end, and front-end more than testing), not for exact numbers.
    • For real expectations, rely on specific cases (interview/salary examples tied to resumes and skills).
    • He also promotes a community where people share salary outcomes.

  • Salary jump is not automatic: Even when moving to a related specialty with higher pay, the “payoff” depends on learning cost and time. Switching from front-end to back-end, for example, may bring only a moderate raise but requires significant ramp-up time (learning and building experience). The increase may not last if the new role doesn’t align with how you build value.

  • The “no growth” misconception: Stagnation often comes from reaching a plateau where tasks stop feeling new—not because skill-building is pointless.

    • The speaker claims that not learning new tech doesn’t automatically mean you’ll earn less.
    • What matters is whether you’re aiming to solve new challenges (growth via learning) or to maximize income (money isn’t guaranteed by learning alone).

  • Best high-level direction to switch toward (ranked):

    1. End/Front-End (EE/DEC in subtitles; web/frontend-style work implied) — said to be winning by a large margin, especially because AI makes some front-end work (code generation, UI building) easier.
    2. ML/DS/NLP — second place, driven by the AI “gold rush,” though he warns many people underestimate the actual work and assume it’s only heavy math.
    3. DevOps — third place, with a major warning about responsibility level and release-triage accountability. He advises candidates to speak with other DevOps engineers before committing.

  • Observed career transition patterns (from people who changed):

    • Common moves:
      • front-end → stays in front-end
      • testing → automated testing → back-end
      • back-end → DevOps or ML/DS
    • Some unusual moves are also mentioned (e.g., back-end → sales manager, sales → back-end).
    • Generally, transitions bring more responsibility and higher abstraction of tasks.

  • Payoff after transition (survey outcomes):

    • Among successful transitions:
      • 47% saw a significant salary increase (50%+)
      • 20% saw a smaller increase
      • 20% saw no change
      • 14% saw a decrease
    • Satisfaction is high:
      • 43% rated 4/5
      • 37% rated 5/5
    • He adds a critique: people may rationalize their decision (post-purchase justification).

  • How fast people switch / learning timelines:

    • 41% transitioned in under 3 months
    • 32% in 3–6 months
    • only 7% took over a year

  • Fear and hiring filters as practical barriers:

    • Biggest fears are failure/uncertainty during interviews and the difficulty of learning.
    • He argues failure feels more frightening than success feels rewarding.
    • Recommendation: prepare using interview “leaks”/question banks and practice.

  • Tactics to reduce risk (“test demand” approach):

    • Treat career change like product validation:
      • create tailored resumes for the new direction
      • use AI/resume generation and keyword optimization
      • measure response rate/invitations
    • Also suggests short HR screenings to gauge salary expectations.

  • Don’t over-invest in “market monitoring”:

    • Constantly consuming “doom” signals from communities (backend dying, salaries falling, etc.) isn’t reliable.
    • Better: start the transition process and validate with real steps (resume work, interviews, mentorship).

  • Additional tactical advice:

    • Expect adjacent responsibilities once you switch (AI and lean teams blur roles).
    • Mentoring is useful because it reduces wasted time and provides a roadmap.
    • Continuous theory-only studying is less effective than applying.
    • Maintain resilience via competitive sports/hobbies to avoid spiraling after repeated interview rejections.

  • Timing note: The speaker emphasizes that a new hiring period is expected in the fall, leaving roughly 3 months in summer to build a transition strategy.

  • Anti-entrepreneurship commentary: He argues entrepreneurship isn’t automatically more profitable during crises and rising taxes, and challenges “SaaS ChatGPT make me rich” narratives—emphasizing that customer acquisition and business economics still matter.

Presenters / contributors

  • The video speaker (author/host) — referenced as “I” throughout; no specific name is provided in the subtitles.

Original video