ГАЙД ПО РЕЗЮМЕ в IT (как пройти все фильтры HH)

Summary

The video argues that a résumé can be rejected before a recruiter reads it. HeadHunter’s search and filtering tools may rank or exclude candidates based on role, skills, experience, location, salary expectations, and other criteria. Even after passing those filters, a recruiter may spend only seconds scanning for relevance and red flags.

The goal is to make a résumé easy for search systems to match and clear to a human reviewer.

Frameworks and Practical Playbooks

• Focus each résumé on one target role. Don’t combine unrelated positions or technology stacks in one profile. Create separate versions for distinct targets, such as Go developer and team lead.
• Match the vacancy and company domain. Highlight relevant technologies and domain experience in each job description, not just in a general skills list. For example, fintech experience might include transactions, billing, fraud detection, or payment gateways; e-commerce experience might include catalogs, carts, orders, and inventory.
• Keep the profile complete and current. The presenter recommends keeping job-search status active, filling in résumé fields, listing relevant skills, responding to messages, and updating the résumé regularly. He says he updates his at least weekly.
• Make the header immediately legible. State the target role, location, work format, and accessible contact details. The presenter recommends repeating contact information in the “About” section. A photo is optional, and salary can often be left unspecified.
• Align titles and career history. Keep the target title consistent with the job titles in the experience section. If you were promoted within one company, consider grouping the roles under one employer and showing progression in the description, rather than creating several short entries that could look like frequent job changes. Explain employment gaps where appropriate.
• Describe achievements with context. Use the formula “Did X using Y to achieve Z.” First explain the product, domain, workload, team, and your area of responsibility; then describe what you delivered and its impact. The presenter suggests roughly 6–8 achievements for the latest role, 5 for the previous role, and 1–3 for older roles.
• Use concrete metrics. Provide before-and-after values and explain what was measured. Avoid unsupported or suspiciously round percentage claims.
• List technologies under the relevant job. A skill mentioned only in an older, unrelated role may not help the résumé match a current vacancy. Include commonly requested skills when they genuinely reflect your experience.
• Keep the “About” section focused. The presenter recommends 3–5 sentences describing the tasks you can solve, relevant domains and technologies, and a way to contact you. Include GitHub or courses when they strengthen the application.

Metrics and Examples Mentioned

• The presenter says a developer vacancy can receive more than 100 applications per week.
• He estimates recruiters may spend 10–15 seconds scanning a résumé.
• He reports receiving more than 15 HR messages in his first week after revising his résumé. This is an anecdote, not a guaranteed outcome.
• Illustrative performance claims include reducing a service’s 95th-percentile latency from 450 ms to 120 ms, or response time from 500 ms to 80 ms. These are examples, not targets.
• In an employer-account review, the presenter examines a candidate among the top 80 search results. The candidate had 8 years of experience, but a recent 4-month self-employment period and a résumé focused heavily on Java made their fit for a Go role unclear. The résumé mentioned 70+ microservices but lacked detail about the projects, workload, and the candidate’s specific contribution.

Main Caution from the Résumé Review

The presenter recommends rewriting or cutting irrelevant experience when targeting a different technology stack. In one scenario, he also suggests presenting prior work as Go-focused even without Go production experience, which risks misrepresenting a candidate’s background.

The safer approach is to tailor the résumé honestly: emphasize transferable backend work and any real Go experience, clarify which technologies were used for each project, and make sure you can explain every claim and metric in an interview.

Presenter/source: Максим Карась. The video also demonstrates résumé search using a HeadHunter employer account.