pirch › resume guide › part one
part one — what you're up against

what actually happens after you hit submit

not to scare you — to orient you. once you see the pipeline, every résumé rule you've ever heard either starts making sense or turns out to be junk.

part 1 of 5

you spent an evening on it. you found the posting, tuned the wording, attached the file, hit submit — and then, very often, nothing. before you rewrite a single line, it's worth knowing exactly what happens in the machinery on the other side of that button. it's less mysterious than it feels, and less hostile too. mostly, it's just indifferent — and indifference is something you can design for.

a parser reads the file
software converts your résumé into database fields: name, title, employer, dates, skills. this takes about a second, and it's where most damage happens — not by rejection, but by mangling. a two-column layout, a text box, a skills chart: the parser doesn't reject them, it scrambles them, and nobody tells you.
you become a row in a database
your application sits alongside everyone else's. nothing has judged you yet. whether anyone ever finds this row is what the next two steps decide.
a search happens — or doesn't
recruiters search the database the way you search anything: by words. the words they use come from the job description they wrote. if your résumé says what you did in your words but never in theirs, the row exists and no search ever returns it.
a human skims — in seconds
the first human look at a résumé is measured in seconds, not minutes. it's a sort, not a read: current title, current employer, a scan for the thing they need. this pass decides whether you reach the maybe pile.
the maybe pile gets the minutes
only now does someone actually read the thing you wrote. everything in parts two and three of this guide exists to get you here — where the writing finally matters.

so: two readers, two jobs

everything that follows comes down to this. your résumé has exactly two readers, and they want different things:

the machine wants structure it can parse — one column, real text, headings it recognizes, your work described at least once in the words the job posting actually uses.

the tired human wants a reason — fast. something in the first five lines that says this person changed something somewhere, and it's the kind of change we need.

the good news: these two jobs never conflict. the format that parses clean is also the format that skims fast. the writing that survives a search is also the writing that lands in seconds. you never have to choose between the robot and the person — you just have to stop writing for neither, which is what most résumés do.

one more thing before part two: not every silence is about you. a chunk of listings have no live hiring behind them at all — we wrote a whole field guide to spotting ghost jobs, and the math on why 200 applications can produce zero replies. read those when the silence starts feeling personal. it usually isn't.

the danger isn't a robot saying no. it's your best work parsing into mush — so nothing ever says yes.

why format matters before words do
part one, in one breath

parse clean. give the human a reason. that's the whole game.

the pipeline is a parser, a database, a search, and a skim. format so the parser keeps your meaning (part two). write so the search finds you and the skim stops on you (part three). everything else is decoration.

← the guide
all five parts