Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How To Interview And Why

How To Interview And Why

An interview too often feels like a first date - awkward, strange, and not entirely predictive of what’s to follow. There are countless books and websites to help you when you’re a job seeker, but what about when you’re the one doing the hiring? Will you just ask the same puzzle questions or sort algorithm problems? What are your metrics for evaluating or contextualizing the answers? In this talk, I’ll discuss successful practices and techniques to help you find someone who will innovate your business, bring new energy to your team, get the work done, AND be someone you’ll want to work with.

Kerri Miller

August 03, 2014
Tweet

More Decks by Kerri Miller

Other Decks in Programming

Transcript

  1. HOW TO BE AWESOME AT INTERVIEWING • Know What You’re

    Looking For • Find People Who Have It • Keep Improving Your Process Saturday, August 2, 14
  2. 1 KNOW WHAT Y O U ’ R E LOOKING

    FOR Saturday, August 2, 14
  3. DEFINE YOUR CULTURE • Start the conversation early • Refuse

    to accept vagueness • Generate “Belief/Therefor” statements Saturday, August 2, 14
  4. "WE BELIEVE IN RESPECT, THEREFORE WE WILL SHOW UP ON

    TIME FOR ALL MEETINGS." Saturday, August 2, 14
  5. TYPICAL HIRING PROCESS 1) Job posted 2) Resumé and/or code

    samples reviewed 3) Initial phone screen(s) 4) Technical phone screen(s) 5) Interview Saturday, August 2, 14
  6. INTERVIEW DAY! • Have a schedule • Set expectations •

    Make an effort to have diverse interviewers • Allow for breaks Saturday, August 2, 14
  7. MAKE A GAME PLAN • Assign different areas of focus

    for each interviewer • Have a hand-off system • Create 3-5 questions for each interviewer to ask • Record impressions immediately after interview Saturday, August 2, 14
  8. SETTLING IN • Start with a simple conversation • Ease

    candidates into process • Double-check for red flags • Learn how they communicate Saturday, August 2, 14
  9. BEHAVIORAL INTERVIEWING • Hypothetical questions are game-able • Ask for

    the story of specific situations • Keep in mind they want to get hired! Saturday, August 2, 14
  10. COLLABORATION AUDITION • Plan an app • Focus on high-level

    design • Jr - simple MVC app • Mid/Sr - OO game • Sr/Lead - distributed API Saturday, August 2, 14
  11. PAIRING AUDITION • Not everyone pairs • Let them use

    their setup • Pick a kata, Ruby quiz, or open source project you’re both familiar (but not intimate) with Saturday, August 2, 14
  12. PRESENTATION AUDITION • Have candidate teach you something • It

    needn't be technical • Set clear expectations about length, format, and investment of time Saturday, August 2, 14
  13. AFTER THE INTERVIEW • Gather all feedback, then discuss as

    a group • Find a consensus • Follow-up interviews can be problematic • Set candidate expectations for response and meet them Saturday, August 2, 14
  14. • Don’t say why, call out deficiencies, or make it

    personal • Be respectful • Explain potential for reapplication (if any) • Be cautious with follow-up HANDLING REJECTION Saturday, August 2, 14
  15. GPA, SAT, GRE • GPA useless after 2-3 years •

    More interesting to see what was studied than test results • SAT and GRE are for judging academic performance only • High School transcripts = LOL Saturday, August 2, 14
  16. “NEGGING” • “You’re not qualified for this job -- I’m

    not sure how you got this interview” • “You’re qualified but I’m not feeling a spark. Convince me you’re the right person for this job.” Saturday, August 2, 14
  17. “SUBMIT A PR TO APPLY” • What about the well-

    documented barriers to OSS? • You’re asking for free work for the CHANCE of a job • Many people can’t tip their hand that they’re looking for new employment Saturday, August 2, 14
  18. GROUP/SPEED INTERVIEWS • Disrespectful of individuals • Filters for people

    who can attract your attention Saturday, August 2, 14
  19. PUZZLE QUESTIONS • Google on puzzle questions: “a complete waste

    of time” • Filter for people who have the same context as you • Only serve to make you feel smart Saturday, August 2, 14
  20. WHITEBOARD CODING • It is artificial to code by writing

    on the wall • Adversarial rather than collaborative Saturday, August 2, 14
  21. FIZZBUZZ • At best: a time waster • At worst:

    an insult Saturday, August 2, 14
  22. WE IMPROVE WHAT WE MEASURE • Register predictions ahead of

    time • Discover your biases • Keep tabs on people you turn down Saturday, August 2, 14
  23. KERRI MILLER (@KERRIZOR) • glass artist • Vespa mechanic •

    lighting designer • author & teacher • player of games • software developer Saturday, August 2, 14