Hacker News Reader

Comment by jonfw | Hacker News Reader

> “I’ve been hiring people for 10 years, and I still swear by a simple rule: If someone doesn’t send a thank-you email, don’t hire them.”

I was contacted by a recruiter a short while ago asking my availability for a phone screen- and I replied simply with my availability. The recruiter still hasn't gotten back to me, and I think that it may be because I didn't go out of my way to thank them for reaching out to me.

Are all of the niceties in your email inbox really that important to people? It seems pretty manufactured and boilerplate when people send me emails that they "hope find me well".

I may just have to get over it and start letting people know how "excited I am to speak with you and learn more about this opportunity!"

View on HN

Just to make it clear - I posted this as an example of anti-pattern, not the actual advice to follow :)

Yes. They're not testing your knowledge of etiquette, people skills, or friendliness though. They're looking for a more basic and far more widely applicable skill: following best practices. If you were configuring Apache for the first time, wouldn't you google for a list of do's and don'ts and spend a few minutes implementing the low-hanging fruit? Not doing that puts you at a huge risk of leaving a huge security hole or massive performance hit, right? It would be amateurish, and if a problem occurred because you didn't take even a few minutes to do the most basic and widely known stuff, you would have no excuse.

Likewise, while nobody really cares about thank you emails, not doing that suggests you didn't even bother to Google "Interview Tips" and implement the ones that took less than a few minutes. That's not a good signal to send to people that are going to have to rely on your professionalism and quality of work for the next few years.

This would make sense except that the job isn't interviewing for jobs. You shouldn't hold people to the expectation that they're going to approach communicating with recruiters in the same way they would approach actual work they were actually getting paid for. This is a great way to filter good candidates out based on something that has nothing to do with the work you are hiring for.

This doesn't just have nothing to do with the work you are hiring for, this is testing for something that's actually a negative trait in your work.

Technical writing should be as concise and clear as possible

It's my understanding that if you are a talented engineer who is socially competent and interviews well, no, you don't have to don't have to do this.

Reply on news.ycombinator.com