The power of two: Using pair programming to improve technical interviews

As the name suggests, pair programming is a technique which requires two people to code together. They are termed as Driver and Navigator. One writes the code and the other evaluates each line of code and suggests changes or identifies problems in real time. The roles may be exchanged at any point, and the two regularly interact to guarantee the code is of high quality and fits the required criteria.

Pair programming is an Agile development method originating from Extreme Programming (XP) and is usually used in software development to accelerate delivery. It is also known as yin-yang programming, doer-checker or active-passive programming.

The same method can be adapted to tech hiring to help hiring managers better understand how applicants work, communicate, and solve problems in groups. By viewing the code, managers can analyze candidates’ technical skills, communication skills, problem-solving ability, and attitude to challenging jobs.

Pair programming assists engineering managers in better understanding how candidates think, learn, and process information. Managers can acquire significant insights into how a candidate approaches and solves real-world coding difficulties by working together on a coding problem.

Pair programming can be used for technical interviews by teaming an applicant with an interviewer to write code in real-time. This way the interviewer can assess the developer’s code-writing capabilities and accuracy in a familiar environment.

The candidate and interviewer collaborate on a coding challenge or a real-world programming task. As the applicant codes, the interviewer navigates, giving directions and comments. This is a great way to assess how applicants describe their methods and assumptions while verbally communicating their thinking and reasoning.

Engineering managers need to prepare for pair programming interviews by selecting a problem to collaborate on. This problem could be a fresh question, or something that is half-written and needs extension. Or, this could be a take-home assignment the candidate wrote which the interviewer can build on top of.

The aim of the process is to have a problem with a scalable solution, and then assess the candidate’s ability to re-think their original solution when presented with such a problem.

Writing code is a complex process requiring a lot of collaboration. Many times, a developer might be asked to work on a project midway or help a peer with their task. If they are not able to pick up the code midway and add to it or review it and find ways to improve, then they may not be the best fit for a team that relies on close collaboration to get things done. Therefore, conducting a pair programming interview gives an engineering manager a clear picture of a candidate’s potential performance in such situations

Here are some reasons why you should include pair programming as an interview technique

The interviewer can start as the navigator, providing comments and ideas to the driver as they work through the challenge. In addition, they might suggest alternative approaches to solving the problem or point out errors in the code. The interviewer can observe how the applicant responds to feedback or comments through this process.

A candidate open to feedback and prepared to investigate various problem-solving ways is more likely to accept constructive criticism well. They may ask clarifying questions about the comments they are receiving and collaborate with the interviewer to find a solution.

When the roles are reversed and the candidate has to act as navigator, the way they communicate and provide feedback can tell you a lot about their leadership style, and how well-suited they are to guide and mentor others.

Theoretically, pair programming interviews sound like a hoot! However, it is important to be strategic and avoid hindrances during the interview. We asked our in-house tech experts to help us out with the best techniques to conduct pair programming interviews, and here is what they said:

Hiring the right developer for an organization needs mindfulness and strategy. No matter how well an engineering manager plans a tech interview, certain things can slip through the gaps. Use the best practices outlined below to conduct a pair programming interview and never leave any loophole during tech hiring.

Thus, pair programming during interviews may help assess candidates’ coding prowess and collaborative abilities. Yet, considering the elements above is crucial to a successful interview process.

Evaluating pair programming interviews involves assessing the candidate’s coding ability, communication and collaboration skills, problem-solving approach, and overall fit for the role. Here are some ways to evaluate pair programming interviews:

Evaluating pair programming interviews involves assessing the candidate’s coding ability, communication and collaboration skills, problem-solving approach, and overall fit for the role.

Here are some ways to evaluate pair programming interviews:

Here are a few pointers to help you manage your time

1.Choose a problem statement that allows the interviewer to evaluate the candidate’s work in multiple parts. You can also use a problem that needs to be solved at an increasing level of complexity to understand the candidate’s competency level.

2.Drive the conversation/interview in a manner so that solving for the first case will automatically lead to the second case, and so on.

3.Take care that there is some atomicity in the way the solution needs to be written. For example: a DB optimization problem should be separate from a business logic change problem. This way, you can always move on to the next challenge if time is running out.