If pairing periodically is enough of a burden on you that it would cause you to interview elsewhere, it really seems like you're overthinking the impact.
These are the questions that periodic pairing answers with the lowest possible negative impact to members time.
Now, if you get into an environment that is 100% pairing all the time, or two people at the keyboard taking turns with an egg timer, etc...that can be a huge pain and I'd totally understand not wanting any part of it.
Watching somebody code while you drink a cup of coffee at your desk and offering the occasional "you know, if you do such-n-such it will be a little cleaner" or "I think there's a function that already does what you're writing"...is pretty low-impact.
EDIT: I read through your comment history and see that you were with Pivotal. IIRC they are a pairing all the time shop (I seem to remember seeing a presentation at some point). I can completely understand how that would suck.
The perks of pairing are regularly unsticking stuck people, getting another set of eyes on a problem, learning from each others development habits as a side effect of doing your job. People tend to really overthink what is involved in pairing, turning it into some rigidly drilled type of exercise.
All that is needed to get most of the benefits is to fire up a screen share and verbally communicate while the main developer keeps working. Everything else falls into place. Even if it's just for a couple of hours here and there rather than "finish this entire story with this person" it's beneficial.
When people get stuck on something, it can become harder for them to focus. They'll start looking for alternatives like opening HN or Facebook, reading an article, etc. For a lot of people trying to prove themselves, asking for help isn't going to happen until it's too late and that makes it easy for people to work in their own little bubble.
If it's considered an interruption for you to screen share while the person continues to code, you're doing pairing wrong.