I Built a Proper Résumé in a Couple Hours (And Finally Got Past the Bots)

For years I assumed my résumé was fine. It looked sharp: two clean columns, a skills sidebar, a little color, a tasteful icon next to my email. People complimented it. So when applications went quiet, I blamed the market, the timing, the role being "already filled."

It turns out the problem wasn't my experience. It was that a machine read my résumé before any human did, and the machine couldn't make sense of it.

That machine is an Applicant Tracking System: Workday, Greenhouse, Taleo, iCIMS, Lever, and friends. Most mid-to-large employers run every résumé through one. It parses your file into fields, scores it against the job, and quietly filters out anything it can't read cleanly. The cruel part: you never find out. There's no bounce-back that says "your two-column layout scrambled and we couldn't find your job titles." You just don't hear back.

So I sat down one afternoon and decided to actually see what the bots see. A couple of hours later I had a résumé that was genuinely better. Not prettier, better. And I understood exactly why. Here's the walk-through.

Step 1: Watch a parser choke (≈10 minutes)

The first thing I did was the free, no-signup part: Audit the Bots at /audit. You upload one résumé and it runs three different parsing strategies over the same file (a naive line reader, the raw content-stream order, and a column-aware pass) and shows you how differently each one reads it.

My beautiful two-column layout? The three parsers gave three different answers. My job title ended up wedged between a skill and a date. That's the whole game right there: if the parsers disagree, your résumé is a coin flip every time you hit "Apply." Seeing it laid out like that was the moment it clicked. The layout I was proud of was actively working against me.

Step 2: See exactly what the bot extracted (≈15 minutes)

Next I ran a real check at /scan. Upload the PDF, and Past the Bots shows you "what the bot saw": the literal name, email, phone, links, skills, and sections an ATS pulls out of your file.

This is the report I wish every job site showed you. Mine had problems I'd never have guessed:

• My phone number got swallowed because it sat inside a graphic.
• A couple of skills I lead with weren't being extracted at all.
• One of my section headers was too "creative" to be recognized as Experience.

Every issue came with a plain-language fix and a critical/warning/ok flag, so I knew what was actually killing me versus what was cosmetic. No jargon, no "optimization score" mystery meat. Just "here's what's broken and here's why."

Step 3: Match against a real job (≈20 minutes)

Then I pasted in an actual job description I was targeting. (You can paste the link too, and it'll fetch and pull the text out for you.) Past the Bots gives you a skill-weighted match score, the keywords you matched, the ones you're missing, and any hard knockout gaps: the must-haves a system will reject you on outright.

This is where I stopped guessing. I could see, concretely, that the posting leaned hard on a few terms my résumé technically earned but never actually said. Not buzzword stuffing. I genuinely had the experience; I'd just described it in different words than the job did.

Step 4: Rebuild it, truthfully (≈30 minutes)

Here's the part that earns the word "proper." With the Job-Hunt Pass, the AI tailoring rewrites your bullets to line up with the job, but it has a hard rule I really respect: it never fabricates experience. If a keyword isn't supported by what's actually on your résumé, it doesn't get bolted into a bullet. It gets surfaced as a gap you can decide to address honestly. No inventing a skill you don't have. No lying to a robot and then having to defend the lie in an interview.

On top of that, it generated a clean, single-column ATS-safe rebuild (the same content, reordered into the structure parsers expect), plus a tailored cover letter and a short recruiter outreach message. I exported the rebuild straight to .docx, tweaked two lines in Word to sound more like me, and that was it.

Step 5: Verify the fix (≈10 minutes)

Last thing: I ran the new version back through the scanner. Phone number: detected. Skills: all there. Sections: mapped cleanly. Match score on my target role: up substantially, and for the right reason: I was now saying the things I'd actually done.

Total time, including me overthinking the wording: about two hours.

What I actually learned

A few things stuck with me:

1. "Looks good" and "parses well" are different sports. Multi-column layouts, text trapped in images, fancy tables, and clever section names are exactly the stuff that breaks ATS parsing. The plainer file usually wins.
2. You're often filtered for fixable reasons, not for fit. Mine was a buried phone number and a few unspoken keywords. That's not a career problem; that's a formatting problem.
3. Tailoring honestly beats tailoring desperately. The strongest version of my résumé wasn't padded. It just described my real work in the language the role used.

I'm biased (I work on Past the Bots), but I built it because I needed it, and this afternoon was the proof. If your applications have gone quiet, don't assume it's you. Go run the free audit at /audit and watch what the bots actually do with your file. Worst case, you learn your résumé is rock-solid. Best case, you find the invisible thing that's been filtering you out for months and you fix it before lunch.

A proper résumé didn't take me a new career, a coach, or a week of agonizing. It took a couple of hours and the ability to finally see the bot's-eye view.

Try it free, no signup for the audit, at pastthebots.com.