RehearseaBlog
5 min read

A rejected application is not a failed interview

An interviewer lists the reasons they did not hire someone who left thinking it went well. Almost none of them were visible from inside the conversation.

  • job rejection
  • interview process
  • job search
  • hiring

When an interview goes well and the offer does not arrive, the default reading is that you were assessed and found wanting. There is a version of this post that is easy to write and useless: it would say the interview was not what you thought, you did your best, and the outcome was not about you. That is comforting and it is not true, because the alternative reading is also wrong, and the person who can tell you why is on the other side of the table.

What interviewers say actually happened

Someone who has sat on hiring panels posted their own list of why they had not hired a candidate who, from the candidate's side, had a very good interview.

They are worth reading in the order given, because the reasons get further from anything the candidate could have controlled:

  • A weak answer on a core requirement, and a strong one on a bonus skill. The interviewer is explicit that the candidate often does not know which skills the company cares about most, "especially because the job posting may not make it clear".
  • Someone else was the favourite. Not a better candidate on the evidence: someone a panel member had worked with before and "felt comfortable with", "picked out already".
  • An internal candidate. Someone who "would have had to basically fall flat on their face to lose the role", and "did okay".
  • Level, or shape. Too junior, too senior, or skills skewed towards an area the team cannot use. The interviewer's phrase is "for this particular role".
  • A hidden requirement nobody was told about. A role with no room for advancement, where a candidate's obvious strength was the wrong thing.

Read that list as a whole. Four of the five are things the candidate could not have observed, and the fifth is a requirement the posting did not state. None of them is a judgement about how well someone answered.

What this does to the meaning of "it went well"

The interview is a sample, and the sample is small. An interviewer telling you the interview went well is reporting their own experience of it, and it is not the variable the decision turned on.

That is not a reinterpretation invented to be kind. It is the account of the person who made the decision, describing a case where the conversation was genuinely good and the outcome bore no relation to it. Which means the inference "the interview went well, therefore I am a strong candidate" is not supported by the interview alone, and neither is the opposite inference from a bad one.

The uncomfortable part is that this cuts both ways, and the reverse reading is no more available. A rejection after a good interview is weak evidence about your ability, and so is an offer after a bad one. Neither tells you much, because the interviewer has just told you what else was in the room.

The one thing the interviewer suggests doing

The post offers practical advice rather than sympathy, and it is the same advice a recruiter gives elsewhere in this research: ask, at the start, which requirements are highest priority.

The interviewer suggests something close to this: "I have wide-ranging experience, but for this interview I'd love to focus in on what you're most interested in. From your list of job requirements, are there any you'd consider especially high priority that I should make sure to highlight?"

It is a reasonable thing to say. It also has a limit worth being honest about: it surfaces the priority if the interviewer knows and is willing to say so. It does not surface the internal candidate, the panel member's old colleague, or a role that was re-scoped last week. It addresses the first item on a list of five, and the first item is the only one on the list a candidate can act on.

Most of what can be prepared is already legible in the posting itself, which is the argument for reading the interview questions off the job posting. What is not in the posting is the priority ordering, and this is the one interview in five where you can ask for it.

A second reason, from outside the interview entirely

The filter is not only the conversation. Someone reviewing resumes for a client listed presentation patterns that decide whether a strong background is read at all: graduation years from the eighties or nineties left in, email addresses carrying a birth year, an AOL address. The author is careful to say this is about presentation rather than age, and notes the correlation without claiming it as cause.

It matters here for one reason: an application can fail before a conversation happens, and a candidate who never gets to the interview has no signal at all about why. That is the same silence problem the product exists for, in a different place, and it is the reason the tracker records a posting as never sent rather than counting it as an application.

What to take from a rejection

Not reassurance, and not a self-assessment. Two things that are cheap and usually skipped:

Record which stage ended it. Rejected at a screen, and rejected after a fifth round with the word "alignment" attached, are different events with different causes, and a list of forty is the only thing that makes the difference visible. That is the whole of what the product's search summary is: counts, and a statement that quiet is normal. It is arithmetic over your own applications, and it is absent rather than shown when there is not enough of it to mean anything.

Do not convert a process outcome into a verdict on yourself. The interviewer in this post rejected people they liked, on a colleague's favourite, for a role that had been written for someone else. The rejection reason is a sentence somebody had to type, not a finding about you.

And the honest limit: this is one interviewer's account, and one resume reviewer's list. Neither is a rate, and this product has started collecting its own rather than borrowing a number it would have to invent.

Related