What a 45-minute interview is actually costing you
One measurement of what an interview process costs a candidate, taken from a single reply in someone else's thread.
- interview process
- job search
- time cost
- hiring
Nobody counts their applications, but everyone counts their hours. That's backward because the applications are almost free, but the hours are not. A candidate can send out 200 applications without spending more than a week on them. The process on the other side of that sends you somewhere for a day, sometimes more than once, and there is no way to opt out of the parts you cannot see.
The one measurement in twenty-one threads
The author applied for IT Helpdesk Support at a small company, and "literally asked for the same salary" they had asked for before. They interviewed with seven different people in person, plus a phone screening, eight in total, and one of those people did a further phone call after the phone screening. Three rounds. The in-person interview included the other two helpdesk people, the IT director, the DevOps manager, the infrastructure manager, the HR manager, and the COO. It was broken into four different groups, some questions repeated across different people.
They walked out "feeling defeated". They also got the job, which turned out to be the best company they'd ever worked for.
Read those two facts next to each other. The same day, the same interview produced the impression that it had gone badly and the outcome that it had gone well. Whatever an interview feels like on the inside and what it decides are not the same variable, and the distinction between the two is what makes a search difficult to reason about.
What it actually cost
Three or four hours in a room, plus travel each way, plus a phone screen, plus a second call. For a position advertised for around 65k at one of the smaller companies in its market rather than a large employer with a formal process.
Multiply that by the size of a typical search. A candidate with thirty applications might have six interviews in them. At four hours each, that is a day and a half in rooms, before travel, before the phone calls, before the waiting. A candidate with a hundred applications and a ten per cent interview rate has ten, which is three or four days of their life spent sitting in other people's offices being asked about a GPA.
None of that is visible in a tracker that counts applications. An application is a row. An interview is a row. The number that is actually large, the one that competes with a job, with a course, with a life, does not appear anywhere.
What to do about it
Not much, and the honest answer is that the hours are mostly fixed. What can change is how many of them you use.
Count the hours once, properly, and then stop counting applications. The arithmetic above is straightforward, and it is the only version of the question worth asking: how many interviews have you had, how long each one lasted, and how much they added up to. A candidate who has never done this has no idea, and the result is usually higher than expected.
Use it as a limit rather than as a score. The person who posted it came away feeling defeated from a process that went well for them. An interview that exhausts you is not proof that you performed poorly, and treating exhaustion as a verdict is how a lengthy process yields a quick result.
Set the threshold in advance. The three-interview limit that appears elsewhere in this research is the same idea as a rule about information. Beyond a certain depth, additional rounds are costing you a day and telling you something you can act on. Deciding that in advance is cheaper than deciding it at round five, having already paid for rounds one to five.
Notice the shape of the process, not just its length. Four groups, some questions repeated, a COO in the room for a helpdesk position. A process that repeats itself is one that was designed around a template rather than the role, which tells you something about what the round is measuring.
What this product does with it
The tracker keeps track of the stages a candidate reported going through per application, and the search summary adds them all up: sent, replied, interviewing, offers, rejected, and how long the silences lasted.
That is a count of stages rather than a count of hours, and the difference is deliberate. Converting stages to hours would require inventing a duration for a stage that the product has never seen, and an invented duration is precisely the type of number that this product refuses to generate. The honest version is the one above: count your own hours once, because only you know them.
And the same reason applies to the comparison the product will not make. It is not going to tell you that your search is going well, because there is no baseline to say so against.
The limit of this, stated plainly
This is one reply in someone else's thread. It is not a study, not a sample, and not something that can be checked. It is the only measurement of what an interview process costs a candidate in the whole corpus this product was built from, and one data point is not a rate.
What survives that limit is narrow and still worth having: the hours are larger than the application count suggests, they are invisible in the tools candidates use, and the same interview can feel like a failure and turn out to be successful. These are arithmetic and experience rather than statistics, and they are the reasons the tracker exists.
Related
- Five rounds, and a man in a car park is in a process where the last conversation lasted twelve minutes.
- A rejected application is not a failed interview, on what the people making the decision say actually happened
- Stagger your applications, when spending the applications, you do not care about being bad at something first.