Then you are not gonna do well in any interview or team setting; which basically disqualifies you from working in this field unless it’s open source or something.
Pair programming is quite rare in most orgs. Most code is discussed async after its been written. A take home test where you modify some existing code based on new business requirements would be far more similar to the real job. LIVE Discussion about the requirements before or code after would also be similar.
Most interviews involve either pair programming or whiteboard problems. Not being able to think when being watched is not gonna cut it.
Interviewers all seem to state the problem and then let me work quietly between a few clarifying questions. My impression of pairing is a lot more talking with no time to start thinking.
What on earth are you talking about? I’ve been in the industry a really long time and have never seen anyone actually pair program. The entire concept of pair programming is silly. If anything it’s ear phones on and don’t bug me.
That's ridiculous; only once has this been asked during an interview.