Let's look at this from another POV: given your predisposition, you're likely doing a disservice to the employer. They certainly don't want to hire someone who "hates" one of their development practices. Have you informed them of your perspective given such a tight-collaborative environment? If not, you're potentially misrepresenting yourself.
As an employer, I would be pretty frustrated to hire someone who knew, coming in, that they wouldn't be happy with the development practices we had put into place. It's a recipe for discontentment and frustration for everyone involved.
Edit Given that they understand where you're coming from (and are willing to take you on, as you mentioned in your comment), why not discuss how you feel with a few developers in the company? It's possible they'll be able to address any concerns or biases you have against PP. It's also important for them to know you're not terribly keen on the idea since you'll be working with them full-time.
It will also give you an opportunity to learn something about the people you'll be working with so closely.
If everyone is on board, I would certainly advocate PP for the same reasons mentioned in the answers here. You have immediate accountability for what you're writing; another set of eyes on your code will likely catch defects or trouble-spots you might otherwise miss; you get great exposure to someone else's perspective on coding (and get to provide your own experience); and the end result is very often much better than you would expect.
I appreciate your bias against PP; there are times I want nothing more than to sit at a computer banging away at a problem, and PP gets frustrating (I'm also an introvert, which means PP leaves me feeling a bit more drained at the end of the day) because someone is always there. This said, the results, in my experience, speak for themselves and I'm much more amicable to it on a regular basis.