Rethinking the Technical Interview

The Problem with Technical Interviews

In this section, the speaker discusses the issues with technical interviews and how they are usually conducted.

Technical Interviews Today

• Most technical interviews involve asking random code questions that are algorithm-heavy and don't teach much about the candidate's abilities.

• Companies use these types of interviews because it's an easy default that has existed for a long time, not necessarily because it identifies quality engineers.

• The interview culture says a lot about the type of company you'll be working at if you get that job.

Proposing a New Model

• The speaker proposes giving more agency to the interviewee during the interview process to set them up for success in their role.

• Before the interview, candidates receive a document detailing multiple options on how the interview can go and what they can expect. This helps prevent them from being caught off guard by unexpected questions or curveballs.

A Different Approach

• The goal of this approach is not to challenge candidates with difficult coding problems but rather to give them an opportunity to showcase their skills in a way that aligns with what they will be doing on the job.

• This approach involves having candidates work on real-world problems or projects that simulate what they would be doing if hired.

• By using this approach, companies can better assess whether a candidate is a good fit for their team and culture while also providing valuable experience for the candidate.

Dan Abramov Interview

In this section, the speaker talks about his interview with Dan Abramov and the different types of technical interviews he offers.

Types of Technical Interviews

• The Traditionalist

• Everyday elite code problems that showcase technical skills.

• The Pragmatist

• Realistic code problems that test understanding of core concepts.

• Example problem given is the Pokedex problem.

• The Realist

• Allows interviewee to show how they work by fixing a bug or adding a feature to an existing project.

• A pairing exercise is done during the interview.

Technical Interview for Dan Abramov

• Since Dan is a strong open source contributor, a technical interview was not necessary in real life.

• However, since he wanted to showcase what it looks like to interview someone on the core team of React and creator of Redux, they decided to do a more technical interview.

Tips for Technical Interviews

In this section, the speaker provides tips for technical interviews and emphasizes the importance of showcasing skills in a way that makes the interviewee feel confident.

Showcasing Skills

• There are better ways to showcase skills than what is typically listed on resumes.

• Interviewees should show their skills by demonstrating them or providing examples.

• The interviewer wants to see how an interviewee thinks and works, so it's important to showcase technical abilities in a way that makes the interviewee feel confident.

Take-Home Assignments

• The speaker is unsure about take-home assignments because some employees may not be able to justify spending free time working on them without being paid.

• However, if an interviewee prefers a take-home assignment, one can be provided.

Additional Tips

• Interviewees should do more interviews and participate in both sides of the process (as an interviewer and as an interviewee).

• Being involved in the interview process helps individuals understand where they fit on a team and how valuable they are.

• Giving feedback to candidates after interviews helps them improve for future opportunities.

Conclusion

The speaker encourages rejecting candidates with feedback and emphasizes that being involved in the interview process can help individuals grow professionally.

Importance of a Good Interview Process

In this section, the speaker emphasizes the importance of having a good interview process to attract and retain quality engineers.

The Impact of a Poor Interview Process

• A poor interview process can lead to losing potential candidates who feel disrespected.

• A company's best engineer is only as good as their interview process.

• If a company's interview process is limiting, it will limit the quality of engineering at that company.

The Importance of a Good Interview Process

• A good interview process attracts quality engineers and helps retain them.

• If you have a process that makes good engineers, word will spread and more people will be excited to recommend engineers to work for your company.

Additional Information

• The speaker offers to share a video of him using his interview process to interview someone named Dan.