Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RailsConf 2018: The Code-Free Developer Interview by Pete Holiday When it comes to evaluating candidates for software engineering roles, it's hard to keep up with the latest and greatest techniques. We know logic puzzles don't work. Writing pseudocode on a white board is so tired and cliche at this point that companies brag about not doing that. Teams have resorted to what seems like an obvious choice at first blush: just have the candidate write some code. This new trend may have some unintended consequences, though. In this talk, you'll learn how to design an interview process which allows you to evaluate candidates without making them code for you.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the presentation "The Code-Free Developer Interview" at RailsConf 2018, Pete Holiday discusses innovative interview techniques aimed at evaluating software engineering candidates without the traditional stress of coding tests. Holiday, a software engineering manager at CallRail, critiques existing methods such as whiteboarding, logic puzzles, and live coding, arguing that they often fail to reflect real work and can disadvantage certain candidates. Instead, he proposes a more conversational approach. **Key Points Discussed:** - **Ineffectiveness of Traditional Coding Interviews:** Holiday emphasizes that coding interviews, while well-intentioned, often don't replicate real-world scenarios and can cause undue stress for candidates. This leads to uneven assessments, especially for those with demanding schedules or less access to resources. - **Alternative Interview Techniques:** Instead of coding, Holiday suggests three main methods: - **Experience Digging:** Candidates discuss specific projects they've worked on, detailing their roles and the challenges faced. This allows interviewers to assess their thought processes and the practical applicability of their skills. - **Code Review Role Play:** Candidates review sample code, allowing interviewers to gauge their communication skills and understanding of coding standards. This method involves providing simplified code that highlights common issues without overwhelming candidates. - **Collaborative System Design:** This technique engages candidates in a brainstorming session where they collaboratively design a system. Holiday highlights that this method allows the interviewer to assess a candidate's problem-solving abilities, thought process, and comfort level within a technical discussion without the pressure of programming in real-time. - **General Interviewing Tips:** Key recommendations include defining what to look for in candidates beforehand, asking consistent questions, and practicing interviewing skills regularly to improve assessment quality. - **Conclusions:** Holiday concludes that reverting to coding tests can be acceptable as a temporary solution but strongly proposes transitioning away from these practices for a more effective, conversation-driven interviewing process. He believes that refining interview techniques can lead to higher-quality hires and improve candidates' perceptions of the company’s interview process. By prioritizing dialogue and practical experience over stressful coding tasks, companies can foster a more inclusive and effective hiring process, ultimately benefiting all parties involved.
Suggest modifications
Cancel
