Recruiters TechCamp (QA)


Recruiters Pain in 2018:
А вот и наш первый спикер по направлению QA - Anthony A. Muzhailo
У него отлично развит навык преподавателя, его интересно слушать и задавать вопросы)
Мы разберем кто такие QA/QC/AQA, как среди огромного количества резюме свитчеров/junior определить действительно грамотного специалиста.
Обсудим тему как Technical Recruiter может провести первичную оценку кандидатов и какую QA терминологию/процессы нужно знать, как свои пять пальцев, что бы грамотно вести диалог на interview/pre-screening/неформальной обстановке.
ЗЫ: мы не говорим, что рекрутер должен проводить полностью собеседование с QA's, однако у Technical Recruiter обязательно должно быть базовое понимание сферы вакансии.

Transcript

1. Understanding Test Engineers Anton Muzhailo
2. About me in/muzhailo/
3. Who am I according to Linkedin messages? Test Engineer QA Engineer QC Engineer Tester Engineer in Test QA Tester Testing specialist Automation Engineer Software Developer in Test QA Automation Automation Tester Automotive specialist QA/QC Auto Engineer AQA Engineer
4. Who really can I be? Test Engineer QA Engineer QC Engineer Tester Engineer in Test QA Tester Testing specialist Automation Engineer Software Developer in Test QA Automation Automation Tester Automotive specialist QA/QC Auto Engineer AQA Engineer
5. What are my regular tasks during working day ▪ Emails (Q&A, discussion, clarification, notification etc) ▪ Meetings (same activities as Email) ▪ Making decisions based on income data (analysis) ▪ Planning, creating/explaining tasks for engineers ▪ Assisting engineers on their tasks / knowledge sharing ▪ Investigation, troubleshooting, finding a way out, dealing with unknown ▪ Coding / debugging
6. Test engineer’s skills Soft skills Domain or business Technology Software testing activities
7. People is the most often bottleneck ▪ More than 50% of all issues are because of bad communication ▪ Many projects failing because of trying to build processes before building the team ▪ We can fix tech issues by smarter frameworks and better computers, but we can’t fix people. ▪ It’s possible to learn the monkey to code, but you will never learn the monkey to be human
8. Soft skills >> Hard skills Skill Level Time A B C D E F G Skill Level Time A B C D E F G Strong technical but low soft skills Lower technical but strong soft skills
9. What are the soft skills? Ideal senior specialist should be able to: ▪ Learn (Ask to use some new framework with the help of Google) ▪ Share knowledge (Ask to tell something or write some documentation) ▪ Explain (Ask to proof his point of view with evidences and arguments) ▪ Negotiate (Ask to convince you on some hot topic, ie iOS vs Android) ▪ Review and be reviewed (Check reviewing skills on a prepared document) ▪ Separate work conflicts from personal (Ask the thoughts)
10. How do I react on proposals? ▪ No problems with wrong name, I was already called even by girl name ☺ ▪ I have an opinion about many companies based on job proposals received. ▪ I will always decline propositions that require an engineer to be chief cook and bottle washer at the same ▪ I respond only on those proposals on LinkedIn, which are correct and clear. So what’s the problem?
14. Which one looks interesting?