“Why was my resume rejected when I think I’m a great fit for this job?”

So many times I’ve observed the reason being the hiring manager not talking with their recruiter / inbound sourcer / the person doing the resume screening.

The hiring manager would eg say “I want someone senior with Go experience, don’t send me anyone below 5 YOE” and the recruiter rejects anyone without 5 years of Go on their resume, even though it’s not what the hiring manager meant…

A lot of the times, the issues come not just from the lack of hiring manager - recruiter communications, but not having a job description that specifies what the hiring manager is *really* looking for. Wrote suggestions on how to tackle this in The Pragmatic Engineer: https://newsletter.pragmaticengineer.com/p/hiring-software-engineers
Hiring Software Engineers

Building an engineering hiring process from role definition to debrief, and calibrating it.

The Pragmatic Engineer

@gergelyorosz Absolutely agree - The worst mistake I have done as a hiring manager was telling the recuiter that „It‘s a generic profile, same as always“, but as soon as CVs and candidates came in, the „But actually I need…“ started. Which is not only a big waste of time, but also damaging to the HM - Recruiting relationship.

Spending time and dilligence upfront on a clear internal and external description of who could fit the job pays off a lot, especially when hiring a lot.