Video summary

Портфолио дизайнера интерфейсов. Как вырваться из бесконечного поиска и получить оффер?

Main summary

Key takeaways

Educational

Main ideas / lessons

  • A portfolio is a sales teaser: its job is not to show everything you know, but to arouse interest and lead to an interview (i.e., convert “viewing” into “invitation”).
  • Hiring typically has multiple stages, but the key ones discussed are:
    1. initial response/message to a vacancy, and
    2. portfolio review.
  • Your competitiveness is not just “having projects”; you must stand out (through polish and/or “extra skills”).
  • Portfolio content should be structured and scannable: hiring managers have ~one minute to scan.
  • Execution matters: treat the portfolio like a product—UI presentation, animation, and clarity drive attention.
  • Don’t overinvest time: portfolio prep should be a sprint (2–3 weeks max) rather than a long marathon.

Methodology / step-by-step instructions

1) Understand the relevant hiring stages (high level)

Common corporate/studio hiring stages include:

  • response
  • portfolio review
  • technical interview
  • test assignment (and others)

The video focuses on response + portfolio review.

Purpose of each stage (conceptually):

  • Response: create interest and avoid being filtered out early.
  • Portfolio review: act as a teaser of your experience, transforming into an interview invitation.
  • Technical interview: verifies what you claimed.
  • Test task: additional confirmation.

2) How to write the vacancy response (avoid losing early)

  • Avoid overly generic “dry” templates (no personalization).
  • Avoid “template-like” AI responses that clearly weren’t adjusted.
  • Personalize at least enough to not look like a copy-paste.
  • Send one consolidated portfolio link, not many scattered links/files:
    • Don’t send dozens of Figma files / Google Drive links / separate documents.
    • Keep the reviewer’s attention and avoid slowing down the process.

3) Build the portfolio as a teaser (3 components)

The portfolio link should help the viewer understand “who you are” and “why you’re a fit” using three components:

1) High-level cut of your USP (unique selling proposition)

  • A short “who are you / what kind of projects you do” statement.
  • Helps hiring managers quickly see specialization (e.g., mobile interfaces).
  • How to formulate:
    • Think for about a week about your superpowers (what you’re truly good at).
    • Write your thoughts, then convert them into complete sentences.
    • Reference other portfolios for phrasing, but avoid copying blindly.

Recommended structure inside the USP:

  • Mention specialization/grade + focus areas (as a teaser).

Project descriptions should use “key results”:

  • Metrics are optional; key results can be described even without quantitative improvements.
  • Examples include launches, deployed pilots, operational outcomes, etc.

2) UI presentation (visual interface quality + “juiciness”)

  • Hiring managers judge quality partly like they judge clothes: your presentation affects perceived competence.
  • Treat the portfolio as a designed interface:
    • Use ideas like animations/mock device scenes instead of static screenshots only.
  • If your design level is lower than you can now achieve:
    • Polish/rework (even for delivered/NDA work) by adjusting visuals:
      • remove/replace logos and identifiers
      • change color schemes/themes/texts to create a safe public variant
      • keep the rest “as-is” if needed
    • Don’t refuse to show NDA work—show anonymized versions.
  • Use animation as proof of effort and craft:
    • Example approach: animate Figma prototype content (e.g., using mirror/prototype-like behavior) rather than embedding only a single frame image.

3) “VIB” / non-technical personality signals

Convey vibe using:

  • texts (how you formulate and communicate)
  • some photographs or a visible avatar

Even introverts should include at least a small photo/avatar so you don’t seem fully anonymous. Photos can be simple (taken quickly at home).

4) Recommended portfolio structure (avoid “life story” format)

The most effective format makes it clear:

  • who you are as a specialist
  • what you can do
  • projects
  • skills
  • contacts

Don’t turn your portfolio into a resume/cv/entire career narrative.

You can link to a separate resume (e.g., Google Drive), but the main portfolio should remain focused.

5) Portfolio writing workflow (like creating a landing page)

Approach it like a structured landing page:

  1. Write the full structure first (outline, ideas).
  2. Then write complete sentences for content/meaning.
  3. After text is ready:
    • design UI for shots
    • adjust and add animation if needed

Describe pages in order:

  • Main page first (lead-in)
  • then internal page(s) This gives the sense of progress toward an end result rather than getting stuck.

6) How to “stand out” beyond the baseline portfolio (extra skills)

Competitive reality:

  • Many applicants make mistakes (missing links, broken links, irrelevant profiles, etc.).
  • Only a smaller portion becomes real competition.

To win against similar portfolios, add focused extra skills.

What counts as extra skill (examples):

  • AI-assisted generation/concepting
  • complex prototyping used in code testing
  • strong animation/proof-of-motion craft
  • high-level Figma component/variables workflows, etc.

How to add extra skills correctly:

  • Provide evidence: stories, examples, proof in the portfolio.
  • Don’t add long lists of unverified abilities.
  • Only list what you can defend in interviews and show with examples.

Warning:

  • Inflated/unprovable claims lead interviewers to ask deeper questions and reduce your effectiveness (“you bury yourself in the interview”).

Where to host your portfolio (4 formats + pros/cons)

  1. Notion (and analogues)

    • Pros: clear structure; minimal layout effort.
    • Cons: can become “boring/overused,” losing individuality; Notion links may require VPN to open.
    • Suggested use: quick MVP when speed matters.

  2. A link aggregator service (“Benta”) used with Notion

    • Function: acts like a presentation/link container with supported gifs/videos.
    • Pros: flexible media embedding; less separate layout work; adaptive work types (desktop/mobile).
    • Note: consider it complementary; not a complete standalone solution for full project descriptions.

  3. Your own personal website

    • Pros: more individuality/control.
    • Cons (important):
      • overdoing the website design can hurt you—your website visuals may be worse than your UI/product work
      • website should be as ascetic as possible, focusing on text and projects, not flashy web design
      • requires responsive/adaptive work and hosting on a separate domain
    • Tool suggestion: learn Framer (Figma export to Framer workflows exist).

  4. Figma-based presentation

    • Options: Figma prototype mode or Figma Slides (if you have subscription).
    • Structure:
      • left side: project + key result
      • right side: scrolling prototype/story in a presentable format
    • Pros: no need for responsive website adaptation.
    • Cons: requires effort to make it look polished.
    • Example impact mentioned: higher conversion and multiple interview offers after converting to presentation format.

Time management lesson

  • Treat portfolio work like a sprint:
    • spend 2–3 weeks max
  • Don’t exhaust yourself making it for months (3–5 months cited as harmful to stamina).
  • Portfolio isn’t the only task—interview preparation, tests, etc. also require energy.

Speakers / sources featured

  • Speaker: Dania (designer at Yandex)
  • Mentioned companies/products/venues (referenced, not quoted): Yandex, Yandex Lavka, Sberhealth, Gazprom, X5 (plus “top 5 banks” mention), Telegram, Google Drive, Figma, Notion, Craft, Framer, Benta, After Effects, Adobe (implied), Radimag/Tilda (examples of tools for practice)
  • Person mentioned as a portfolio example (visual inspiration): Elena Sakharova
  • Mentor mentioned: Anton (mentor)
  • Manager/supervisor mentioned: Vlad (supervisor)
  • Studio/creator mentioned: Oleg Chulakov’s studio

Original video