|
|
|
|
|
by dsk139
2953 days ago
|
|
Source: I'm an engineer & recruiter that works with over 100 tech companies in NYC. I also work on a SaaS platform for recruiters. After A/B testing tons of messages (and analyzing messages from a SaaS platform I built for recruiters to send messages) the messages that work are ones that are short. So I try to keep messages brief, reach out about a specific company that might be a match, and hope to get on the phone with you to actually be able to do my actual job. It's very hard to convert someone over an e-mail message. Getting you to respond to my e-mail is the first part of the funnel. From there if I can get a conversation with you I can move on to the "fun" part of my job. Giving candidates a broad overview of the market based on their interests, expectation setting, and career counseling. Edit: To answer your question directly the reason you get bad recruiting messages stems from a mix of bad recruiting practices, bad companies/ low investment in HR departments, and bad engineers. Would be happy to give you a recommendation for a solid recruiter in SF or NYC if you're in those areas. |
|
I completely buy that. But in a short message there is still the choice between concrete information (tasks, location, level, tech/tools, salary, business sector, team size...).
> hope to get on the phone with you to actually be able to do my actual job
But that's the point: a phone call is a pretty big effort I think. I might do it if there is any clue that the job might be something for me but I won't do it if there is a risk that the job is in the wrong part of the country!
> Would be happy to give you a recommendation for a solid recruiter in SF or NYC if you're in those areas.
Not in the US, but thanks!