ЛЕГЕНДА: Откуда взять опыт, чтобы попасть на собес

Summary

The video is a tutorial on fabricating an IT work history—what the presenter calls “spinning experience” or creating a “legend”—to improve a candidate’s chances of getting interviews. The presenter treats the invented history not as a short interview story, but as a replacement biography that must remain consistent over time.

The advice involves misrepresenting employment and experience. The presenter’s claims about hiring and background checks are not independently verified.

Main ideas

• The video’s wider series: The presenter says this installment is about creating a work-history narrative. Later installments will cover self-presentation, technical interview questions, negotiating an offer, and employment paperwork.
• Why people consider it: She describes a difficult entry-level market and argues that candidates without experience may struggle to get interviews. She also says that some people with limited real experience may find it insufficient for the roles they want.
• Four common fears she addresses:
  • Having a different or unrelated job history in official employment records.
  • Being too young to claim several years of experience.
  • Having already applied widely with a real résumé.
  • Failing an interview, getting an offer, or coping with the job afterward.

She argues that résumé screening and accounting checks may be separate, and suggests that interview performance and preparation matter more than the résumé’s stated history. These are her assertions, not verified facts.

• How much experience to claim: She says the amount depends on the role and employer. In her view, outsourcing firms may consider shorter experience histories, while product companies and some competitive specialties may expect more. She describes “experience inflation” as a trend affecting both inexperienced candidates and people with only a small amount of real experience.
• Her stance on criticism: She argues that employers primarily care whether work gets done, while experienced colleagues may object because they earned their skills over time. She recommends keeping the deception private from colleagues, particularly early on.
• After hiring: She acknowledges that doing the job can be difficult and says a newcomer may need to invest substantial extra time or pay for mentoring or hands-on help to complete tasks.

The presenter’s suggested approach

The following summarizes the presenter’s instructions; it is not an endorsement.

1. Choose a target employer type.

   • Decide whether the résumé is aimed mainly at a product company, an outsourcing company, or an outstaffing company.
   • Shape the supposed experience to match the kind of role and work that the target is likely to offer.

2. Choose familiar or interesting domains.

   • Draw on previous work or personal interests.
   • Consider products and services the candidate uses regularly.
   • Ask IT contacts or people in professional communities to explain their projects and work practices.
   • The presenter’s examples include fintech, education, food delivery, healthcare, social media, and e-commerce.

3. Select companies and projects that can be researched.

   • The presenter warns against inventing companies or relying on obscure, unverifiable project histories.
   • She recommends using real companies and publicly visible products, such as apps or websites, and checking their case studies and release notes.
   • She says the narrative should include multiple projects, relevant technologies, colleagues, established processes, and a believable progression in responsibility.

4. Build a consistent timeline.

   • Align the claimed study period, jobs, projects, and transitions.
   • Account for major events or personal circumstances that could explain a job change.
   • The presenter says very short stays at companies, frequent job changes, and implausible career jumps can look suspicious.
   • She recommends gradual progression rather than a sudden leap from beginner to experienced specialist.

5. Research the products and work in detail.

   • Use the app or website as an ordinary user and learn its features and flows.
   • Consider what someone in the claimed role might have done. For example, a tester might examine failure cases, while a developer might study the interface or implementation.
   • Check release notes and company case studies for changes, project timing, and features.
   • Look at job postings, résumés, and professional contacts for information about technologies, team sizes, and processes.
   • The presenter also suggests using AI tools to brainstorm plausible tasks or interview questions, and listening to interview recordings to learn how candidates discuss projects and mistakes.

6. Make the narrative chronological and rehearsed.

   • Prepare an account covering how the candidate started learning, got their first role, worked on projects, developed skills, and moved between jobs.
   • The presenter recommends practicing a long, detailed version—around 20–30 minutes—so questions about different points in the timeline can be answered consistently.
   • She says a later self-presentation video will show how to condense this material into a short pitch.

7. Protect identifying information.

   • To avoid recognition from earlier applications, the presenter suggests using alternate contact details and changing identifying details on a résumé.
   • She says this may reduce the chance that an old application is matched to a new one, while noting that fully anonymous résumés may perform worse.

Approaches the presenter says to avoid

She cautions against histories that rely on:

• Invented companies or hard-to-verify work.
• Freelance or project work used as a vague substitute for commercial employment.
• Very short tenures or repeated job changes.
• Outdated technologies that do not match the target market.
• A single project completed alone, with no evidence of teamwork.
• Rapid switches among unrelated professions presented as equivalent experience.
• Claims of ambitions, such as rapid promotion, that the target company cannot offer.
• Some industries or projects that she believes may create an unfavorable impression.

Three example profiles

To demonstrate the process, the presenter constructs three fictional profiles aimed at different levels of experience:

• Vasya: A longer-serving employee at one outsourcing company, with a sequence of projects in food delivery, education, and real estate.
• Petya: A more experienced profile that moves from outsourcing projects to a banking project and then to a product company, with the stated goal of moving into another larger product business.
• Natasha: A less experienced profile involving study, an internship, short outsourcing projects, and later outstaff work on a recognizable product. The narrative explains why she is looking for another role.

The presenter emphasizes that these are templates for building a personalized account, not stories viewers should copy verbatim.

Sources and speakers featured

• Speaker: One unnamed female presenter from the channel авось прорвемся. No guest speakers or interviewees appear as distinct speakers in the supplied subtitles.
• Sources and materials mentioned: The presenter’s consultations and mentoring experience; hiring and career chats; interview recordings; résumé and vacancy listings on HeadHunter; company websites and case studies; app stores and release notes; conversations with IT contacts, colleagues, and mentors; and ChatGPT or similar AI tools.
• Examples discussed: Companies and products including Level Kitchen, Skyeng/Lang, LSR, Austin, Labyrinth, Surf, SimbirSoft, and HeadHunter.