Video summary

Как попасть на стажировку в Яндекс

Main summary

Key takeaways

Business

Summary: How to get an internship at Yandex (Yandex Practicum webinar)

1) What Yandex internship programs are (operating model)

  • Real work, not “just training”: tasks are aligned with team goals, and strong contributions may be integrated into production products.
  • Work-pipeline structure: mentorship + measurable deliverables.
  • Typical duration: 3 or 6 months (you choose based on workload/availability).
  • Primary goal: convert to full-time employment through one of several pathways (e.g., team headcount, rotation to other projects, deferred offer).

Intern support system (process)

  • Mentors: deepen knowledge, share experience, analyze projects in webinars
  • Reviewers: validate tasks, spot errors, propose solutions
  • Curators: ensure schedule compliance, deadlines, and motivation

Intern → offer conversion

  • KPI mentioned: slightly more than 50% of interns remain on staff.
  • No strong bias toward internship length (3 vs 6 months); success depends more on the number and quality of tasks completed.

2) Entry paths (where to apply / how people get in)

Yandex internships are accessible via three main paths:

  1. Standard selection: apply via the website
  2. Educational projects: e.g., summer schools across multiple directions + related events
  3. Events-based accelerated selection (short track): sometimes you can skip parts by meeting a team leader who pre-accepts you

Rule of thumb

  • If you have less than 1 year of experience (ideally from a large tech company), internships are positioned as the route to full-time employment “in ~3 months” (as described).
  • Motivational insight: people may apply multiple times; “failure once” is treated as normal.

Company brand statistic

  • “Every third Yandex developer” started via internship (plus additional internal-leadership examples).

3) Internship organization & employment mechanisms (HR/ops)

After internship completion, possible outcomes include:

  • Offer to the same team (headcount + manager feedback)
  • Rotation to another project (if the original team cannot keep you)
  • Deferred offer: example mentioned as functioning for ~3 years after the internship ends (return later via a reduced-rate selection step)

Additional detail:

  • Interns are paired with mentors—“no one abandons you”.

Concrete product example (case story)

  • An intern suggested and implemented “whisper mode” for Yandex’s smart speaker (Alice), presented as proof that interns can deliver real product features.

4) Selection process: technical vs non-technical track (playbook)

Overall stages are systematized, but content differs by track.

A) Stage 1: Online “YandexContest” (technical) / tests (non-tech)

Technical: YandexContest

  • Online contest with time pressure
    • Example: 5 hours, 5 tasks increasing in complexity
    • Time cannot be paused
  • You must plan execution under constraints (practically: maximize solved tasks)

Non-technical tests (4 main types)

  • Standard test: mini version of work tasks (e.g., market/comps analysis; small presentation output)
  • VCV: video recording Q&A (no live interviewer; answer prompts at home)
  • Quiz / single-correct format (school-like)
  • Assessment center: business game focused on teamwork behavior under stress (team dynamics, flexibility, conflict handling), not just “winning”

Preparation resources

  • Training contest + mini-practice tasks for relevant directions
  • Non-tech tests: described as no time limit at home (time varies by format)
  • Advice: read the vacancy carefully and map it to likely tasks

B) Stage 2: Interview after Stage 1

Technical

  • Whiteboard interview with a developer/analyst
  • No running/compiling code—writing by hand
  • Must speak through reasoning aloud
  • Emphasis: communication + ability to understand and correct mistakes early
  • Tip: proofread before submitting

Non-technical

  • Interview often continues from your test + presentation
  • You must defend decisions and reasoning, possibly handle tricky questions/cases
  • Recommended case-answer framework:
    • STAR: Situation → Task → Actions → Result

C) Stage 2.5: “Finalists database” (team matching mechanism)

  • After passing the first technical assignment + first interview, candidates enter a common database.
  • Team leaders choose about 5–10 candidates for finals.
  • No specific age/student-status privileges were mentioned; selection depends on:
    • performance in earlier stages
    • resume/experience signals
  • If multiple teams invite, the candidate may choose where to join.

D) Stage 3: Final interview with the team

Common final structure

  • Self-presentation: “Tell me about yourself” (free format)
    • Prepare so you don’t “get lost”
    • Include a quick project teaser to guide interviewer questions
  • Then:
    • technical teams may give more advanced tasks than Stage 2
    • non-technical teams focus on expectations alignment + motivation fit

Critical final-stage mistake

  • Don’t respond with “everything is clear, no questions”.
  • Prepare meaningful questions about:
    • team/product work
    • internal processes/infrastructure
  • Avoid purely HR/process questions—HR is expected to handle those.

Recruiter guidance on questions

  • Strong questions show genuine research (e.g., read materials, talks, Habr, public videos)
  • HR/internship logistics questions should be asked to HR during working hours—not in the final team block.

5) Internship conditions (operational/HR facts)

  • Trial period: 2 weeks (described as safe; you won’t “fly off” just for adapting)
  • Schedule: flexible; example window 12:00–18:00, but can shift earlier/later if task requirements are met
  • Salary: described as fixed for all interns (exact figure withheld)

Office / culture operations

  • “Cool offices”, tours, and on-site availability prioritized for better adaptation
  • Community building: interest groups, events, team trips, parties, mentor-led onboarding/adaptation

6) Resume, portfolio, cover letter: application “asset” playbooks

Resume framework (intern resume as 1–2 pages)

Core structure:

  • Summary: 3–4 sentences
    • who you are, role applied for, background, motivation
  • Education: positioned according to vacancy relevance
  • Relevant achievements: hackathons, competitions, training highlights (e.g., top positions)
  • Projects: enough detail + public links to code

Resume rules

  • Emphasize vacancy relevance; downplay unrelated education (optional mention at end)
  • Industrial work experience = commercial relevance; adjacent work also OK
  • Avoid huge unreadable text blocks
  • Avoid “skill dot charts” (e.g., “Python: 4/5”); show concrete capabilities instead
  • Ensure GitHub/portfolio code is real and public

Common “do not do” mistakes

  • Extremely long bio text (unreadable in ~15–20 seconds)
  • Unrealistic skills or mismatch to role
  • Too much text / too many irrelevant details
  • “I have nothing” / no examples
  • Unstructured content

Portfolio requirements (3–5 best works)

Your portfolio should clearly communicate:

  • why you made decisions
  • how you did the work
  • difficulties + results

Guidelines:

  • Select 3–5 projects as your best work; weaker academic work may be omitted
  • IT portfolio:
    • project folders + GitHub links
    • ideally show commit history (consistent activity matters)
  • Non-technical portfolio:
    • detailed case studies: problem, your role, cases, obstacles, outcomes

Important warning

  • Don’t copy training assignments directly into your portfolio.
  • Repackage educational tasks only if you rewrite intelligently and add product-like context:
    • SMART-like goals
    • redesign the case story
    • add metrics/outcomes (especially for digital/business tracks)

Cover letter positioning (motivation artifact)

  • Not decisive, but nice-to-have (useful in motivation screening)
  • Avoid generic templates (“I want to work at a big company”)
  • Avoid AI-written templates (“GPT-written” is noticeable)
  • Keep it short and personal:
    • why this vacancy/team/product
    • what led you to apply
    • what your next career step is

7) On-the-job growth: transition from intern to higher grade (people/ops tactics)

Shared growth principles:

  • Move from “do tasks” → own outcomes
  • Improve your ability to:
    • process ambiguous tasks
    • propose solutions and define approach
  • Learn to identify bottlenecks (“sore spots”) and think in terms of impact
  • Treat team tasks like your own while maintaining work-life balance
  • Handle unclear specs by generating options and iterating with mentor feedback
  • Use feedback loops effectively:
    • ticket system (tracked tasks; completion affects evaluation)
    • regular feedback meetings (example: once a week)
  • Handle criticism constructively: treat feedback as guidance, not personal failure

Key metrics / KPIs mentioned

  • Intern-to-offer conversion: slightly more than 50% remain on staff
  • Internship duration: 3 or 6 months
  • YandexContest example: 5 hours, 5 tasks increasing in complexity
  • Team matching: teams choose about 5–10 candidates from the finalists database
  • Feedback cadence (qualitative): mentor/manager feedback often around ~weekly

Concrete examples & actionable recommendations (condensed)

  • Example impact story: intern-built “whisper mode” for Yandex Alice → promoted as real product contribution.
  • Resume: 1–2 pages, structured; use summary + relevant projects; avoid “skill dot charts”.
  • Portfolio: 3–5 projects, each with “what I did / why / difficulties / result”; include public code.
  • Case interviews: use STAR.
  • Final team interview:
    • prepare self-presentation + project teasers
    • prepare meaningful questions about team/product
    • don’t just say “no questions”

Presenters / sources

  • Anastasia Markova — career consultant, Yandex Practicum career center
  • Daria — recruiter/host (internship programs and selection process); referred to as “Daria” in subtitles
  • Yandex / Yandex-Practicum — the program and educational platform (primary source/organization)

Original video