A rejected application is not a failed interview
An interviewer lists the reasons they did not hire someone who left believing the interview went well. Almost none were visible in 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 go far beyond 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 with "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 toward a field the team cannot use. The interviewer's phrase is ""for this particular role"."
- A hidden requirement nobody was told about. A position with no opportunities for advancement and where a candidate's obvious strength was the wrong thing.
Read the list as a whole. Four of the five are things the candidate could not have seen, and the fifth is a requirement that the posting did not specify. 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 size is limited. **An interviewer who tells you that the interview went well is describing their own experience; it is not the variable used to make the decision. **.
That is not a reinterpretation intended 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. In other words, the inference "the interview went well, therefore I am a strong candidate" is not supported by the interview alone, and neither is the inference that is the opposite of 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 of your ability, as is an offer after a bad one. Neither tells you much because the interviewer has already told you what else is in the room.
The one thing the interviewer suggests doing
This post provides advice that is more practical than sympathetic, and it is the same advice that a recruiter gives elsewhere in this research: **ask, at the outset, which requirements are the most important. **.
The interviewer proposes something like 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 that is worth being honest about: **it surfaces the priority if the interviewer knows and is willing to say so. ** It does not show the internal candidate, the panel member's former colleague, or a role that was re-scoped the previous 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.
The majority of what can be prepared is already legible in the posting, as is the case with reading the interview questions off the job posting. What is not in the posting is priority ordering, and this is the only interview out of five where you can request 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 emphasise that this is about presentation rather than age, and he acknowledges the correlation without claiming it is the cause.
It is important here for one reason: an applications can fail before a conversation occurs, and a candidate who never gets to the interview has no idea why. That is the same silence problem the product addresses, but in a different context, and it is why 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 overlooked:
Record which stage ended it. Rejected at a screen and rejected after a fifth round with the word "alignment" attached are two distinct events with different causes, and the only thing separating them is a list of forty different things. 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 candidates they liked based on a colleague's preference for a role that had already been written for someone else. The rejection reason is a sentence that had to be typed, not a discovery about you.
And the honest limit: This is an interviewer's account and a resume reviewer's list. Neither is a rate, so this product has begun collecting its own rather than borrowing a number that it would have to invent.
Related
- Five rounds, and a man in a car park, on a rejection whose stated reason was a process rather than a defect.
- Read the interview questions off the job posting, most of what can be prepared has already been listed in the posting.
- Stagger your applications, when spending the applications, you do not care about being bad at something first.