Interviewing
-
Tech Interviews
-
Behavioural Interviews
-
Biases
Tech Interviews
Figure out The Problem Need
Test Task
vs
Pair Coding
Funnel Optimisations
Algorithms
vs
Open Tasks
Algorithms
vs
Open Tasks
Skill Level Optimisation
Codebase access
vs
Vague Requirements
Learning Curve Assessment
Hints
vs
Answering Questions
Communications Assessment
Role Specific Tasks
Interviewer's How-To
No Stress
Facilitate Questions
Give hints if stuck
Do not mislead
IDE / Coding style/ Language
do not matter (if not specified)
Manage expectations
Interviewee's How-To
Production-ready code (if not specified)
Don't use unfamiliar tools
State your assumptions
Explain your decisions
Read Cracking the Coding Interview
-
Tech Interviews
-
Behavioural Interviews
-
Biases
Behavioural Interviews
Structured interview
Competency-based
Performance-based
Figure 5-7 basic competencies
We want to have AND we have right now
Question Structure
Don't: "what if" and "would be" sentences!
Do: "Give me an example" and "describe".
Validity
2 interviewers to mitigate biases
Standardised Rating Matrix
Written Report for records
Interviewer's How-To
No Stress
Manage expectations
-
timeframe
-
interview type
-
number of questions
Be aware about your biases
Don't interrupt
Focus on most recent experience
Interviewee's How-To
Use STAR format
Situation - Task - Action - Result
You cannot cheat
Use examples from
various areas of your life
Explain details and
what you've learned
-
Tech Interviews
-
Behavioural Interviews
-
Biases
Biases
First 30 seconds
You have made your decision. Now what?
Stress Revenge
Performance under stress is not a reliable indicator
Examination
Knowledge != skills != experience
Discrimination
Mind your own tendencies
Confirmation Bias
We tend to agree and like people who agree with us. Opposite is true as well.
Negativity Bias
Paying more attention to negative things
Halo effect
Positive or negative traits get projected on other areas
Thanks!
Take Aways
Interviewing
By Alexey Migutsky
Interviewing
- 2,336