Hacker News new | ask | show | jobs
by p0rkbelly 1687 days ago
maybe they had multiple windows open, scrolled too far, saw a previous job history? Or an automated script gone wrong?

Nobody is saying the recruiter did a good job here, when someone messes up code in Azure, you didn't see the CTO go "OMG my intern wrote the worst code! Let me post it on Twitter so everyone laughs".

This is a teachable moment -- not a shaming moment.

1 comments

The CTO of Azure has no responsibility to an Amazon recruiter. While the recruiter could likely be identified if you searched hard enough, most people aren't crazy enough to care.

This is a teachable moment. Amazon shouldn't engage in these practices and should manage the people they employ so this doesn't happen.

If this was an innocent mistake, you shrug, cop a few jokes with your co-workers and deal with it. No one is going to sack you solely over an incident like this unless you've been going against a strict policy.

This has nothing to do with MSFT or AMZN. A good CTO is at any company provides an example of what to aspire to become. They are mentors and teachers to the technical community as a whole.
This has everything to do with Amazon. Recruiting there needs to fix their archaic sourcing strings.