4 ms·

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 me

by dsk139 8y 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.

alkonaut 8y ago
> the messages that work are ones that are short. 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!
- dsk139 8y ago
  > concrete information (tasks, location, level, tech/tools, salary, business sector, team size...). If location isn't implied the only reason you wouldn't give it is bad recruiting practices in your case. Salary/Tasks/Team Size could be changing pretty rapidly for startups and an external recruiter might not have the up to to date info. Companies do a bad job at investing in their external recruiting process. FWIW, I always provide company name, location, tech/tools, a hook about why I like them, and if I can find it a hook about the candidate. > But that's the point: a phone call is a pretty big effort I think. Switching jobs is a pretty big effort overall. A lot of engineers who are willing to take the step of taking a call are generally thinking about leaving or actively looking. For strong recruiters the message is just the hook. If you're able to find a few trusted tech recruiters you can use throughout your career it makes the overall search a lot easier every time. It's like finding the all-star real estate agent when you're buying a home. There are a lot of bad recruiters so in your case, it's more likely you haven't found a strong recruiter to work with yet.

by dsk139 8y ago

alkonaut 8y ago

> the messages that work are ones that are short. 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!

dsk139 8y ago
> concrete information (tasks, location, level, tech/tools, salary, business sector, team size...). If location isn't implied the only reason you wouldn't give it is bad recruiting practices in your case. Salary/Tasks/Team Size could be changing pretty rapidly for startups and an external recruiter might not have the up to to date info. Companies do a bad job at investing in their external recruiting process. FWIW, I always provide company name, location, tech/tools, a hook about why I like them, and if I can find it a hook about the candidate. > But that's the point: a phone call is a pretty big effort I think. Switching jobs is a pretty big effort overall. A lot of engineers who are willing to take the step of taking a call are generally thinking about leaving or actively looking. For strong recruiters the message is just the hook. If you're able to find a few trusted tech recruiters you can use throughout your career it makes the overall search a lot easier every time. It's like finding the all-star real estate agent when you're buying a home. There are a lot of bad recruiters so in your case, it's more likely you haven't found a strong recruiter to work with yet.