What: Nearly everyone in tech has to take part in a technical interview during their career, but are we doing them right?

Why: Creating a better technical interview can not only get you better candidates, but save time and money in the long run! You’ll also be putting a little bit less stress into the world.

Rough talk outline:

• Why do technical interview suck?
• What do we actually want to find?
• A skilled coder
• …Who gels with the team
• …Who works well under pressure
• …Who is the ‘best’ person for the job
• …While not wasting a ton of time or money
• For each attribute, we go over:
• How are we testing for it?
• What do these tests actually get us?
• How could we improve these tests to get better results?

Who will benefit from this talk: Practically any developer who is in the industry long enough will eventually be asked to take part in running a technical interview, whether it’s helping craft the questions or creating the whole thing from scratch and running it. Not only will they benefit from a better tech interview process, the people they interview will benefit too.