Somehow, over the years, although I’ve mostly been an IT manager, I’ve become something of a go-to person among HR and recruiting professionals. Probably because every manager needs to know how to hire the right specialists for their team.
For a few years now, I’ve been actively recommending the book “To Hire or Not to Hire?“ by Konstantin Borisov. It’s concise and very clear, covering most hiring-related topics in our field.
That said, there are a number of points that often don’t get the attention they deserve—and I’ve promised more than once in various discussions to eventually share my own approach. It seems that time has come.
I frequently hire employees, so I decided to share my experience on what I pay attention to. LinkedIn is the de facto leading global resource where people publish their CVs. Therefore, I will review resume formatting based on this resource.
There are countless guides and courses on how to properly format your LinkedIn page to get noticed and hired. I can’t say that there is only one right way. Instead, I’ll describe how I look at the profiles of people who catch my interest or potential candidates.
Let me emphasize that this is my personal opinion, based on three pillars:
Personal experience in hiring
Common sense
Advice from fellow recruiters, especially Tatsiana Malinouskaya, arguably the best recruiter I’ve ever worked with
So, let’s go step by step. Any profile consists of several sections, so let’s briefly discuss each.
In recent years I’ve been reading quite a lot about hiring specialists, and I find it interesting to look at the topic from both sides. I interview candidates myself, and I’m constantly trying to get better at it. At the same time, when reading books about hiring, I always try to recall how I was interviewed, how I behaved as a candidate, and what I liked or disliked about the people doing the hiring.
About a year ago, Alpina released a new book on IT recruitment. I wasn’t familiar with the author, Egor Yatsenko, but the reviews were generally quite positive, so it would have been a shame not to pick it up.
With this kind of literature, though, it’s always important to understand the qualifications of the “trainer.” Egor Yatsenko is the co-founder of the recruitment agency Wanted: Profi, which specializes in hiring for the IT sector. In addition, he’s well known as a frequent speaker at various industry conferences, regularly giving talks, and he’s also involved in teaching sourcing (a professional term that essentially means targeted candidate search across different platforms).
In our turbulent times, people change jobs much more frequently than they did in the relatively recent past. In the 1950s-60s in the US, many people would join a company for life—it was the norm. In the USSR, with its system, there were often entire dynasties working at the same place. Working at the same job for life was almost a family tradition for many—grandfather at the factory, father in the same place, and the grandson destined to follow.
The “family” approach to building a team has many advantages, and I must admit, I often grow attached to a team myself. However, modern careers are all about constant job changes and constant interviews. These days, every manager seems to pride themselves on the number of interviews they’ve conducted. It’s strange that the quality of these interviews is discussed far less often, even though it’s much more important (after all, conducting interviews is just part of a manager’s job in a growing company).
I’ve come across numerous articles and books on topics like “how to write the perfect resume” or “how to ace an interview” (including a book I previously mentioned, Résumé for a Million by my former colleagues). However, there’s far less information about how to conduct interviews properly. Personal experience shows that not everyone is good at it (since I go through various interviews quite often, and it helps me stay sharp).
And then, unexpectedly, I stumbled upon the book To Hire or Not to Hire? by Konstantin Borisov. It’s relatively short, but once I started reading, I couldn’t put it down. It’s honestly one of the best management books I’ve read in recent years. Practically no fluff—everything is to the point, with clear arguments. The book primarily focuses on how to interview developers in the IT industry, but most of the material is applicable to any interview and isn’t specifically tied to IT. I’m not sure where the author works, but the company is certainly lucky to have such an interviewer.
