From 0 to 100 in 3 months (HR Meetup Riga #11)

Challenge: speed, scale & quality. Software engineer lost in the hiring process will share an interesting case study from which everyone can benefit and make the World a better place. The story of the hiring process evolution will be shared during which he interviewed more than 100 candidates.

Transcript

1. From 0 to 100 in 3 months* A story of an engineer lost in the hiring process
 
 *a little bit longer, but I like number 3
2. Experienced Multifunctional Software Engineer Sergey Kibish https://sergeykibish.com sergey@kibish.com Skilled in different languages / tools / technologies. Strong engineering professional with a Master of Science (Mg.Sc.Comp.) focused in Computer Science. Natural-born leader, full of passion and charisma. A hobby is music in all of its manifestations (listening, playing, writing). @s_kibish
3. Motivation / Goal I really want you to think one more time about your interview process. Is it really good? Or you just do it, because you are a robot and don’t see any problems? After this talk you should have a will to change your interview process and how your view the candidates
4. Disclaimer
5. Disclaimer This is a rage talk. If I will swear, I’m sorry. I will try not to This talk is based on my personal experience. Something applied here might not work in your environment
6. Story time
7. Once upon a time, team of engineers was asked a question “Who want to help with interviews?” And only one hand raised up This was beginning of the end At some point it was like…
9. Facts • More than 200 interviews in total • More than 110 interviews done only by me • On average 12 interviews a week (it’s up to 4-5 interviews in some days) • Boys and Girls • From around the world • Online
10. Why • New big shiny project was on the horizon • Workforce was needed • Office in a new location was opened • Company committed to provide 200100 engineers before the end of this year
11. Recap Don’t sign contracts where is specified how many people you should provide. Success of your project is not about amount of people, but about quality of the work done
12. Interview process
13. In the beginning • Just check that person know something. General questions on understanding of things. • Interview — 1h long Agencies Interview Offer
14. Recap • Such scheme will work only if agencies invite people that are really what you expect (which is, obviously, impossible) • Interview process is short. People do not expect to get offer right away and they think that something is wrong here • Because interviews are simple, it is difficult to check that it is not a cheater in front of you • I started to burnout
15. In the middle • All from the beginning • Additional team members started to participate in the interviews from time to time
16. In the middle
17. In the middle • All from the beginning • Additional team members started to participate in the interviews from time to time • Classification
18. Classification • Junior • Middle • Senior
19. Classification • Overall technical impression • Junior — fluent in terminology • Middle — depth of knowledge • Senior — T-shaped knowledge, architectural intuition
20. Classification • Self-sufficiency • Junior — requires help from teammates • Middle — independent • Senior — independent and can guide teammates
21. Recap • Classify your candidates • Create framework with questions • Send candidate profiles (avatars) to the agencies • Still getting a lot of candidates that do not fit our expectations
22. In the middle-2 • All from the middle • Added “code review” and “open ended” questions Agencies Interview Offer Internal CV screening
23. Code review
24. Open-ended • What do you love/hate about [technology]? • You’ve implemented a feature. How you will make sure, that it is working as expected?
25. Recap • Less false positives with the candidates • Cheaters are recognised better • Problem to figure out seniority
26. Current state Agencies Interview Offer Internal CV screening Homework Review Interview 2
27. Homework • Should be something simple and connected with your domain in some sense. Should be real and not an algorithmic quiz. • Mandatory and additional requirements • Deadline is set by the candidate • Discuss homework on the second interview
29. Recap • Have a list of requirements for yourself — what do you expect from the candidate. Create avatar • Don’t send junk info to agencies • Tell candidate about your hiring process (respect time) • Homework is only for seniors • Timing: less than a week • Live coding interviews don’t work
30. Candidate
31. Candidate • Know the language in which you will speak • Check that your hardware / software is working before the interview • Refresh some fundamental knowledge (always good) • Talk. We don’t have ability to read your mind
32. Resume • Don’t include personal information like: • Birthday • Marital status • Gender • GDPR
33. Resume (Engineers) • Don’t include information like: • List of technologies • Tell, what you did. Add numbers. • Tell what you really want and how you can be helpful • Make your resume interesting (not Europass or simple black on white) • Add references
34. Recap • Be prepared to the interview; refresh some basic knowledge • Think about your resume from point of recruiter. What you want them to see in it?
35. Interviewer
36. Interviewer • Listen to your candidate • Help your candidate • Make your candidate feel safe and comfortable • Create natural conversation • Don’t be aggressive • Don’t ask candidate to introduce themselves • Don’t use Skype
37. Summary
38. Summary • Interviews are not simple • They kill your engineers • Learn to listen • Create framework • Keep your mind cold • Respect
39. Questions
40. sergey@kibish.com
 @s_kibish It’s time to get in touch