As a senior software engineer, I would read a recruiter email if it didn't look like a form letter that came from somebody that has not even bothered to look at my resume.
If you include information in the recruitment email that shows you read my resume, SO or LinkedIn profile, etc. and that the job is actually a reasonable fit and sounds interesting to me, I would likely reply. If I'm not personally interested in it, I might be willing to forward it to a friend that might have similar skills and is looking.
Also, consider offering a remote option. This provides a nice work/life balance that a lot of senior devs might appreciate. And don't be stingy with PTO, telling a senior dev that has 5 weeks of PTO at their current job that they will only have a couple weeks PTO if they change jobs could be a major problem.
Same, I read and respond to all recruiter messages that don't look automated.
Remote options without a cost of living skewed wage is important too. It doesn't matter if I live in a high cost city or not, my work product costs what I and the market consider fair.
Honest question - are there any companies that don't skew wages for cost of living? I haven't actively looked for remote positions but from what I saw it seemed to be a standard, even at respected places like Github and Mozilla.
I'm curious if this is perceived as a red flag for remote employees or a standard best practice that you disagree with.
I totally agree with this... I'll reply when they actually show me jobs that match my skill set or offer work life balance... Otherwise my good job is good enough...
Yeah, sometimes recruiters reach out with some weird jobs (offering me a position as a warehouse supervisor) because somewhere I'd done inventory control software, lol.
We're considering reaching out without a particular position. The truth is that the place I work at will generally find a place within the organization for great person who is in the ballpark of our technologies. Candidly,even if the person is not looking now but might be doing so in a year or two, we'd like to chat with them and see whether to tell them to call us in a year, or not.
We're thinking about:
"... I would read a recruiter email if it didn't look like a form letter that came from somebody that has not even bothered to look at my resume..."
This, all this all day every day.
Send me a form letter, your address goes on the block list.
Send me an ACTUAL letter, I'll give you the respect of actually reading it.
"...telling a senior dev that has 5 weeks of PTO at their current job that they will only have a couple weeks PTO if they change jobs could be a major problem...."
This is also an immediate deal breaker as well. Why should I leave where I am with 6+ weeks vaca a year for a new place with 2 to 4 weeks? No, not a chance. BTW: in the EU employees START with 4 weeks.
Most of the recruiter emails usually go like this.
Hope this email finds you well.
Hope this email finds you well.
Followed by a contract job description that doesn't fit your skills well and/or pays really low.
I agree remote options and PTO are big selling points.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.