skip to content

questions

5

What is worth asking a recruiter for after a rejection email, given how little most companies share?

level: juniorimportance: must knowfreq 72%

answer

  1. Reply once, then ask one thing
  2. Process facts travel; opinions do not
  3. Stage reached and reapplication window
  4. Run your own debrief within a day

basics

~20 s

Ask the recruiter for what they can safely confirm: which stage the decision was made at, and how long before you may reapply. Detailed per-round critique is rarely shared, so do not build your prep plan around it.

solid answer

~50 s

Reply once, briefly and graciously, then make a single specific ask. A recruiter can usually confirm process facts — the stage the decision landed at, whether the outcome was about fit with that one team or about the level, and how long the reapplication window on your record runs — because those are policy, not opinion. What they almost never send is per-interviewer commentary: written scorecards are internal, and what an employer will put in writing to a declined candidate is set by its own policy and varies by company. So ask for one thing you can act on, offer to stay in touch, and reconstruct the rest yourself while the loop is fresh — write down every question you were asked and every point where you stalled within a day or two. That self-made record is more detailed than any rejection email will ever be.

go deeper

for a junior

Know that a short, polite reply beats silence, and that one concrete question gets answered far more often than an open request for feedback. Write down every question you were asked the same day, while you still remember it.

for a middle

Be ready to explain what a recruiter can and cannot disclose, and why: process facts come from policy, per-interviewer commentary stays internal. Frame your ask so it only ever needs a policy answer.

for a senior

Show that you can extract signal from a near-silent decline — separating a team-fit outcome from a level outcome, and building your own debrief from notes instead of waiting on the employer to supply one.

for a principal

Own the tradeoff between pressing for detail and protecting a relationship you may need for years. Decide in advance what a single ask is worth and what you will change if the answer is nothing at all.

## What actually lands in your inbox Most declines arrive as a short templated message: thanks, strong pool, we will not be moving forward, we will keep your profile on file. It is generated from the same template for every candidate at that stage, and it is deliberately content-free. Behind it, two things exist that you cannot see: the internal write-ups the panel submitted, and a note on your candidate record in the employer's applicant tracking system that says when you were declined and, at many employers, when you become eligible to apply again. Those two artefacts explain the whole dynamic. The write-ups are rich and the email is empty, and candidates spend enormous energy trying to close that gap by asking for the write-ups. That energy is nearly always wasted. ## Why detailed feedback is rare Three forces push in the same direction. 1. **Policy uniformity.** Once an employer gives one candidate a paragraph of specifics, it has to decide who else gets one. Standardising on a template is cheaper and more consistent than adjudicating that case by case, so the decline text is centrally owned by recruiting rather than written by the panel. 2. **Caution about written commentary.** Employers are generally careful about putting a written judgement of a person's ability in the hands of someone who might dispute it. The exact posture here differs by company and by jurisdiction, and some employers do share more than others — but the default across the industry leans conservative. 3. **Interviewer notes are not written for you.** A scorecard is shorthand aimed at colleagues who sat in the same debrief: half-sentences, internal rating labels, references to a rubric you have never seen. Even if it were handed over, much of it would not be interpretable, and the parts that were could be actively misleading. None of this means the recruiter is hiding something scandalous. It usually means the recruiter is allowed to tell you *what happened procedurally* and not *what people thought*. ## The ask that actually gets answered Split your question into the opinion half and the policy half, and only send the policy half. - Which stage was the decision made at? - Was it about fit with that particular team's work, or about the level the role was open at? - How long is the window before I can be considered again, and does it cover the whole organisation or just that team? - Would you like me to check back with you when it lapses? Every one of those can be answered from the record without anyone forming a sentence about your competence. And they are the questions whose answers change what you do next — which is more than a paragraph of critique would do. ## A worked example A mid-level machine-learning engineer interviews with a public-health data nonprofit and is declined after the onsite. The email is three sentences of boilerplate. She replies the next morning: thanks for the process, one question — was this a fit call for that team's problem space or a level call, and when would you consider an application again? The recruiter answers in two lines: the panel liked the modelling depth, the role needed someone who had run production deployment end to end, and the record carries a nine-month window covering the whole organisation. That is not feedback in the sense she wanted. It is better: it tells her the gap is deployment ownership rather than modelling, and it gives her a date. She spends the window taking on the deployment half of her current team's work and messages the recruiter at the five-month mark with what changed. The failure version of the same story is the one to avoid: reapplying to that same team three weeks later with the same materials. Nothing about her record changed, the window had barely started, and the application is auto-declined — while adding a second decline to the record. ## What to do with silence Run your own debrief within twenty-four hours, before memory decays. Write out every question asked, in order; mark where you hesitated, where you were asked to repeat yourself, where the interviewer moved on quickly. Then classify: knowledge gap, communication gap, or genuine misfit. That document is the input to your next preparation cycle, and unlike the recruiter's opinion, you are guaranteed to get it.

  • The recruiter says they cannot share any feedback at all — what do you ask instead?
    Shift from opinion to policy. Ask when the window recorded against you lapses, whether it covers the whole organisation or only that team, and whether they would like a note when it does. Those are facts a recruiter is allowed to state, they are the two things that actually govern your next move, and asking for them ends the exchange cooperatively rather than on a refused request.
  • Your rejection email says the company encourages you to apply for future roles — does that mean anything?
    Usually it is template text, so do not read it as an invitation. The signal worth weighing is whether a named recruiter wrote to you personally, offered to put your profile in front of other teams, or named a timeframe. Test it directly: ask what the reapplication window on your record is. A real invitation survives that question and comes back with a date; boilerplate comes back with nothing.
  • Should you message the interviewers themselves on a professional network to ask how you did?
    No. Panels are normally instructed to route all candidate communication back through recruiting, so a direct approach puts an individual in an awkward position and typically gets forwarded anyway. If you knew someone on the panel before the loop, a neutral thank-you is fine; a request for their verdict on a decision they participated in is not.

saying these in an interview costs you the question

  • Arguing with the rejection email or asking for the decision to be reviewed
  • Demanding per-interviewer scores the recruiter is not permitted to share
  • Emailing individual panel members directly for their verdict
  • Reading a boilerplate encouragement line as a standing invitation
  • Reapplying within weeks with the same materials while waiting for feedback

context

open as a page

How does a hiring cooldown recorded after a rejection constrain when and where you can reapply?

level: middleimportance: must knowfreq 58%

basics

~20 s

A cooldown is an employer policy blocking reapplication for a set period after a decline, commonly six to twelve months. It is recorded against you as a person in the tracking system, so it can span teams, not just that one role.

open as a page

How do you keep a recruiter relationship warm in the months after a rejection email?

level: middleimportance: should knowfreq 47%

basics

~20 s

Answer the decline graciously, ask permission to check back, then send one short note partway through the waiting period carrying something new — scope you now own, work you shipped. Recruiters source repeatedly and move employers, so the relationship outlives the role.

open as a page

Two months after an onsite rejection, a different team at the same employer posts a role — do you apply?

level: seniorimportance: should knowfreq 38%

basics

~20 s

Ask the recruiter first whether the recorded window is organisation-wide or scoped to the team that declined you. If it is team-scoped and the decline was a fit call rather than a level call, a different team is reasonable; otherwise applying blind just adds a second decline.

open as a page

With cooldowns of six to twelve months, how do you sequence applications across a shortlist of target employers?

level: principalimportance: nice to knowfreq 26%

basics

~20 s

Treat each loop as spending an option that a decline locks for six to twelve months. Interview first where a decline costs least, use those loops to calibrate, and approach the one or two employers you most want after a named gap is visibly closed.

open as a page