Oh, I get them all the time. Usually from junior engineers. I don't hold it against them - it's good advice.

So, what's your trick to avoid getting skipped because a contract recruiter or internal recruiter is going through resumes at 6 a minute and looking for keywords nowhere near the job profile? What's your trick to get through the noise? Right now, it's brutal from junior to staff, and if your network isn't hiring there's no real way to tell the difference between someone who is taking care and someone spamming 200 applications and using 5 minutes of AI to customize. So other than "utilize the network you built over 25 years," what's your advice if all you have is "don't do that?"

I'm glad I have a job now. However, it's brutal for people on the hunt in bad situations or people who have been laid off.

> So, what's your trick to avoid getting skipped because a contract recruiter or internal recruiter is going through resumes at 6 a minute and looking for keywords nowhere near the job profile?

I don't know, but I can't imagine the person whose job is not to look at resumes at all is going to do any better.

There's a tragedy of the commons thing here. It might work if people are getting one inbound email a week and they like reading them. Once it becomes common wisdom, suddenly J Random Employee has dozens of incoming cold emails distracting from their work. So all of them go in the bin.

> So, what's your trick to avoid getting skipped

Ideally write the hiring manager and not HR. And, write something that makes it hard to not want to talk to you.

1: Minimal hygiene is writing something that shows you read the vacancy (if any). Don't: "I'm interested in the role, CV attached". do: "You want onsite in Amsterdam, I'm living in Milan but already planning to move to Amsterdam for reason X".

2: Stand out from the average applicant. Someone recently applied with a personal website that was a kinda-functioning OS (with some apps). Someone else applied with a YouTube channel hacking an ESP32 into their coffee machine. Someone applied with a tool on their GitHub profile, super well written, in our target language, doing interesting things on the database we're working with, etc., etc. how could I _not_ talk these applicants? All of these are soft signals that show affinity for their work as engineers. Don't: generic application letter combined with 3+ pages resume with too much detail.

3: if invited: get curious (but not overly opinionated/combative) about their stack. Candidates we've been most excited about have come in asking questions on how we're setup, and why we've made certain choices. Don't: expect the interviewer to ask all the questions, or bring only a prepared question that misses the mark.

4: Its a people process, if that's your challenge, work on that. Maybe you share a hobby with the interviewer, maybe you've both solved similar problems in earlier jobs, maybe you both like Haskell, maybe something else to connect over. Connection matters to most hiring managers.

You got me there, I don't have one. I'm senior in my career but haven't been able to build a network that I can rely on when I'm looking for my next role, so I'm in the same boat with all of you guys and gals.

I do maintain though that cold reach out is more often harmful due to the barrier of HR/recruiting built to prevent this from happening, and you trying to go around that will likely cause trouble.

Also, when you reach out to the employees for "the referral", what does this even mean? If the person knows you, worked with you, or went to college with you, then they can refer you, but if they haven't even met you and don't even know if you're real, what are you asking them to do? "Hey boss I got this email from this guy he says he's a good fit for this role we have open, do you wanna hire him?", is that it?

DO research the company. DO research the role, the team, the manager, the environment, the toolsets, the issues they're facing. Do NOT flood people's inboxes asking for "referrals" whatever that means.