A pair programming interview is a technical format where you and an engineer write code together on a shared problem, usually in a real editor and a realistic codebase. The interviewer acts as a collaborator rather than a silent observer, and the evaluation weighs communication, use of feedback and debugging habits as heavily as the finished solution. Sessions typically run 60 to 90 minutes.
What Pair Programming Interview means in practice
Formats range from a strict driver and navigator split, where one person types while the other directs, to a looser session where the interviewer answers questions and occasionally suggests a direction. Many companies use a small realistic repository, sometimes their own product, with tests already in place and a task such as fixing a failing test, adding a feature or extending a module. You usually work in your own environment or a prepared cloud editor, with documentation and search allowed, because the point is to simulate ordinary work. It is common at companies that dislike puzzle formats, and it typically sits after a technical phone screen.
Why it matters for candidates
Silence is the most common way to fail this format even when the code works. The interviewer is grading collaboration: whether you narrate your reasoning, ask clarifying questions, take a suggestion without ego and push back with reasons when you disagree. It also rewards everyday professional habits that puzzle formats ignore, such as reading the existing code first, running the tests early and moving in small verified steps.
How to prepare
- Narrate your reasoning continuously, including the dead ends.
- Read the existing code and tests before writing anything.
- Ask clarifying questions instead of assuming the requirement.
- Take suggestions gracefully and explain why when you disagree.
- Run the tests early and often rather than only at the end.
Example
A candidate is given a small Python repository with one failing test and 75 minutes. They spend the first eight minutes reading the module and asking what the intended behavior is, then write a narrower failing test to pin the bug down. Halfway through, the interviewer suggests a different data structure; the candidate tries it, finds it slower for this access pattern, and explains the trade-off before choosing. The bug is fixed with 20 minutes left, which they spend on edge cases.
Know the format. Now know the questions. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questionsRelated terms
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it works