What if Your CV Was Fifty Pages Long?

I was staring at my own CV next to a job spec last week, two single pages side by side, and neither one had much to do with the actual job or the actual me. Mine was a tidy summary of twenty-odd years, compressed down to bullet points that survive a two-minute scan (the two minutes is generous, if we’re honest). Theirs was a tidy summary of a role, compressed down to the same shape. Two index cards, each standing in for something far bigger, being matched against each other like we’re back in a post-war job-queue office deciding who gets sent where.

Why one page, though?

The one-page rule was never really about content. It was about the reader. A hiring manager has a stack of CVs and about ninety seconds each, so the format evolved to survive that constraint: the bullet points, the single page, the “relevant experience” section doing the work of ten years in four lines. Dense, not because density is good, but because a tired person skimming a pile needed it that way.

Except that reader is increasingly not a person. Plenty of CVs now get read first by a model: screened, ranked, shortlisted, before a human ever opens the file. And a model doesn’t get tired at CV forty. It doesn’t skim out of boredom on a Friday afternoon. So here’s the thought experiment. If the thing doing the first read can actually process fifty pages as easily as one, why are we still writing for the reader who needed it short?

The case for going long

Give the model everything. Every project, every judgement call, every time you made the wrong decision for a defensible reason. The stuff that never survives the one-page cut because it doesn’t compress into a bullet. It’s exactly the stuff that tells you what someone’s actually like to work with. A one-pager can tell a model you “led a cross-functional team.” Fifty pages could show it the three times that team nearly fell apart and what you did about it.

The case against

You’d be handing over a huge amount of yourself to a system you don’t control and can’t audit. That throwaway anecdote on page forty about a project that went sideways is fine as colour in a long document, but it’s now sitting in someone’s model, ready to resurface as a loaded question in round three of an interview you didn’t see coming. And there’s a sharper problem underneath: if nobody actually reads all fifty pages, you haven’t removed the compression. You’ve just moved it onto whatever summary the model produces for the human at the end of the chain. You’re not writing for the reader any more. You’re writing for the thing that writes the memo for the reader, which is a stranger job than it sounds.

That’s the bit I keep circling back to. The one-page CV was a document calibrated to its reader’s limits. A fifty-page one would be calibrated to the absence of limits, which sounds freeing right up until you remember that somewhere at the end of the chain, a human still has to decide whether to call you.

So who’s actually reading it?

Here’s where I get stuck, because there isn’t one answer any more. There are three kinds of employer now, and they want different documents.

A large organisation runs what chess players would call a centaur process: the model does the reading, a person makes the call, and nobody in that chain ever opens the raw file. Fifty pages costs them nothing. If anything it’s what they’d prefer, because their scoring has somewhere to look.

A ten-person company has no recruiter and no screening software, just a founder going through applications on a Sunday evening between two other jobs. That is exactly the tired reader the one-page rule was built for, still sitting there, unchanged. Fifty pages doesn’t read as thorough to them. It reads as rude, and it doesn’t get read.

The third case is the one I find genuinely interesting. The same founder pastes your CV into a chat window and asks what it thinks. Now they have a centaur process too, but with none of the apparatus: no scored criteria, no consistency across candidates, no record of why anyone was dropped. Just whatever a model said about you on one reading, delivered to someone who will weigh it like a colleague’s opinion. Small organisations are getting the large-organisation reading without any of the large-organisation process, and nobody decided that. It just arrived.

There’s a legal question sitting under that one too, and I don’t think it has been properly tested. A CV is personal data about somebody else. The moment a founder pastes it into a consumer chat product they are a controller, handing a candidate’s employment history, and usually their address and phone number, to a processor they hold no contract with, for a purpose nobody told the candidate about, into a product whose terms may well allow the input to be kept or trained on. The large organisation’s screening vendor has a data processing agreement, a retention schedule and an impact assessment, because procurement made them produce all three. The founder has a browser tab. So the more manual and less resourced the process, the less of the paperwork exists, which is the reverse of how I’d have guessed it would go. Copy and paste has its own data security problems, and they are nobody’s job to fix.

So: no idea. You can’t tell from the outside which of the three you’re posting into, you can’t tell where the document ends up afterwards, and one document can’t be right for all of them. The thing that’s changed isn’t the page count. It’s that the CV stopped being one document with one reader, and nobody has written the second version yet.