This is pure awesomeness. I've rejected people for all of those reasons but haven't ever put them together so succinctly.
The one that can really swing my vote one way or another is the lack of passion. To be clear you are probably passionate about something, and I don't mean "getting paid to work here." For example when I was with Google (and even earlier at Sun) I interviewed candidates who were passionate about wanting to work at the company but were not passionate about any thing in particular the company was doing. Their passion was 'to be employed by <company X>' and I would ask them "Ok, so lets say we hire you and you've achieved your goal, now what are you hoping to achieve?" only to get crickets. That is always hard to get past.
Thanks for reading. I've received many of these responses lately on some job candidates and thought there was some value in compiling them for engineers that may be interviewing. I could certainly see where candidates might get hung up on working for a particular employer without necessarily being as passionate for their role there. I don't see that too often as I tend to recruit for smaller software firms, but I'm not at all surprised that you would see that at Google, Sun, Apple, etc.
The one that can really swing my vote one way or another is the lack of passion. To be clear you are probably passionate about something, and I don't mean "getting paid to work here." For example when I was with Google (and even earlier at Sun) I interviewed candidates who were passionate about wanting to work at the company but were not passionate about any thing in particular the company was doing. Their passion was 'to be employed by <company X>' and I would ask them "Ok, so lets say we hire you and you've achieved your goal, now what are you hoping to achieve?" only to get crickets. That is always hard to get past.