4 ms·
> Two years ago, after a rather unpleasant interview process, I asked to be put on a do-not-contact register Great! Clearly he's closed that chapter in his lif
by dymk 8y ago
> Two years ago, after a rather unpleasant interview process, I asked to be put on a do-not-contact register
Great! Clearly he's closed that chapter in his life and he can move on. It'd be a bummer if they contacted him again, luckily he can just say "No thank you" like a normal person. But wait!
> here I am reading yet another email from an Amazon recruiter asking to talk to me about a possible opportunity. Will this horror never end?
This gets the biggest eyeroll I can possibly muster.
> This is a retelling of the two tedious months that Amazon put me through only to tell me that I can't code, which I now find funny, but at the time it was rather insulting and humiliating
Is this guy serious? He didn't meet the bar, but instead of working on the weak areas of his skillset, he's claiming he's was insulted and degraded.
---
Amazon clearly was not a fantastic company to interview with, but man this guy really milks it to the point where I don't have a lot of sympathy for him.
- TideAd 8y agoI hear about companies telling candidates they "can't code" or "can't communicate" a lot. This just seems like a really rude and arrogant thing to tell someone. If you want to give a candidate feedback, give specific feedback and give it politely. The people who want to improve will get the picture. If you don't want to, just thank them for their time and interest. Other than that, I think you're right. Some of this was really pretty normal and not worth being upset about.
- dymk 8y agoI can guarantee you that Amazon/the recruiter didn't tell this developer that he couldn't code - that's an inference he made
- gbear605 8y agoHe also noted that he was asked interview questions for a job that he wasn’t applying for and hadn’t prepared for! It’s not surprising if he didn’t do a great job at answering frontend questions when he was applying for a backend position.
- bgeeek 8y agoYou are being a little harsh there. I'm not sure if turnover/burnout is high at places like that or they just keep on hiring but I've experienced it whereby recruiters are repeatedly chasing you for the same job over and over again. This is probably partly due to the companies and/or recruiters also having a high turnover. So, if you fail to get the job, you can sometimes almost expect to have other people get in touch with you over and over again for the same role. It can get very, very strange.
- bradenb 8y ago>> here I am reading yet another email from an Amazon recruiter asking to talk to me about a possible opportunity. Will this horror never end? > This gets the biggest eyeroll I can possibly muster. I get why you're saying that, but as a totally average developer, I feel like I can corroborate this: Amazon recruiters email me _constantly_. I do not think I should be a target for them (I doubt I could pass their interview process), I think they're just desperate and take the shotgun approach to recruiting. >> This is a retelling of the two tedious months that Amazon put me through only to tell me that I can't code, which I now find funny, but at the time it was rather insulting and humiliating > Is this guy serious? He didn't meet the bar, but instead of working on the weak areas of his skillset, he's claiming he's was insulted and degraded. I do agree with you on this one, though. I read the story and for the most part thought that nothing they did was too bad. Yeah, they changed up some things, messed up some scheduling (they are human after all), but if you're being considered for a certain level and you don't perform at that level (for them) then what should they tell you? Saying they're "going in a different direction" or "opted for a more qualified candidate" doesn't really give you the feedback you want, does it? I want to know if I'm not performing at the level I think I am.