1. Ping-pong TDD
Partner A writes a failing test. Partner B makes it pass. Partner A writes the next test. This is the gold standard — it forces both engineers to think at the interface level and prevents implementation-first thinking.
2. Strong-style pairing
The rule: 'For an idea to go from your head into the computer, it must go through someone else's hands.' The navigator speaks at the intention level ('let's add a null check here'), and the driver implements. Swap every 25 minutes.
3. Backseat driver
The driver codes freely. The navigator only speaks when asked or when they see a bug. This is best for tasks where one person has significantly more context — it avoids the cognitive overhead of constant explanation.
When to use which pattern
New feature or architecture: Strong-style. Bug investigation: Backseat driver (let the expert drive). Test coverage: Ping-pong TDD. Onboarding a new engineer: Strong-style, then flip roles every 30 minutes so the new hire gets driver time early.