With most of the jobs I'm contacted for, I just get a general intro of, "Hi, I was looking through your profile and thought you'd be a great fit for a role I'm hiring for..." Then they send the job description and half the requirements list technologies I have no experience in. This isn't necessarily a big deal, but I'm a front end developer and, while I have back end experience, I wouldn't consider myself senior-level for full stack developement, too.
Usually, I reply to all recruiters (not necessarily in a timely fashion though, if I'm not too interested), but the recruiters I usually respond best to are ones that actually seem like they've spent time reading my profile and actually tailored a personalized message. The ones that seem canned get a canned, "No Thanks" response from me.
The best recruiters I've worked with were actually ones not specifically trying to fill a role they thought I'd be good for, but ones that wanted to meet for coffee, learn more about me and create a relationship that might eventually turn into a placement. I realize that jobs come in that need to be filled quickly, but if the recruiter already has a pool of good talent to pull from, that they have a relationship with on some sort of personal level, it's far easier to find a good fit, not only for the candidate, but for the company hiring, as well.
As far as the job description is concerned, the things that stand out most to me is HOW it's written, not necessarily what's on it. If they want an expert in Framework A with several years of experience in it, I probably won't be excited to apply. Not because I'm not excited to use that technology, but because that to me says that the company is too locked into their framework to care about whether the person is actually proficient in the underlying language. Yes - I want to know what tech stack you use, but if you say I need 4+ years with React and then don't even mention a measure for JavaScript itself, no thanks. Hire people based off their skills in the language they program in, not whatever framework is "in" at the time. The only exception to this I can think of is with C#/.NET and Ruby/Rails, which are fairly synonymous in their industries.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
With most of the jobs I'm contacted for, I just get a general intro of, "Hi, I was looking through your profile and thought you'd be a great fit for a role I'm hiring for..." Then they send the job description and half the requirements list technologies I have no experience in. This isn't necessarily a big deal, but I'm a front end developer and, while I have back end experience, I wouldn't consider myself senior-level for full stack developement, too.
Usually, I reply to all recruiters (not necessarily in a timely fashion though, if I'm not too interested), but the recruiters I usually respond best to are ones that actually seem like they've spent time reading my profile and actually tailored a personalized message. The ones that seem canned get a canned, "No Thanks" response from me.
The best recruiters I've worked with were actually ones not specifically trying to fill a role they thought I'd be good for, but ones that wanted to meet for coffee, learn more about me and create a relationship that might eventually turn into a placement. I realize that jobs come in that need to be filled quickly, but if the recruiter already has a pool of good talent to pull from, that they have a relationship with on some sort of personal level, it's far easier to find a good fit, not only for the candidate, but for the company hiring, as well.
As far as the job description is concerned, the things that stand out most to me is HOW it's written, not necessarily what's on it. If they want an expert in Framework A with several years of experience in it, I probably won't be excited to apply. Not because I'm not excited to use that technology, but because that to me says that the company is too locked into their framework to care about whether the person is actually proficient in the underlying language. Yes - I want to know what tech stack you use, but if you say I need 4+ years with React and then don't even mention a measure for JavaScript itself, no thanks. Hire people based off their skills in the language they program in, not whatever framework is "in" at the time. The only exception to this I can think of is with C#/.NET and Ruby/Rails, which are fairly synonymous in their industries.