Beyond the Brain Teaser: Technical Interviewing with RESPECT
"How would you move Mount Fuji?"
Great question, but does an engineer need to know the answer in order to write great code? No? I don't think so either.
The technical interview is one of the most controversial, challenging, and stressful parts of an engineer's career. The more senior the engineering position, the less relevant the brain teasers, algorithm quizzes, and puzzles that make up these interviews are to the evaluation of a potential candidate. And although this interview style first became famous at large tech corporations like Microsoft and Google, it has propagated across the industry to the point that courses are springing up in college campuses and bootcamps showing candidates exactly how to "crack" these interviews.
In the past, I’ve worked at a number of companies as a lead developer and in that role I spent a lot of time interviewing folks for technical positions. We weren’t allowed to choose our own process and had to follow the company’s rules. In that time I learned a lot about what works, and what doesn't work, for judging technical aptitude in an interview setting.
In this presentation I will talk about the difficulties of technical interviewing from both the interviewee and interviewer's point of view, and provide several helpful tools using the acronym RESPECT to improve the interviewing experience across the board.
Outline/Structure of the Talk
- A Sample Problem
- My First Technical Interview and Other Stories
- Benefits and Drawbacks of Technical Interviewing
- The RESPECT Process and How To Apply It Without "Lowering The Bar"
- (R)eal Solutions
- (E)arned Trust
After attending this talk, attendees will have a grasp on a new way of approaching evaluation of technical candidates and be able to apply the principles discussed during their own candidate interview cycles.
Engineers, Managers, HR Professionals
Prerequisites for Attendees