2. Screening CV’s
• Dates Matter –
look for gaps.
Does the candidate change jobs too often?
• You're not sure ? Call him. Don’t waste your
and hisher time.
3. Before the interview
• Read the CV before and not during the
interview.
• Look for web fingerprints - Does he write
blog? Does he asks questions on forums? Does
the LinkedIn profile matches the CV?
• Make notes - questions about the CV’S
(specific for the candidate- experience, dates
and so on)
• Prepare paper for scratching stuff.
4. During the interview
1. Trailer
• Company-> Department-> team -> job.
you’re being interviewed! Sell the job.
• Introduce yourself -
5. During the interview
2. Tell me a little about yourself
• let him role.
Stop for questions (open vs. closed – “Do you
know Node.js? –Yes”.
Act as traffic officer.
Create intimacy – what’s your hobbies?
6. During the interview
3. Dig for history
1. Tell me about your current project.
2. Tell me about a failed projectcoding.
3. Tell me about a succeed projectcoding.
Use the STAR questions- situation, task, actions and
results.
• What was the background of what you were working
on?
• What tasks were you given?
• What actions did you take?
• What results did you measure?
7. During the interview
4. Rules
• 80/20 rule- talk about 20 percent of the time.
• pastpresentfuture – know what you need to know
• Respect- Give time to answer questions, don’t
interrupt.
• There are no stupid questions.
• Go deep- The WHY method. Ask why until you dive
enough.
• Once you form an initial impression of someone -
which usually happens within the first 60 seconds - you
should spend the rest the interview trying to invalidate
that impression.
8. During the interview
5. Tech questions
• For each open position create set of tech
questions.
• Force to write code
• Best screening question – real life question.
9. After the interview
• The beer test – will you drink beer with him?
• The car test- will you ride with this man for 5
hours straight?
• Write your thoughts- time has effect on
impression.
• Maybe means No.
