They solicited his feedback. Unless he wants to hold them in his pocket as a fall-back, I can't see why he should sugarcoat his response. Yes, you could call his opinion essentially hubris if you disagree and wanted to be antagonistic, but it's at least honest, straightforward, and not unduly confrontational.
I say this as someone who's been off-and-on involved with interviewing and sent out this kind of question to people who turned us down - the only two times I got a response, they were devoid of any information and just platitudes to butter us up. Literally not a single negative point about us or our process, which needless to say was not helpful and personally annoyed me far more than a letter like this would have done.
This makes it clear that he prefers UNIX and that was a factor in declining the position. It stops short of passing sweeping judgements on people who do not prefer UNIX, which is very likely to annoy somebody who prefers Windows.
TL;DR: If an interviewee two years ago had seen that I was on Windows, turned us down, and cited my Windows development as the reason for their refusal, I would probably have switched to ubuntu six months sooner and saved myself (and the company) upwards of 100 hours of dev troubleshooting. So it's hard to view the raw "You're on Windows developing for UNIX. Just what?" as worse than "I'm not a Windows developer, sorry."
Consider if a Windows user said he didn't want to work at a Unix shop because Windows is a better-designed operating system. Would you not consider this a judgement of Unix?
What I really meant, and I guess I didn't do a sufficient job at getting this across, was that I know Unix is rock-solid; I don't know the same about Windows. Truth be told, I know very little about Windows since I haven't used it for 4 years. I was going for a positive point about Unix, not a negative one about Windows.
But you have a pretty good point about my praise of Unix being a vacuous swipe at Windows.
I don't have any local Linux / Unix help.
Perhaps if you joined the team, many of the other developers would also have switched. I might have if I was from this company.
Judgment of a platform and judgment of its users are separate issues.
i think this candidate's response was quite detailed, like for example the fact that he didn't see value in the being grilled on theoretical puzzles.
One great thing about techie and science culture is the wide agreement that being straight and blunt is the way to go. It allows us to identify the problem instead of getting into a game of reading between the lines and trying to figure out what was really meant. In this case the interviewer wanted to know why his offer was rejected. The more complete and direct the answer, the better.
And let's remember this wasn't the initial "thanks for your time, but sorry" letter. It was solicited explicitly. The OP delivered. And there's every reason to think the recipient of this will be smart enough to take it as a data point for the future.
If feedback and criticism are asked for, there's little point to apply sugar, especially when you probably won't have much contact in the future. Sugarcoating is required in environments where saying something that could be taken as insulting can get you killed or a much lower status.
You could have given the same feedback in a way that is much
less likely to come off badly by simply saying "I've really
a UNIX kind of guy and a Windows shop probably isn't the
best fit for me."
This makes a ton of sense. I admit that I saw a chance to soapbox, though I thought constructively, and leapt at it.This also has a good chance of being interpreted badly. Depending on who reads it, picking Windows for your development environment could make sense. Lots of Java development is done on Windows and Windows laptops are a very common sight on Java-related conferences.
Especially as a new grad, it's not really your place to lecture someone about how Unix embodies the essence of good software engineering when they have probably been doing this a lot longer than you and have their own ideas about what good software design is.
You could have given the same feedback in a way that is much less likely to come off badly by simply saying "I've really a UNIX kind of guy and a Windows shop probably isn't the best fit for me."