Compare candidates before you submit the req

Most reqs do not have one perfect person. You have a strong Java person with a weak cloud story, a cloud person who is light on Kafka, and a contractor who can start Monday. Sending all three without a point of view makes the hiring manager do your job.

Compare against the JD, not against each other in the abstract

“Who is more senior?” is the wrong question. The right one is who hits the gates and the must-haves. Put the same JD next to every resume. Score must-haves, recent evidence, and logistics. Then pick a first submit and a backup — or pass on all three.

• Same JD for every row. Do not move the goalposts mid-matrix.
• Call out the gap you will disclose. Do not hide it in the third paragraph.
• If two people are equal on skills, let notice period and location break the tie.

Compare Candidates takes one JD and multiple resumes and builds the matrix. Use JD Analyzer if the req is still a wall of text. Send the first packet with a recruiter summary that says why this person, not why the other two were almost as good.