4 ms·

Considering how strongly the author feels about developing exclusively on *nix, I found it surprising that it took as much as an interview for him to learn that

by grammr 16y ago

Considering how strongly the author feels about developing exclusively on *nix, I found it surprising that it took as much as an interview for him to learn that "company X" uses Windows. Almost all software job reqs. offer reasonable insight as to what key technologies they use. Other than that, I found his response reeking of condescension and inexperience.

dhume 16y ago
I found it surprising that it took as much as an interview for him to learn that "company X" uses Windows. I didn't catch anything in the post saying he didn't find that out until the interview.
- kenjackson 16y ago
  Then why did he interview? If it was a phone interview... sure, no biggy. But an onsite interview requires some DD by the applicant. You don't even accept the interview if there's no chance you'd work there. And if you do it anyways, maybe for practice, then you don't give this type of feedback. It's like going out on a date with a girl you're not attracted to just for practice. And then when she asks why you didn't go on a second date saying, "Because you're frankly not very attractive." You were kind of a jerk for going on the date in the first place, but the feedback made you a certified one. In any case either the candidate doesn't do the type of reasonable DD that I'd expect from an applicant, even a college hire. Or he's bordernline unethical.
  - dhume 16y ago
    You don't even accept the interview if there's no chance you'd work there. You don't know that there's no chance of working there until you know what your other options are. If you're still interviewing (i.e. you don't have offers/rejections in hand yet), you don't know what options you have. You might know that you won't accept Company X's offer if Company Y also makes you an offer, but that's quite a different situation from knowing there's no way you'd accept Company X's offer.

by grammr 16y ago

dhume 16y ago

I found it surprising that it took as much as an interview for him to learn that "company X" uses Windows. I didn't catch anything in the post saying he didn't find that out until the interview.

kenjackson 16y ago
Then why did he interview? If it was a phone interview... sure, no biggy. But an onsite interview requires some DD by the applicant. You don't even accept the interview if there's no chance you'd work there. And if you do it anyways, maybe for practice, then you don't give this type of feedback. It's like going out on a date with a girl you're not attracted to just for practice. And then when she asks why you didn't go on a second date saying, "Because you're frankly not very attractive." You were kind of a jerk for going on the date in the first place, but the feedback made you a certified one. In any case either the candidate doesn't do the type of reasonable DD that I'd expect from an applicant, even a college hire. Or he's bordernline unethical.
- dhume 16y ago
  You don't even accept the interview if there's no chance you'd work there. You don't know that there's no chance of working there until you know what your other options are. If you're still interviewing (i.e. you don't have offers/rejections in hand yet), you don't know what options you have. You might know that you won't accept Company X's offer if Company Y also makes you an offer, but that's quite a different situation from knowing there's no way you'd accept Company X's offer.