Creating a Technical Interview that Doesn't Suck
A Meetup Talk by Brooks Patton
But First...Who Am I?
Technical Team Lead at Health Scholars
Worked in the IT industry for over 14 years
Including contracting at NASA as a systems administrator
Live-coding projects and fun visualizations on Twitch.tv
Objectives
- Determine what you are really looking for in a new hire
- Create a code challenge that is fun and informative
- Run a technical interview and answer if this candidate is someone you want to hire (technically)
Before we get started
Determine what you are really looking for in a new hire
Determine what you are really looking for in a new hire
Specific Problem
General Problem
- Devops
- Scaler
- Mentor
- ...
- You have more important things to do than you have time to do them
Determine what you are really looking for in a new hire
We rarely have specific problems that require a specialist
Determine what you are really looking for in a new hire
Create a code challenge that is fun and informative
Create a code challenge that is fun and informative
Create a code challenge that is fun and informative
Create a code challenge that is fun and informative
Create a code challenge that is fun and informative
Create a code challenge that is fun and informative
Rubric
- willing to ask for help
- takes feedback
- describes closures
- solved 3 or more problems
Run a technical interview and answer if this candidate is someone you want to hire (technically)
Recap
- Determine what you are really looking for in a new hire
- Create a code challenge that is fun and informative
- Run a technical interview and answer if this candidate is someone you want to hire (technically)
Contact me at
twitch.tv/brookzerker
github.com/brookspatton
twitter.com/brooks_patton