HR brand in IT companies: the specificity of attracting developers
Why an employee convinces better than the 'Careers' page
A company's marketing communication and the opinion of a specific engineer on GitHub or at a meetup work for different audiences in terms of trust level. A developer is accustomed to verifying facts — this is a professional deformation: he reads code, not advertising copy. A post by a technical lead about how CI/CD is organized in the company, or an open repository with internal tools, says more than ten pages about 'innovation culture'.
GitLab has released an open Remote Playbook with detailed documentation of processes — this is not a gesture of goodwill, but a way to show that remote work here is not a slogan, but a detailedly described process. Linear protects deep work not with a declaration, but with the architecture of the product itself and internal regulations without meaningless calls. Such companies do not talk about EVP — they give it a try before the interview, and this works better than any slogan.
Junior, middle, senior: three different labor markets within one vacancy
The mistake of most IT HR strategies — trying to write one vacancy text and one hiring process for all levels. In practice, this is three different markets with reverse demand and supply dynamics.
| Grade | Competition for the vacancy | Key motivation | What works in attraction |
|---|---|---|---|
| Junior | 18–32 resumes for the vacancy | Stability, training, mentor | Mentorship programs, clear growth trajectory, internships |
| Middle | 14–15 resumes for the vacancy | Interesting tasks, no ceiling | Project rotation, technical freedom, transparent grading |
| Senior | around 3 resumes per vacancy | Influence on architecture, expert recognition | Personal contact with CTO, participation in conferences, referral networks |
The deficit at the senior level means that a standard test assignment with a deadline is more likely to repel such a candidate than to select them: he perceives this as a lack of trust in his expertise. For juniors, on the contrary, a test assignment is part of the expected process, while the absence of mentoring after hiring quickly leads to disappointment and departure in the first few months.
What developers actually check and what others check
A traditional candidate looks at salary, office, and benefits package. A developer adds to this a list of technical criteria that for HR often remain a blind spot:
- Technology stack and how outdated or relevant it is;
- Code review practice — is it formal or does it actually influence code quality;
- Presence of an open technical blog or public appearances by employees;
- Flexibility of remote work: developers highly value the opportunity for remote work and are ready to change employers over its loss;
- Real, not declarative, access to learning — in the style of the Google program, where employees could spend 20% of their working time on personal projects, from which Gmail and Google News were born.
The approach differs fundamentally: a benefits package can be described in text, but engineering culture has to be shown through artifacts — open code, process metrics, recordings of internal talks. Words weigh almost nothing here.
Active recruiting versus waiting for responses
Passive waiting for responses to a vacancy in 2024 year is a slow death of hiring senior and some middle specialists, because they are less likely to be in active job search. Active recruiting with direct outreach to passive candidates reduces time-to-hire to 14–21 days against months of waiting with a passive strategy.
Tinkoff actively develops IT communities and holds technical meetups as part of its candidate attraction strategy — the company meets developers well before a vacancy appears. Yandex increased responses to vacancies by 2,5 times thanks to personalized vacancy matching via an ML algorithm in email newsletters. Both examples share one thing in common: recruitment here does not react to a vacancy, but builds relationships in advance.
Signals that a developer is ready to leave
Staff turnover in IT rarely happens suddenly — usually there are three to four months of signals that the team simply does not read as warning signs.
- Decline in scores in regular pulse surveys — often the first and earliest marker;
- Overtime exceeding norm by more than 20% without compensation or acknowledgment;
- Drop in activity during code reviews — the developer stops investing in the quality of others' code;
- Lack of requests for internal growth, rotation, or new projects.
Working with these signals requires a targeted approach: a conversation with a manager, not a general HR newsletter about well-being. Additional complexity 2024–2025 years — blurring of grades due to AI: developers note the impact of AI on the nature of their work: there is a need for verification and context management with models instead of direct code creation. This changes the motivation for retaining seniors — they need a new field for expertise, not just a salary increase.
In summary: EVP needs to be verified, not declared
PostHog, GitLab and Linear built their HR brand not on formulations, but on verifiable artifacts: open source code, public metrics, and documented processes. For the Russian market, this means a concrete thing — a talent bank and meetups work better than job postings, personalization is many times more effective than mass mailing, and the difference in approach to junior, middle and senior levels should be embedded in the recruitment funnel from the very beginning, not appear as an exception for 'difficult' candidates.
Why an employee convinces better than the 'Careers' page
A company's marketing communication and the opinion of a specific engineer on GitHub or at a meetup work for different audiences in terms of trust level. A developer is accustomed to verifying facts — this is a professional deformation: he reads code, not advertising copy. A post by a technical lead about how CI/CD is organized in the company, or an open repository with internal tools, says more than ten pages about 'innovation culture'.
GitLab has released an open Remote Playbook with detailed documentation of processes — this is not a gesture of goodwill, but a way to show that remote work here is not a slogan, but a detailedly described process. Linear protects deep work not with a declaration, but with the architecture of the product itself and internal regulations without meaningless calls. Such companies do not talk about EVP — they give it a try before the interview, and this works better than any slogan.
Junior, middle, senior: three different labor markets within one vacancy
The mistake of most IT HR strategies — trying to write one vacancy text and one hiring process for all levels. In practice, this is three different markets with reverse demand and supply dynamics.
| Grade | Competition for the vacancy | Key motivation | What works in attraction |
|---|---|---|---|
| Junior | 18–32 resumes for the vacancy | Stability, training, mentor | Mentorship programs, clear growth trajectory, internships |
| Middle | 14–15 resumes for the vacancy | Interesting tasks, no ceiling | Project rotation, technical freedom, transparent grading |
| Senior | around 3 resumes per vacancy | Influence on architecture, expert recognition | Personal contact with CTO, participation in conferences, referral networks |
The deficit at the senior level means that a standard test assignment with a deadline is more likely to repel such a candidate than to select them: he perceives this as a lack of trust in his expertise. For juniors, on the contrary, a test assignment is part of the expected process, while the absence of mentoring after hiring quickly leads to disappointment and departure in the first few months.
What developers actually check and what others check
A traditional candidate looks at salary, office, and benefits package. A developer adds to this a list of technical criteria that for HR often remain a blind spot:
- Technology stack and how outdated or relevant it is;
- Code review practice — is it formal or does it actually influence code quality;
- Presence of an open technical blog or public appearances by employees;
- Flexibility of remote work: developers highly value the opportunity for remote work and are ready to change employers over its loss;
- Real, not declarative, access to learning — in the style of the Google program, where employees could spend 20% of their working time on personal projects, from which Gmail and Google News were born.
The approach differs fundamentally: a benefits package can be described in text, but engineering culture has to be shown through artifacts — open code, process metrics, recordings of internal talks. Words weigh almost nothing here.
Active recruiting versus waiting for responses
Passive waiting for responses to a vacancy in 2024 year is a slow death of hiring senior and some middle specialists, because they are less likely to be in active job search. Active recruiting with direct outreach to passive candidates reduces time-to-hire to 14–21 days against months of waiting with a passive strategy.
Tinkoff actively develops IT communities and holds technical meetups as part of its candidate attraction strategy — the company meets developers well before a vacancy appears. Yandex increased responses to vacancies by 2,5 times thanks to personalized vacancy matching via an ML algorithm in email newsletters. Both examples share one thing in common: recruitment here does not react to a vacancy, but builds relationships in advance.
Signals that a developer is ready to leave
Staff turnover in IT rarely happens suddenly — usually there are three to four months of signals that the team simply does not read as warning signs.
- Decline in scores in regular pulse surveys — often the first and earliest marker;
- Overtime exceeding norm by more than 20% without compensation or acknowledgment;
- Drop in activity during code reviews — the developer stops investing in the quality of others' code;
- Lack of requests for internal growth, rotation, or new projects.
Working with these signals requires a targeted approach: a conversation with a manager, not a general HR newsletter about well-being. Additional complexity 2024–2025 years — blurring of grades due to AI: developers note the impact of AI on the nature of their work: there is a need for verification and context management with models instead of direct code creation. This changes the motivation for retaining seniors — they need a new field for expertise, not just a salary increase.
In summary: EVP needs to be verified, not declared
PostHog, GitLab and Linear built their HR brand not on formulations, but on verifiable artifacts: open source code, public metrics, and documented processes. For the Russian market, this means a concrete thing — a talent bank and meetups work better than job postings, personalization is many times more effective than mass mailing, and the difference in approach to junior, middle and senior levels should be embedded in the recruitment funnel from the very beginning, not appear as an exception for 'difficult' candidates.
Recent articles
MegaFon, BMW, VTB and more 240+ companies. See how it looks in the showcase reel:
Our branding agency is approached to order:
Branding agency services
