Video summary

Как джуну-автоматизатору заполнить резюме на hh.ru | проект PomidorQA | AQA за 60 дней #17

Main summary

Key takeaways

Wellness and Self-Improvement

Key wellness / self-care notes

  • No explicit wellness/self-care content was provided in these subtitles. The focus is on resume-building and job search productivity.

Key wellness & productivity strategies / tips (resume + job search)

1) Build a resume that recruiters can quickly “parse” (ATS + HR)

  • Treat your resume as a business card that shows how useful you’ll be for the hiring team.
  • Use keywords strategically so your resume is selected by ATS (application-tracking systems).
  • Do not overspam keywords:
    • Add skills you truly used.
    • Avoid listing tools/languages you haven’t worked with—this increases the chance of technical questions you can’t answer.

2) Fill HH.ru correctly: essentials that prevent missed opportunities

  • Title/profession: include keywords that match common vacancy titles (e.g., QA Engineer / Automation / API).
  • Contacts:
    • Include phone
    • Include email and ensure it’s accessible
    • Include Telegram (mandatory in their workflow)
    • Add links (especially GitHub)
  • Location strategy:
    • Set Moscow as default location to widen remote/office opportunities.
    • If you set a region (e.g., Krasnodar), fewer matches can appear.

3) Use the skills section like a keyword bank (target up to ~30)

  • Extract skills from testing vacancies (using their QA skills list).
  • Add relevant items such as:
    • Testing types: manual, functional, regression, smoke, negative/positive scenarios
    • Automation: Playwright, TypeScript/JavaScript (often HTTP/API testing)
    • CI/CD / automation execution: GitHub Actions, CI/CD
    • Dev/tooling keywords: Git, GitHub, REST API, SQL (only if you know it), Swagger, Postman (if studied)
    • Architecture/approach: Page Object Model, locators
  • Cap/limit to the maximum permissible number of keywords (practical target: ~30).

4) Project/work experience must show “proof + metrics”

For each project/experience entry, include:

  • Domain (what the product/service is)
  • What you did (tasks/responsibilities)
  • Concrete achievements + numbers

They emphasized example metrics such as:

  • # of automated tests
  • Coverage % of requirements
  • Integration/CI results (tests running in CI, reporting, stability improvements)

Additional guidance:

  • Describe training/projects as practical experience, not generic claims.
  • Prefer real-ish domains/practice over fictitious “detached” examples (if possible).

5) Order of experience matters

  • The top-most job/project should be the “fattest” (most relevant skills/keywords/achievements).
  • If you have multiple experiences, list them in descending relevance.

6) Add a strong “About me / Summary” section (not watery)

Must be:

  • Non-formulaic
  • Keyword-rich
  • Project-relevant

Suggested approach:

  • Mention your target role (e.g., junior automation/QA)
  • Mention you did both manual + automated work (if true)
  • Mention the key project proof (tests, coverage, tech stack)
  • Add a repository link and finish with a call to action

7) Quality checks before applying

  • Proofread (spelling/punctuation).
  • Verify:
    • Links open publicly (GitHub, etc.)
    • Dates don’t overlap
    • You included all required blocks (contacts, summary, skills)
  • Use the resume analyzer / CV check concept:
    • Check that the output contains the necessary keywords and is readable.

8) Matching strategy: respond widely + iteratively

  • Don’t assume experience alone is enough—ATS matching via keywords is key.
  • Use tools/extensions (they mention a “responder” extension) to see how well your resume matches vacancies.
  • Adjust terminology to mirror vacancies (swap specific tool names if you have the equivalent you actually used).

Presenters / sources

  • Presenter/lecturer: Kostya (main host of the lesson)
  • Co-host / participant referenced: Vika
  • Other participants mentioned by name: Sultan, Valentin, Ruslan, Lyuba, Ksenia, Oleg Andreev, Timur, Kostya’s colleagues/students, Slava
  • Sources/brands/tools mentioned (not as presenters):
    • HH.ru (HeadHunter), GitHub Actions, ATS
    • Playwright, TypeScript/JavaScript, locators
    • CI/CD, Postman, Swagger
    • Git/GitHub, REST API, Telegram
    • Confluence, Jira, Grafana, Docker (mentioned as not included)
    • AQA course site / IQA website, AIQA website, web vacancy aggregators

Original video