The Candidate File

The Candidate File: What They Write About You After You Leave the Room, and How to Read It

You close the laptop, exhale, and replay the whole thing for about forty minutes. Was that pause too long? Did that joke land, or did it belly-flop in front of four people on a grid?

Meanwhile, on the other side of that call, something more consequential is happening. Someone is typing. Scores are going into boxes, a hiring manager is leaving a comment, and a recruiter is writing two sentences that will outlive your memory of the entire conversation.

A record of you is being created, and it is the version of you the company will actually keep. Then the rejection email arrives, and it says almost nothing. “We’ve decided to move forward with other candidates.” Cool. Thanks. Extremely illuminating.

Here is the part most candidates never find out: that record is not sealed, and in many cases you have a legal right to read it.

Your Interview Notes Are Data, and Data Has Rules

Under the General Data Protection Regulation (GDPR), information relating to an identifiable person is personal data, and that definition is broader than people assume. It is not just your name, email, and phone number. It includes opinions about you.

That means interview scorecards, panel feedback, recruiter comments, the reason code someone selected when they moved you to rejected, and the free-text box where a hiring manager typed what they really thought can all fall within your right of access.

You submit a subject access request, and the organization is generally required to respond within one month, extendable by two more if the request is genuinely complex. It should not cost you anything.

The rule applies to organizations processing the data of people in the EU and UK, which in practice sweeps in a very large share of internationally hiring companies, including plenty headquartered elsewhere. Remote hiring has quietly made this far more relevant than it was five years ago.

What People Actually Find in There

This is where it stops being a compliance footnote and starts being genuinely interesting.

Candidates have used access requests to discover that the interview panel recommended them and someone further up the chain overruled it.

Others have found that a decision hinged on a single throwaway remark, or on a scoring rubric where they lost points on a criterion nobody mentioned during the process. Some have found notes that were simply wrong, recording an answer they never gave.

It is not always dramatic. Often you get a scorecard, some numbers, and a sentence like “strong technically, concerns about seniority.”

But even that is worth more than the standard rejection template, because “concerns about seniority” is something you can address in your next twelve applications. “We’ve decided to move forward with other candidates” is something you can only stew over.

The real value is diagnostic. You stop guessing which part of your performance is costing you, and you start knowing.

What They Can Keep From You

Not everything comes back, and it helps to know the limits before you ask, because unrealistic expectations are how these requests turn sour.

Organizations can redact information that would identify other people, so a comparison between you and another candidate will usually arrive with the other person’s details stripped out.

They can withhold material covered by legal privilege. Notes so scribbled and unstructured that they were never filed anywhere may fall outside a request in some circumstances, though the modern reality is that most hiring now happens inside an applicant tracking system, and anything typed into that system is very much on the record.

They can also push back on requests they consider excessive or repetitive. One clear, polite request is fine. A campaign is not.

How to Actually Send One

Keep it short and unmistakably a subject access request, since vagueness invites delay.

Email the company’s data protection officer or privacy contact, which is usually listed in the careers page privacy notice.

State that you are making a subject access request under the GDPR, identify yourself and the role you applied for, and ask for all personal data held about you in connection with that application, specifically including interview notes, assessment scores, and internal correspondence referring to you. Give a date range. Ask them to confirm receipt.

Then wait. The clock starts when they receive it.

While you are waiting, keep applying, because a pending request is not a strategy. Platforms like Jobs Hub exist to keep that pipeline moving, and momentum matters far more to your outcome than any single company’s opinion of you does.

Should You Do It Every Time? Probably Not

Let us be honest about the social physics here. A subject access request is a legal instrument, and using one on a company you desperately want to work for next year is a bold move.

Save it for the cases where it earns its keep. A late-stage rejection you cannot explain. A process where the feedback contradicted itself. A situation where you suspect something went wrong that had nothing to do with your ability. Those are the moments where the file tells you something you could not otherwise learn.

For a first-round no, let it go and spend the energy on the next application.

The Point Is Not the Paperwork

The point is that hiring feels like a black box because candidates have been trained to accept that it is one. It is not entirely. There is a written record, it describes you, and the law gives you a door into it.

You may never need to walk through that door. But knowing it exists changes how you carry yourself through the process, and that alone is worth the five minutes it took to read this.

#JobSearch #InterviewTips #GDPR #CandidateRights #Recruitment #CareerAdvice #HiringProcess #JobsHub