Recruitment in IT — a case study from the Full Stack Developer search in TEONITE software house

Paulina Maludy
teonite
Published in
3 min readAug 7, 2018

→ Check our BLOG
→ Follow us on:
Facebook, Twitter, Instagram, LinkedIn

At the beginning, I would like to point out that I am not an HR specialist — for several years I have been active in the field of marketing and until now the topic of recruitment in IT was foreign to me. Therefore, the more I am happy that today I can present you my first case study on searching for the right person for TEONITE team.

Read full article HERE

Why the Full Stack Developer?

Before proceeding to the analysis of the recruitment process, let me explain the definition of Full Stack. I will use the description founded on the Quora portal during research for this case study:

Source Quora

The above definition clearly shows why the only matching term for the person we were looking for was “Full Stack Developer”. We chose this position mainly due to its commonly accepted competences, but also to:

“Being a full-stack developer is constantly learning new skills”.

Why? Because TEONITE core is made with people who constantly gain new skills and work in frontend and backend technologies, but also in data science and machine learning.

Is content always the most important thing?

The original version of the job advertisement

After reviewing several case studies and guides, I wrote a “standard” advertisement based on the form: who we are looking for, what skills we require, what we offer, etc. Despite the correctness of this version and the use of the most common promotional activities (list HERE).

…the announcement did not result in the inflow of a CVs.

Metamorphosis of content

We wanted to know what did not work. We analyzed the first version of the text and we came to the conclusion that perhaps these “standard” announcements simply do not match us. So:

  1. I changed the content and translated the components into our language, adding a bit more information about “our work philosophy”.
  2. I published (on Facebook groups dedicated to developers) a much less formal version, creating something like “anti-offer”

Check how number 1 and 2 looked like HERE.

Small change, big effect

We thought that maybe content is not the problem here? That’s why we decided to do more radical change — we split the Full Stack position into JavaScript and Python Developer. The whole was supported by the same promotional actions and … the effect was immediate — the first applications started to arrive on the first day of the publication!

Why? Read the whole article HERE

--

--