Of course it's true. Fit is more important than most things. For instance if you have a team that works together closely and you hire a lone wolf, you can expect arguments, code that doesn't fit the design and does things in a way that the others don't like and no intention to fix it, lack of willingness to help others out when they need it, refusal to commit stuff to source control, rewriting code for no good reason except he didn't want it that way, etc.
If you have a group of freindly people who hang out together and you hire someone who wants to work in total silence, you will have friction. You may also have harrassment of the person who doesn't fit in.
If you have a group of people who want freedom to do things the way they want and you hire a process-oriented person, there will be continual arguments especially if the process-oriented person is the lead.
If you hire someone whose experience and background make them more of a beginner in a team where everyone is expected to be senior, you will have annoyance as no one wants to mentor the guy or help him learn as they expect he should be able to do it without help.
If you hire someone who expects special priviledges the other employees don't have - you can expect constant warfare. The feelings is "if Sally is so good she gets to wrok from home when I don't, then why should I help her out?" There is resentment when someone comes into a team expecting things (and getting them) that the others don't get especially when they haven't accomplished anything yet. Or there is resentment from the new employee side if they expect things and don't get them when everyone else is fine with the way things are. Then the unhappy employee will waste everyone's time complaining and dragging around like he is being tortured because he has to come in before 1 pm.