I love pairing. It is the right thing for me, and I work in a company that has pairing in its core culture. Feeling that pair programming isn't the thing for you is your choice and it probably works out well for you, but you wouldn't be hired by my organaization, or Braintree. That's the point that the blog post tries to make while also talking about virtues of pair programming. Not that it is for everyone and anyone who doesn't do it is foolish.
Yes, I definitely wouldn't work for a company that has pair programming in its core culture. I also wouldn't work for a company that has standing desks in its core culture, or Perl programming in its core culture, or Emacs or vi in its core culture. In fact, I avoid monoculture as much as I can, because it stifles innovation by reducing diversity.