Как вкатиться в IT в 2026 году / Все грустно или шанс есть?

Main ideas / lessons (what the video is trying to teach)

• IT hiring in 2026 is hard, but not “everything is lost.” The speakers argue that the market is tougher than before, yet people still get hired; pessimism is discouraged.
• Reality check via numbers and cases. Rather than staying general, the speakers cite statistics (vacancy competition, document checks frequency, offer amounts, hiring speed) and share concrete success cases.
• “Boosting experience” (legends + resumes) is a practical tactic, framed as skills/experience packaging rather than pure fiction. The video later discusses when “cheating” is/was possible and how hiring filters are generally structured.
• Market trends are shifting by specialty.
  • Some ML sub-areas become more accessible or change in competition.
  • Classic ML and QA dynamics evolve over time.
  • Frontend competition increases: more candidates and stronger expectations around framework/library familiarity.
• Successful job search is an active process using tools and repetition, not waiting:
  • Respond broadly and consistently (often daily).
  • Use auto-responses and optimize resume keywords for ATS-like ranking.
  • Update your resume often and maintain “activity” on the platform.
• Interview success depends on preparation artifacts and communication style:
  • Resume + “summary” + “legend” (a story of project responsibilities, decisions, conflicts, and failures).
  • Train answers out loud; avoid sounding like you’re reading.
  • Be ready for technical questions that validate your story.

---

Methodology / instructions presented

1) Decide whether entering IT is worthwhile

• Don’t treat “crisis” as proof that hiring is impossible.
• Assume people are getting hired while some filters exist.
• If you want faster entry, reduce randomness by:
  • building strong “credible experience” presentation,
  • using job-search tools and consistent outreach.

2) Choose a specialty (pragmatic guidance)

• You can start in any direction and still reach target earnings.
• Avoid “silver bullet” thinking (e.g., “this niche is easiest”).
• Suggested empirical approach:
  • compare relative vacancy supply/competition using aggregators,
  • avoid relying on one platform’s absolute counts.

3) Build a “legend” and “summary” for your resume (experience packaging)

• Start from vacancy content:
  • Find a vacancy description and extract responsibilities/project scope.
  • Prefer vacancies with specifics (not vague requirements).
• What to include in the legend/experience block (as described):
  • Company + what the company does
  • Project/team context and your responsibilities (what you did)
  • Stack and architecture (enough to match typical interview expectations)
  • Achievements with measurable impact (use metrics like RPS, latency, seconds, etc., not only “%”)
  • Production process details:
    • how tasks arrived,
    • how you solved,
    • how it was tested,
    • how it behaved in production
  • Conflict + failure stories:
    • include proactive resolution steps,
    • don’t present as pure blame; keep it neutral
  • Dismissal/responsibilities format:
    • describe neutrally (avoid negative about employers)
• Use at least two places/roles of experience to widen applicability and vocabulary for different vacancy profiles.
• Avoid “fake specificity” mismatch:
  • ensure years/skills/projects in your resume realistically match,
  • stay consistent with what you say during interviews.

4) Turn “experience” into interview-ready communication

• Rehearse your story out loud:
  • read 10+ times ideally,
  • record audio and replay,
  • have a friend/relative listen for naturalness.
• In technical interviews:
  • explain concepts in your own words (don’t memorize robotic wording),
  • be ready for questions like: where did you look, what metrics, how did you debug,
  • close gaps honestly: if you lack something, prepare plausible learning steps and what you would do next.
• When asked about your work:
  • provide a structured outline + concrete example,
  • avoid deep rambling (offer to answer follow-ups).

5) Use AI tools strategically (not as full automation)

• Use AI as:
  • an explanation tool for complex topics,
  • a prompt/context clarifier,
  • a generator of practice questions / mock interview scenarios,
  • a review/evaluation helper for your answers or recordings.
• Don’t rely on AI to replace understanding: neural network outputs must be validated with real architecture/context knowledge.
• In hiring reality checks, AI is treated as a tool, not a complete replacement for engineers.
• For “mock interview” training: provide transcripts/recordings and ask AI to critique technical correctness and coverage.

6) Course vs mentoring decision

• Passive learning from courses (“watch and repeat”) is criticized as ineffective.
• Mentoring advantages claimed:
  • roadmap to employment + “exit to the market”
  • community support and feedback,
  • review of artifacts,
  • interview roasts/life coding/group calls
  • payment structure often aligned with outcomes (e.g., more paid after employment).
• Course advantages:
  • some skills are best learned via structured content.
• Suggested rule:
  • a good roadmap answers: what to study, in what order, and what you can do after each block.
• Practice requirement:
  • practice must be useful and progressively harder,
  • ideally a mini-project from start to finish,
  • use tools similar to real corporate workflows (e.g., GitLab/GitHub/CD pipelines).

7) Use Headhunter/response platforms effectively (indexing + “conversion”)

• Respond to vacancies consistently: repeated advice is to “respond to everything,” daily.
  • Example working hours mentioned: 10:00–12:00 and 13:00–15:00 Moscow time.
• Auto-responses:
  • use automation for the “first touch” volume,
  • but avoid paid autoresponses that can worsen filter outcomes (speakers warn that some bots reduce quality/accuracy).
• Cover letter: recommended because recruiters/filters may use it as a proxy for intent/time.
• Resume keyword optimization:
  • platforms score resumes by how many vacancy keywords appear in the text,
  • advice: fill available keyword slots (up to ~30 words mentioned),
  • tools/services can generate keyword lists from vacancy text.
• Resume activity & “issuing higher in search”:
  • higher response activity can raise listing position,
  • suggestions include daily updates and repeated responses (a “hidden pool”/activity points concept is mentioned).

8) Referrals (how they’re treated)

• Referral channels listed:
  • Cold outreach
  • Auto-response (bots)
  • HR contact outreach (if you can find direct contacts)
  • Referral through friends/colleagues
  • Mentors → referrals
  • Specialized vacancy Telegram chats
• Warning about “begging referrals”:
  • if someone pushes referral links with no shared context, it may be low-value or scam-like.
• Better referral tactic:
  • be in communities with some trust/connection; provide your resume and clearly communicate readiness.

9) Security Service / verification (SB) perspective

• The video’s stance:
  • SB typically checks the correctness of provided personal/data rather than performing a full forensic audit of every “experience boosting” detail.
  • direct work-record verification is said to be uncommon; if asked, it may be more about paperwork completeness.
• Advice:
  • provide documents honestly when possible to avoid red flags,
  • don’t spread myths that SB can “see through walls” or automatically detect every legend.

---

Key statistics and quantitative claims mentioned (as stated in subtitles)

Many figures include subtitle noise/uncertainty; below are the main numeric claims that were legible.

Document / contract confirmation frequency

• Around 1 in 10 cases where civil-law contract documents are requested to confirm work.
• Another figure mentioned: ~1 in 10 for direct document requests confirming work.

Time-to-offer and relative speed (mentor/student stats)

• Fastest: QA
• Then Java
• Then frontend
• Emphasis: context matters; don’t judge decisions only by one number.

Mentor platform review totals (approximate)

• “Over last 2 years”: ~500 reviews (reviews equated with employment outcomes by the speaker)
• Specialty examples given:
  • frontend: 275
  • Python: 109
  • Java: 154

Salary ranges (on-hand / offers) by specialty (multiple speakers)

• Frontend
  • newbies: 150–170 (some cases)
  • general average: 200+
  • experienced: 250–300 (some 350–400 rare)
• Backend C#
  • without experience: average around ~220
  • with senior experience: around ~300–310
• ML/analytics
  • broad ranges described; “classic-ish” around ~300k gross
  • one speaker said it could reach ~375 in a “26th year scenario”
• State-sector offers
  • average around ~320k
  • Teamlead event up to ~500k (examples)

Employment outcomes examples

• One mentor claimed: employed about 80 people in C# direction; ~45% had no experience.
• Another anecdote: a student with zero/minimal experience allegedly got ~270,000 salary without extra checks.

---

Speakers / sources featured (identified)

Named participants (speakers in the video)

• Anton Nazarov (main host / speaker; repeatedly mentioned; “Антон”)
• Igor (speaker; discusses Security Service and interview tactics)
• Ruslan (speaker; discusses experience/resume “selling,” training structure, and frontend/ideal-candidate details)
• Andrey (speaker; discusses AI in interviews, frontend/backend skill expectations, hiring realities)
• Nikita (speaker; discusses analytics/ML trends and salary dynamics)
• Nazarov / Bliss / narrator voice (host framing; “Bliss” appears to be the channel/stream persona)
• Sergey (speaker; shares C# mentor employment statistics and experience-related concerns)
• Artyom (speaker; discusses frontend and market observations, plus anecdotes)
• Andrey Afonina (mentioned as a referenced debate/discussion source; cited, not a direct participant with speaking lines in the subtitles)

External “sources” referenced (not speakers)

• Headhunter (platform discussed heavily)
• Getmch / Getmatch / Getmax (tool/site described in “confirmation of experience” stories)
• Habr / YouTube / Habr articles and videos (learning sources)
• LinkedIn (discussed as an additional conversion path)
• Telegram / Telegram chats (referrals and vacancy channels)
• VK (referenced in a story context)
• Gosuslugi (example of document submission/verification)
• Getmch / Getmax demo comparing LinkedIn/GitHub/resume
• UEFA coach / Nazarov.travel / Trade Union conference 2.0 (promotional references for events/services)

Note: If you want, a separate section could be extracted for “verification myths vs claims,” but the summary here focuses on the main requested points.

---