The Rejection Reply Score, Six Dimensions to Close, Thank, Ask, or Redirect
Score any rejection on six dimensions in about 16 minutes and send exactly one reply (none, thank, ask, or redirect), with a dated follow-up or close-out logged.
Key takeaways
- In Talent Board's CandE benchmark, 33% of rejected candidates were notified from a do-not-reply address, so a blanket "always reply" rule wastes effort on about one rejection in three.
- Feedback odds rise with stage: 70% of candidates got no feedback after a phone screen versus 54% after an interview, so a feedback question belongs mainly to interview-stage rejections.
- Only 6% of candidates received feedback on assessment results, yet feedback on a piece of work is safer for an employer to give than feedback on a person, which makes the assessment question an unmet but low-risk ask.
- In Refolk's index there are about 12.4 US recruiters per recruiting coordinator, so a rejection signed by a coordinator should be redirected to the recruiter who owns the requisitions.
- A redirect must cite a requisition ID and its first_published date from the employer's public job feed, because updated_at changes on every edit and makes old postings look fresh.
- Every rejection ends in the log with either a calendar follow-up date or a written close-out, never an open loop.
This is the scoring standard for the reply window right after a rejection. It tells you which noes to close in silence, which to thank, which to ask one feedback question of, and which to answer by pointing at a specific open role at the same employer. It is for job seekers running dozens of applications who get several rejections a week. You score each rejection on six dimensions, send exactly one of four replies within 48 hours, and log a dated follow-up or a close-out.
What the rejection reply score decides
The rejection reply score settles one question: what, if anything, you send in the 48 hours after a no. It does not cover mid-loop updates or whether to reapply months later. Those are separate decisions with their own evidence.
The usual advice is "always reply", with one template attached. That advice treats every rejection the same, and they are not the same. A message from a do-not-reply address after you submitted an application differs from a named recruiter's note after your final round on four counts: whether anyone reads your reply, whether you will get feedback, how cautious the employer is legally, and how likely you are to be contacted again as a near-miss.
The four replies:
- None (close). Nothing is sent. You log the rejection as closed, or you apply directly to a different requisition if one fits.
- Thank. Two lines that keep you on the recruiter's list of near-miss finalists.
- Ask. One feedback question, fitted to the stage you reached.
- Redirect. One message that names a specific live requisition at the same employer and asks the recruiter to route you to it.
Terms used throughout:
- A requisition (req) is the employer's internal record for one approved opening, usually with its own ID.
- An adjacent requisition is a different open req at the same employer that the evidence from your rejected process fits.
- A silver medalist is, in SocialTalent's definition, "the second-place candidate behind the eventual hire".
- A cooldown is the period an employer asks you to wait before applying again, usually scoped to a job family rather than the whole company.
The six dimensions and how to score each
Score every rejection on six dimensions from 0 to 2: stage reached, sender type, message wording, live adjacent requisition, stated cooldown, and named-contact value. Each score has a specific way of misleading you, so the check matters as much as the number.
| Dimension | 0 | 1 | 2 |
|---|---|---|---|
| Stage reached | Application screen | Recruiter screen or assessment | Hiring manager or final round |
| Sender type | No-reply ATS address | Template from a named account, coordinator, or agency | Named in-house person, written for you |
| Wording | Pure boilerplate | Names a team or a timeframe | Cites something from your rounds |
| Live adjacent req | None | Adjacent but stale or off-team | Live req with ID and fresh first_published |
| Stated cooldown | Covers the adjacent req's job family | None stated, none found | Explicitly invites other roles |
| Named-contact value | Nobody, or agency without other reqs | Coordinator | In-house recruiter or TA lead who owns reqs |
Stage reached
The stage shows how much the employer knows about you, and how much a reply can draw on. Use five stages: application screen, recruiter screen, assessment, hiring manager round, final round. It lies when the ATS (applicant tracking system, the software that stores applications) sends a rejection because one posting closed while you are still in process for another. A single person in an ATS can have several applications, each with its own status. If you have another live process at the employer, ask the recruiter before you score this as a no.
Sender type
The sender tells you whether a person will read your reply. It lies when a personal-looking email is really a template scheduled under the recruiter's name. Recruiter accounts on Blind say the ATS sends the email after a recruiter clicks reject, and that personal-looking emails get scheduled from the recruiter's own account. Look for merge-field phrasing, such as your name in a different font or a generic role title, and for a send time outside working hours.
Message wording
Wording shows whether anyone thought about you specifically. It lies when you read "we'll keep you on file" as interest. That line is boilerplate. Score it 1 only if the message names a team or a timeframe, and 2 only if it refers to something that happened in your interviews.
Live adjacent requisition
This shows whether there is a real opening to send the recruiter to. It lies when you trust a "recently updated" date. In the public Greenhouse feed, updated_at moves whenever a posting is edited. On one board, all 44 jobs had an updated_at in the past week, but only 1 had a first_published date in that week. Score 2 only with a requisition ID and a first_published date you have checked yourself.
Stated cooldown
The cooldown shows whether the employer will even consider you for the adjacent req. It lies when you apply an old forum figure to an employer whose policy has changed. Third-party summaries of Google's careers page report a wait of at least a year for the same type of role, while older sources report 90 days after a resume-stage rejection. Check the employer's current careers FAQ, and note whether the cooldown covers the job family or the whole company.
Named-contact value
This shows whether the person you reach can actually move a requisition. It lies when the sender is an agency recruiter. Agencies appear among the top employers of recruiters in Refolk's index: K2 Partnering Solutions and Experis in the US, Hays in the UK. An agency recruiter usually does not own the employer's other reqs. Check the sender's email domain against the employer's.
Which reply each score earns
Add the scores into two numbers. The relationship score is stage + sender + wording + named contact (0 to 8) and measures whether a reply will reach someone who knows your work. The opening score is live req + cooldown (0 to 4) and measures whether there is a door to point at. Together they place each rejection in one of four quadrants.
Rejection reply quadrants
Apply these rules in order. The first one that matches wins.
- Hold. You have another live application at this employer and have not confirmed this is a final no. Ask the recruiter that one question. Do not score yet.
- Redirect. Live req = 2, cooldown is 1 or 2, named contact is 1 or 2, and relationship is 4 or more. If the contact is a coordinator, address the redirect to the recruiter.
- Apply direct. Live req = 2, cooldown is 1 or 2, but relationship is 3 or less. Reply none. Apply to the req as a new application and log it as one.
- Close. Relationship is 3 or less. Reply none.
- Ask. Stage = 2 and either sender = 2 or wording = 2. Also ask after an assessment if a named person sent the rejection, because feedback on work is low-risk for the employer.
- Thank. Everything else that reached this rule.
When both ask and redirect qualify, redirect wins. No source documents whether to ask for feedback first or redirect first. My reasoning is that a redirect asks for a decision the recruiter can make today, while feedback asks for something their legal training tells them to withhold. Save the feedback question for a later follow-up if the redirect goes nowhere.
A reply is worth sending only when someone who can change a decision will read it.
Who actually reads the reply
Talent acquisition has layers, and the person who signed the rejection is often not the person who can act on a reply. Route thank-yous and feedback questions to the recruiter you worked with, and route redirects to whoever owns the adjacent requisition.
Who can act on your reply
- No-reply ATS addressFired when someone clicks reject; no documented reader
- Recruiting coordinatorSchedules and sends; rarely owns requisitions
- Recruiter or TA PartnerOwns requisitions; the target for thank, ask, and redirect
- Head, Director, or VP of TAAbout one per 48 recruiters in the US; not a first stop
Refolk's index shows how thin each layer is in the US:
| Role band | US profiles | Recruiters per role |
|---|---|---|
| Recruiter / TA Partner | 122,594 | 1.0 |
| Recruiting Coordinator | 9,891 | 12.4 |
| Head/Director/VP TA | 2,549 | 48.1 |
Source: Refolk's index. The ratios are derived from the profile counts.
Titles mean different things in different markets. In Refolk's index, Recruiter, Technical Recruiter, and Talent Acquisition Partner titles make up 122,594 US profiles and 9,345 UK profiles, and the mix differs sharply:
| Market | Technical Recruiter | Recruiter | TA Partner |
|---|---|---|---|
| US | 36% | 28% | 8% |
| UK | 12% | 28% | 48% |
Source: totals from Refolk's index. The shares come from a 25-profile sample of top titles, so treat them as directional.
The practical reading: in the UK, a "TA Partner" title is common and often belongs to a recruiter aligned with one business unit. That may make a redirect easier to route if the adjacent req sits in the same unit. Treat this as a hypothesis, and confirm it by asking the recruiter which teams they cover.
When asking for feedback pays
Ask for feedback only after an assessment, a hiring manager round, or a final round, and only with one specific question. After a phone screen, most candidates get nothing back, and the feedback that does arrive is often too general to use.
| Metric | Value | Source year |
|---|---|---|
| No feedback after screen or interview | 56% | 2025 |
| Feedback on assessment results | 6% | 2025 |
| No feedback after phone screen | 70% | pre-2021 |
| No feedback after interview | 54% | pre-2021 |
| Notified via do-not-reply address | 33% | 2025 |
Source: Talent Board CandE benchmark (2025 rows) and Gem (the 70% and 54% rows).
The gap between what candidates want and what they get is wide. In one 2022 survey, 94% of candidates wanted interview feedback and 41% got any. Of those who got feedback, only 37% found it useful, and 22% of interview-stage feedback was general rather than specific. There is a reason for employers to do better: candidates' willingness to refer others rose 53% when they received specific feedback at the interview stage. That gives you an angle, but it does not oblige anyone to answer.
Why recruiters go quiet
The main fear is discrimination claims. One practitioner puts it this way: a stated reason "gives the candidate the opportunity to poke holes in that reason". The legal landscape:
- US, general: no general federal duty to give reasons was found.
- US, background reports: the FCRA applies only when a background report was used, and even then it "does not explicitly require employers to state the specific reason for the decision".
- New York, criminal history only: Correction Law § 754 requires, on request, a written statement of the reasons for the denial within 30 days.
- UK and EU: a GDPR subject access request (SAR), a legal request for the personal data an organisation holds on you, reaches interview notes and scores. It must be answered within one month, extendable by two more months.
One question per stage
Fit the question to what the employer actually saw. Feedback on a piece of work is safer to give than feedback on a person, which is why the assessment question has the best ratio of risk to reward, even though only 6% of candidates get assessment feedback today. At the hiring manager and final rounds, ask about evidence going forward, not about how you compared with the person hired.
The 48-hour rejection reply run
Run the same eight steps on every rejection: classify, stage, wording, requisition check, score, send, log, and an optional SAR. The first five take about 16 minutes in total, most of it the requisition check.
From rejection email to a logged reply
- Classify the senderDecide whether the rejection came from a no-reply ATS address, a recruiter's or coordinator's own address, or an agency recruiter, and check the email domain. Done when the sender type is logged (1 minute).
- Record the stage reachedLog one of five stages: application screen, recruiter screen, assessment, hiring manager round, final round. If you have another live application at this employer, confirm it is really a no before scoring (1 minute).
- Read the wordingLook for a stated cooldown, "future roles" language that names a team or timeframe, and any personal detail from your rounds. Done when a cooldown date or "none stated" is logged (2 minutes).
- Check for live adjacent requisitionsPull the employer's public job feed, filter by the department or office you interviewed with, and read first_published, not updated_at. Done when you have a requisition ID and first_published date, or "none" (10 minutes).
- Score and pick one replyScore the six dimensions from 0 to 2, compute the relationship and opening scores, and apply the decision rules in order. Done when exactly one of none, thank, ask, or redirect is chosen (2 minutes).
- Send within 48 hoursSend the chosen reply to a named person, never to the no-reply address. Done when it is sent, or logged as "none" with the reason.
- Log a dated follow-up or close-outWrite a calendar date for the next check, or mark the loop closed. Done when the row has a date or a close-out.
- Consider a SAR after a final-round no (UK and EU only)If a final-round no makes no sense, consider a subject access request for your interview notes and scores, which the employer must answer within one month, extendable by two.
Notes on the steps that take judgement:
- Step 4, the feed. Employers that host jobs on Greenhouse expose a public job board feed that needs no login, documented in Greenhouse's Job Board API docs. Each job returns id, internal_job_id, requisition_id, updated_at, first_published, departments, and offices. Cite requisition_id, title, department, office, and first_published in your redirect. Never cite updated_at as the date the job was posted. If the employer uses another ATS, read the posting date on its careers page and note that you could not confirm it from a feed.
- Step 6, the 48 hours. Treat the window as my working rule rather than an established fact. Data attributed to Talent Board links response speed to how candidates rate the process, but I have only seen it second-hand and could not verify it. The practical reason is simpler: two days after the no, the recruiter can still place your name without reopening the file.
The four replies, ready to send
Each reply is short, goes to one named person, and asks for at most one thing. Paste the version the score chose and fill in the braces. Never send a template with an unfilled field.
NONE
(Nothing sent. Log: "closed, {date}, reason: {no-reply sender / application screen / apply direct to req {ID}}".)
THANK
Hi {Name}, thanks for letting me know, and for the time {the team} gave me through the {final round}.
I'd like to stay on your list for {team or role family}; if a similar seat opens, I can move quickly.
ASK (one question, matched to stage)
Hi {Name}, thank you for the update and for the {interviews / exercise}.
Recruiter screen: Was there one requirement in the posting where my background read as short?
Assessment: Was there one part of the {exercise} that weighed most in the outcome?
Hiring manager or final round: Is there one area of the role where you would want to see stronger evidence from me next time?
REDIRECT
Hi {Name}, thanks for the update on {role}.
I noticed {Title} (req {requisition_id}) in {department}, {office}, first published {first_published}.
It leans on {the specific overlap}, which is where my {rounds} went strongest.
Are you the right person to put me forward for it, or should I go to its recruiter?Send exactly one. Replace every {brace}. Pick the single ASK line that matches the stage you reached.
The redirect is the reply that "keep me in mind" never manages, because it hands the recruiter a decision with a requisition attached. It only works if your fit for the adjacent req is real, and judging that at speed is where the time goes. Refolk scores how well you fit the adjacent posting before you name it, and tailors your resume to that requisition so a tailored version is ready if the recruiter says yes. If the fit score is weak, downgrade the reply to thank or ask instead of sending a redirect you cannot back up.
Log every rejection in the same format, whatever reply you chose:
Received: {date}
Employer / role / req: {employer} / {title} / {requisition_id or "none"}
Stage: {application screen | recruiter screen | assessment | hiring manager | final}
Sender: {no-reply | named template | coordinator | agency | named in-house}
Scores (stage/sender/wording/req/cooldown/contact): {0-2}/{0-2}/{0-2}/{0-2}/{0-2}/{0-2}
Relationship (0-8): {n} Opening (0-4): {n}
Reply: {none | thank | ask | redirect | hold}
Sent: {date or "not sent"}
Cooldown ends: {date or "none stated, checked {date}"}
Follow-up date: {date} or Closed: {date, reason}
Outcome: {to fill}One row per rejection. The last two fields must never both be blank.
How the score goes wrong
Each dimension has a false positive, a reading that looks like a strong signal but is not. These seven account for most bad replies, and each comes with a check that takes under a minute.
- The rejection that is not a no. Looks like: an ATS rejection while you are mid-process for another role at the same employer. Why it lies: one person can hold several applications in an ATS, each with its own status, and closing one posting triggers the email. Check: ask the recruiter whether your other process is still live before you score anything.
- The scheduled "personal" note. Looks like: an email from the recruiter's own name and address. Why it lies: recruiters schedule templated rejections from their own accounts. Check: look for merge-field phrasing, a generic role title, and an odd send time. If you find them, score sender as 1, not 2.
- "We'll keep you on file." Looks like: interest. Why it lies: it is boilerplate that goes into nearly every rejection. Check: does the message name a team or a timeframe? If not, wording is 0.
- The fresh-looking stale req. Looks like: an adjacent posting updated this week. Why it lies: updated_at moves on every edit. On one board, 44 jobs showed a recent update but only 1 had been first published that week. Check: use first_published, and nothing else, as the posted date.
- The borrowed cooldown. Looks like: a forum post saying you can reapply after 90 days. Why it lies: policies change. Summaries of Google's careers page now report at least a year for the same type of role, against older reports of 90 days. Check: the employer's current careers FAQ, read for scope (job family or company-wide).
- The useless answer. Looks like: you asked for feedback and got a reply. Why it lies: 22% of interview-stage feedback in one survey was general, not specific. Check: ask one stage-specific question, never "any feedback?", and log a generic answer as closed rather than chasing it.
- The agency dead end. Looks like: a warm, named recruiter who wants to help. Why it lies: agency recruiters, who show up among the top employers of recruiters in Refolk's index, usually do not own the employer's other requisitions. Check: compare the sender's email domain with the employer's. If they differ, score named contact as 0 for redirect purposes.
There is a quieter failure too: scoring generously because a rejection stings. If you reached a final round and the recruiter was warm, the urge is to send a thank-you, a question, and a redirect in one email. That message asks for three things and gets none. The scores exist so that each reply competes for one slot.
Keeping the log current
The log is only useful if every row ends with a date. Re-contact finalist relationships within three months, re-check cooldowns against the employer's live careers page, and close everything else.
Set follow-up dates by reply type:
- Redirect: chase once if there is no answer. Check the req in the feed again first, because a req that is no longer listed ends the loop.
- Ask: if no answer arrives, close the loop. Do not chase feedback twice.
- Thank: set a finalist check-in date under three months out. One playbook reports silver medalist response rates of 35-40% within 3 months, 20-25% at 3 to 12 months, and 8-15% after a year. The underlying dataset is unverified, but the direction matches SocialTalent's estimate that role-specific re-engagement lands often 5-15% over 12 months.
- None: close on the day, unless you applied direct to an adjacent req, in which case that application gets its own row.
- Cooldown: log the end date as its own reminder. Volume limits are separate from cooldowns. Google, for example, allows up to three applications per rolling 30 days.
Treat every cooldown and cap in your log as a snapshot. Re-check the employer's careers FAQ on the day you act, note the date you checked, and replace any figure you got from a forum. For employers other than Google, no cooldown is verified in this guide. Find it yourself or log "none found, checked {date}".
When a redirect gets a yes, the bottleneck moves from deciding to tailoring, and you may be applying to two or three adjacent reqs at once. Refolk tailors the resume to each requisition and drafts the cover letter from your own history, so the speed you gained in the reply window carries into the application itself.
Before you close a rejection row
- The sender type is logged, and any agency sender has been identified by email domain.
- You confirmed the rejection is not just one posting closing while another application at the same employer is still live.
- The cooldown is logged with its scope and the date you checked the employer's current careers FAQ, or logged as "none found".
- Any requisition you named was verified by requisition_id and first_published, not updated_at.
- Exactly one reply was chosen, and it went to a named person, not a no-reply address.
- Any feedback question was a single question fitted to the stage reached.
- The reply was sent within 48 hours of the rejection, or the row says "none" with a reason.
- The row ends with either a dated follow-up or a dated close-out.
Questions job seekers ask
Should I reply to a rejection email from a no-reply address?
No, not to that address. No vendor documents that replies to do-not-reply addresses get routed to a person, and Talent Board's benchmark found 33% of rejections arrive that way. If you reached an interview stage and know a named recruiter from the process, send your one reply to that person directly. If you never spoke to anyone, log the rejection as closed and move on.
Should I ask for feedback after a rejection?
Ask only when the odds justify it: after an assessment, a hiring manager round, or a final round, and only when a named person sent the rejection. After a phone screen, 70% of candidates get no feedback at all. Ask one specific, forward-looking question rather than "any feedback?", because 22% of interview-stage feedback in one survey was general and not useful.
Can I apply for another role at the same company after being rejected?
Usually yes, but check the employer's current careers FAQ for a cooldown first. Third-party summaries of Google's careers page report a wait of at least a year for the same type of role, while different job families are not covered. Google also caps applications at three per rolling 30 days. Other large employers' rules are not verified here, so check each one yourself.
How do I ask a recruiter about other open roles after a rejection?
Name one specific live requisition rather than writing "keep me in mind". Give its title, requisition ID, department, office, and first_published date from the employer's public job feed, say in one sentence why your evidence from this process fits it, and ask whether the recruiter is the right person to put you forward. Send it to an in-house recruiter, not an agency recruiter.
Why won't recruiters tell me why I was rejected?
Mainly fear of discrimination claims: a stated reason gives a candidate something to challenge. In the US there is no general federal duty to give reasons, and even the FCRA does not require a specific reason when a background report was used. New York requires written reasons on request only in criminal-history cases. In the UK and EU, a subject access request can reach interview notes and scores.
Put this to work
Paste your career in once. Every application after that is written for you.
Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.
01Drop your resume
A PDF or a LinkedIn URL. About a minute, once.
02I rank the openings
Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.
03Each one is written up
Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.
- New matches ranked and written before you are up.
- Every bullet stays inside what your history supports. Nothing invented.
- Queued, submitted, interviewing, offer: one screen, not a spreadsheet.
Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.