One of the oldest jokes in tech is that our three biggest problems are naming things and off-by-one errors. If that's still true, the fourth major problem might be interviews. With no industry standard approach or format, the ways to conduct and prepare for an interview for a technical position can vary dramatically, to such an extent that a search for "technical interview" books online can return over 1,000 results. This talk will cover the various approaches I've seen from a developer's perspective on both sides of the interviewing table at various points over the course of 20 years and will encourage discussion from the attendees about good, bad, and ugly experiences with different tactics. Participants can expect to leave with exposure to different viewpoints from fellow tech workers, the benefit of lessons learned without having to learn everything through the painful experience of the worst interviews ever, and maybe a couple of book recommendations or a new way to solve FizzBuzz.