Video summary

Найди работу БЕЗ советов с КУРСОВ IT РЕЗЮМЕ КОТОРОЕ РАБОТАЕТ

Main summary

Key takeaways

Business

Core issue (market reality framed as HR process problem)

The speaker argues that many IT job seekers are rejected not because there’s “no demand,” but because they fail an employer/HR screening process—most notably due to a resume that doesn’t match what recruiters need to verify quickly.

“Resume through the eyes of an employer” (playbook)

The video repeatedly frames the resume as a sales document for the buyer (HR/recruiter), not a self-expression document.

Key principles / checks (high priority)

  • Contacts must be present (email, Telegram, phone).
  • Communication readiness: candidates must respond immediately to recruiter outreach; “tomorrow I’ll answer” = lost opportunities.
  • Include only what’s potentially relevant to the target role:
    • relevant work experience
    • education (only if it helps)
    • required time zone
    • availability
    • desired role type (job vs internship)
    • role-relevant stack keywords
  • Do not include irrelevant content, including personal hobbies/content unrelated to the role.
  • Be easy to read:
    • short, scannable formatting (not a big text block)
    • bullet points / clear sections (recruiters use Ctrl+F)
    • fix typos and title mismatches (e.g., incorrect language/framework name or wrong job title)
  • Keyword accuracy:
    • put the right keywords in the stack section
    • don’t list unrelated technologies
  • Avoid “mass-sending” generic resumes: tailoring matters because HR scans quickly.

“About me” rules (especially for juniors)

For juniors, “About me” is the most important point, but it should:

  • not be a life story
  • not include irrelevant personality markers (e.g., rings, diseases, quirky items)
  • be 3–5 lines max
  • sell “fit” to the recruiter:
    • greeting (speaker suggests “Hello!” as acceptable style)
    • what role you’re seeking (job/internship; specific target such as product/golang/devops)
    • availability + communication ease
    • willingness to work hard

For experienced programmers: “about me” is less emphasized than the career description, but it should still communicate domain and fit.

Concrete examples / red flags (from the speaker)

  • Wrong or misleading resume details
    • missing contacts entirely
    • wrong job title (e.g., “software developer” instead of the target)
    • typos in language names
    • listing unrelated skills in keywords (e.g., front-end role but also Haskell)
  • Irrelevant “about me” content
    • long personal passion blocks (e.g., violets for multiple paragraphs)
    • personal/criminal content or personal social media examples (VK/Telegram “naked carcass/dogs” style examples)
  • Experience inflation / “fake” work
    • the speaker warns that inventing experience is risky because you’ll be questioned during HR/security checks and technical probing
  • Over-verbosity
    • e.g., “400 lines about framework subtleties” while leaving critical contact/link info unusable

Resume structure / content formulas (actionable)

Template concept (sequence the speaker recommends)

  • 1–2 sentences: describe the business domain you worked in (e.g., fintech gets more callbacks than “generic fintech scripts”).

  • Main responsibilities:

    • if nothing special, keep standard responsibilities (code, review, deploy)
    • highlight differentiators if real:
      • legacy revival
      • specialized high-end domain
      • complex internal demo/client work
      • uncertainty problem-solving
  • Last section: the speaker notes that “achievements/responsibilities” formulas are common, but recommends focusing on what’s directly relevant and verifiable.

Stack section

  • Include role-relevant technologies only, aligned to job requirements.
  • Recruiters search keywords using Ctrl+F, so stack keywords must match.

KPIs / targets mentioned

No formal business KPIs (revenue/CAC/LTV/churn) are presented.

Instead, the speaker gives time-based hiring outcomes as implicit targets:

  • Response time expectation: respond within hours/days, not “tomorrow.”
  • Intern pipeline: conversion may take up to ~1 year via an ethical path.
  • In “speed” scenarios (adventurer method): first employment claims include ~2 months to an offer.

“Experience with no experience” (GTM-like funnel alternatives)

The speaker provides three paths (“methods”) to get hired when you don’t have relevant experience.

Method 1: “Adventurers” (resume + invented/optimized experience) — unethical/risky

  • Claim: people may get hired with fabricated resume claims; a “buddy with no experience” allegedly got ~5 years’ worth of work and lasted >6 months (presented as the “smartest case”).
  • Execution details:
    • you must still be able to explain the invented experience when asked
    • cross-check dates and consistency (security/HR checks)
  • Recommendation tone: works but not recommended—“for the stupid and brave.”

Method 2: “Smart young honest guys” (internships at big companies) — ethical and calm

  • Suitable for students with 2–3 years ahead.
  • Emphasis:
    • internships in large companies
    • strong focus on patience and process:
      • cover letter
      • test tasks
  • Timeline: job conversion may take ~1 year (or may fail).

Method 3: “Dead sweaty donkeys” (take any first job to get experience)

  • Claimed strategy:
    • accept low-quality vacancies / exploitative onboarding to get first programming experience.
  • Example metrics from the speaker’s story:
    • ~2 months from first book to offer
    • initial salary: ~11,000 rubles
    • then: ~180,000 rubles in the first 3 weeks
    • later to product development: ~330k per month (with “cookies”/benefits mentioned)
  • Warning:
    • can be “hell,” heavy workload, limited learning initially
    • requires studying afterward even after getting a “real” programming role

Key operational/management claims (about the hiring system)

  • Recruiters/HR skim hundreds of resumes daily and decide quickly.
  • Screening is largely mechanical:
    • keyword scanning (Ctrl+F)
    • formatting readability
    • exact matching of role title and stack terminology
  • Therefore, candidates should optimize for screen-passability rather than “being technically impressive on paper.”

Actionable checklist (condensed)

  • Add email + Telegram + phone
  • Ensure job title + language/framework names are spelled correctly and match the target role
  • Keep resume short and scannable (bullets, spacing)
  • Populate stack section with only relevant keywords
  • Make “About me” for juniors 3–5 lines max and role-focused
  • Remove irrelevant content: hobbies, unrelated technologies, personal/social posts
  • Check consistency for HR/security: dates, roles, timelines
  • Respond immediately to recruiter messages

Presenters / sources

  • Presenter: the speaker (unnamed in the subtitles)
  • Sources mentioned: the speaker references their own Telegram/streams and “knowledge base” links / “database of real interviews and resumes,” but no specific third-party external sources are explicitly named.

Original video