2 ms·
Given that I've hired a couple of very good people via it... And given that a while after that I went through the round (at least 12 interviews by 10 unique pe
by buro9 13y ago
Given that I've hired a couple of very good people via it...
And given that a while after that I went through the round (at least 12 interviews by 10 unique people) at AWS because of it (though I later turned that down - I wanted a combination of tech and customer focus, they wanted either one or the other and felt I was too strong technically to be used on a customer focused role)...
Yes.
It works.
If you are hiring you should think hard about how you present it. Corporate-speak is ill-advised, and less is definitely more. Plain developer-to-developer language is the best route.
It is not unusual for candidates to go back over old whoishiring posts, filter by city and then look... so if you can include a permalink to a "positions available" page on your site you will continue to reap the rewards of a good, short advert for quite a while. Make sure to include an email address too (in the advert) so that HN candidates reach you directly rather than get lost in the official HR process.
If you are going for a position, I would advise that you use the opportunity to strike up a conversation and learn about the position and company, rather than just spam them with your CV (how does that help either of you?).
And as mentioned above... look at the whoishiring posts for the last quarter or 6 months, a company in growth probably is still looking.
It works, so long as you realise that this platform connects individuals, rather than treating it as an agency/corp HR style thing.
- lgomezma 13y agoI couldn't agree more on the developer-to-developer language. We tend to forget that companies are made by people and for people.
- beachstartup 13y ago> felt I was too strong technically to be used on a customer focused role)... seems like amazon and google have the same ideas when it comes to support.
- buro9 13y agoMy impression of Amazon was that they really are customer obsessed. They did say I was too technical, but what I think they really meant is that they were looking for someone with more business/customer-facing experience and a bit of tech... it was an AWS Solutions Architect position. What they offered instead was a very compelling purely technical position, but I have this deep belief that technology is a set of tools that solves customer problems. I didn't feel comfortable accepting a position in which I could not directly hear from a customer.