What actually happens to your resume after you click apply

People picture one gate: a machine looks at the resume and says yes or no. That is not the shape of it. There are five steps, you can fail any of them, and the fix is different every time.

Step one: your file is turned into text

Whatever you uploaded, the first thing that happens is that software pulls the words out of it. Not the design. The words, in the order it thinks they come in.

This is where most of the real damage happens, and it is invisible to you because your copy still looks perfect on your screen. A parser generally reads top to bottom and left to right, which is fine until your layout disagrees. Two columns can be read straight across, so the end of one line joins the start of another. Table cells can be glued together. Content in a header or a footer is often skipped entirely, which matters a lot when your phone number lives there.

A resume that looks beautiful and parses badly is worse than a plain one that parses cleanly. The parse is the only version anybody downstream ever sees.

Step two: the text is sorted into fields

Next the system tries to work out which bit is your name, which is your email, where your jobs are and what your skills were. It leans on ordinary headings to do it. A section called Experience is easy. A section called My Journey So Far is a guess.

When this step goes wrong you end up in the database as a record with blank spaces in it. Nothing announces that. You just quietly stop matching things.

Step three: you are stored, and you sit there

Now you are a row. For a popular role there may be several hundred rows within a few days, sometimes a few thousand. Nobody is reading all of them, and nobody was ever going to.

Step four: a recruiter searches and filters

This is the step that decides most outcomes, and it is the one almost nobody optimises for. A recruiter types words into a box. Those words are the ones in their own head and in the job posting. Everyone whose record contains them comes back, in some order, and the rest may as well not exist.

So if the posting says Postgres and your resume only says SQL, you are not in that result set. Not rejected. Absent. This is the whole and unglamorous reason to mirror the language of the posting, and it is covered properly in how to use keywords without stuffing.

Some teams also set hard filters on the application form itself. Work authorisation, a required licence, a minimum qualification. Those really are automatic, they run before anybody reads anything, and your formatting has nothing to do with them.

Step five: a person skims what came back

Finally a human looks, and not for long. They are scanning for whether you plausibly match, how recent the relevant work is, and whether anything stands out. The top third of the first page carries most of that weight.

This is the step everybody writes advice about, and it is the last one. Being good at it does nothing if you fell over at step one or step four.

Working out which step is failing you

You cannot fix a problem you have not located. The symptoms do differ.

What this means in practice

Spend your effort in the order the steps happen, not in the order the advice is loudest.

1. 1.Make sure the file reads cleanly. This is cheap, takes minutes, and everything else depends on it.
2. 2.Use ordinary section headings so the fields fill in.
3. 3.Use the words the posting uses, where they are honestly true of you.
4. 4.Put your strongest, most relevant thing in the top third.
5. 5.Then apply to fewer roles, better matched. Volume is already working against you.