Latest / The Resume Room with Fexingo: Resume Writing, Cover Letters, and Application Strategy / How to Audit Your Resume for ATS Failure
Transcript
- Lucas: We spend hours polishing the narrative of our careers, refining every bullet point until it sings, but then we hit a wall that has nothing to do with talent. It is the invisible gatekeeper, the Applicant Tracking System, and today we are going to talk about how to make sure your resume actually passes through it. Luna: Right, because if the software cannot read you, you simply do not exist to the hiring manager, no matter how impressive your background is. Lucas: Exactly. And I want to look at a specific case from last week where a senior operations director named Elena applied for a role at a mid-sized logistics firm. She had twelve years of experience, managed a team of forty people, and cut costs by fifteen percent year-over-year. On paper, she was perfect. Luna: So why did she hear nothing back? Lucas: Because her resume was designed like a brochure. She used two columns, embedded graphics in the header, and saved it as a PDF with complex text boxes. The ATS parsed that document, saw a jumbled mess of non-sequential text, and essentially auto-rejected it before anyone clicked on it. Luna: That is terrifying when you think about it. A perfectly qualified candidate eliminated by a formatting choice. Lucas: It is common enough that we need to treat resume writing as a technical exercise in data entry, not just creative writing. The first thing to check is the file format. While many modern systems can handle PDF, a simple Word document or a plain-text version is always safer because it forces the parser to rely on standard character codes rather than trying to interpret visual layers. Luna: I have heard people say they should never use headers or footers either, because some parsers skip those areas entirely. Lucas: That is correct. Contact information in a header might get buried. You want your name, phone number, and email in the main body of the document, top-left aligned. Simple. If the system cannot find your phone number in the first three lines, it might flag your application as incomplete. Luna: And what about those fancy icons for contact details? Like a little envelope icon next to your email? Lucas: Avoid them completely. To the parser, an icon is just an image. It reads zero characters. So instead of seeing an email address, it sees a blank space. You need to spell out your contact info in full, standard text. Luna: So the goal is maximum compatibility over maximum aesthetics. Lucas: Precisely. Once you secure the file format and the basic structure, we move to the skills section. This is where most candidates fail to optimize for keyword matching. If the job description asks for 'project management' and you write 'managed projects,' the algorithm might miss the connection. Luna: So you want to mirror the exact terminology from the posting, even if it feels repetitive? Lucas: You mirror the core terms. If they ask for 'Python,' do not just say 'coding.' If they want 'stakeholder engagement,' do not just list 'client relations.' Use the exact phrases from the job description in your skills list, assuming you genuinely possess those skills. Luna: It sounds mechanical, but it is necessary to beat the initial filter. Lucas: It is mechanical until it gets to the human. And here is the tricky part: the human reader wants personality, but the machine wants precision. You have to balance both. We see so many people using complex fonts or unusual color schemes to stand out, which only guarantees they will be filtered out by the machine. Luna: Is there a safe font size range we should stick to? Lucas: Between ten and twelve points for the body text. Anything smaller than ten becomes hard to read for humans and sometimes difficult for older parsers to recognize clearly. Stick to standard fonts like Arial, Calibri, or Times New Roman. Do not use custom fonts unless you are absolutely certain of the recipient's technology stack. Luna: What about tables? People love using tables to align dates and titles neatly. Lucas: Tables are another major trap. Many parsers read left-to-right across the entire page, ignoring the grid structure. So if you have a table with 'Company Name' in column one and 'Dates' in column two, the parser might merge them into 'Company Name Dates' as a single line of text, ruining the chronology. Luna: That would completely scramble the work history section. Lucas: It would. Use tabs or simple spacing instead. Keep the layout linear. Name, Title, Company, Location, Dates. All on one line or clearly separated blocks. Linear data is easy data for a machine to consume. Luna: This brings up a good point about the summary statement. Should that include keywords too? Lucas: Yes, but sparingly. The summary is your elevator pitch. It should contain your top three or four hard skills and your professional identity. But do not stuff it with jargon. Write for the human who will read it after the machine approves it. If it sounds robotic, the human will bounce. Luna: So the resume serves two masters: the algorithm and the person. Lucas: Always. And the algorithm is the bouncer. If you do not pass the bouncer, you never get to the party. That is why we recommend doing a dry run. Take your resume and paste the raw text into a plain text editor like Notepad. If it looks like gibberish or loses all its structure, the ATS will likely see the same thing. Luna: That is such a practical test. I never thought to strip the formatting just to check readability. Lucas: It reveals exactly how much visual design is hiding behind the content. If the text flows logically without the styling, you are in good shape. If it jumps around, you need to restructure the document elements. Luna: Let us pause here for a moment to talk about how we keep this show running. Lucas: We appreciate every listener who tunes in daily to navigate these career complexities. If today was worth a coffee to you, that is the link — buy me a coffee dot com slash fexingo. It helps cover the costs of production and keeps the episodes coming ad-free. Luna: Thank you for supporting the network. It allows us to keep digging into these specific strategies for you. Lucas: Back to the resume. Once you have optimized for the ATS, you still have to deal with the human review. And that is where the narrative comes back in. Luna: After surviving the robot, you have to impress the recruiter. Lucas: Right. Recruiters spend about six seconds scanning a resume initially. They are looking for patterns, consistency, and impact. If your resume is ats safe but boring, you lose them here. You need quantifiable achievements, not just duties. Luna: So instead of saying 'responsible for sales,' you say 'increased regional sales by twenty percent.' Lucas: Exactly. Numbers grab attention. They provide proof. And they are generally safe for the ATS to parse as long as you write them out clearly, like 'twenty percent' or '20 percent,' rather than using obscure symbols. Luna: What about the order of sections? Does that matter for the human scan? Lucas: For most corporate roles, reverse chronological order is the standard. It shows stability and progression. Functional resumes, which group skills by category rather than time, are often viewed with suspicion by recruiters because they can hide employment gaps or job-hopping. Luna: So stick to the timeline unless you have a very specific reason to deviate. Lucas: Unless you are changing careers entirely, in which case a hybrid approach might work. But even then, anchor it in dates. Humans crave context. They want to know when you did what, and how long you stayed. Luna: And what about references? Should we put 'references available upon request' at the bottom? Lucas: Do not waste the space. Any employer asking for references will request them later in the process. Using that line just takes up valuable real estate that could be used for more skills or project details. Luna: Efficiency is key. Every inch counts. Lucas: It does. And finally, proofreading. A typo in an ats optimized resume is doubly bad. The machine might miss it, but the human will see it immediately and question your attention to detail. Always read it backward, or have someone else read it aloud. Luna: Because if the software lets you through, the human is judging everything you wrote. Lucas: Precisely. You have cleared the first hurdle. Now you are on stage. Make sure your performance matches the preparation. Luna: So the takeaway is simple but rigorous: design for the machine first, then polish for the human. Lucas: Design for the machine to survive, and design for the human to win. If you can do both, you are already ahead of ninety percent of applicants. Luna: A quiet victory, but a powerful one. Lucas: Indeed. The best resume is the one that opens the door. Everything else happens after that.