Latest / Career Coaching with Fexingo: Professional Coaches, Career Counselors, and Guidance for Workers / Why Your Resume Format Is Losing You Interviews
Transcript
- Lucas: If we've helped you think through a career move or decision, know that this show runs entirely on listener support rather than ads. A small group of you chips in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these conversations possible. Luna: It keeps the signal clean without corporate noise interfering with the advice. Thanks for keeping the lights on. Lucas: Let's dive in. Most professionals treat their resume as a literary document to be read by a human being. It is not. As of late September 2026, it is primarily data to be parsed by an algorithm known as an applicant tracking system. The gap between those two realities is where careers stall out. Luna: Right, because people spend hours polishing the narrative but ignore the syntax. Have you seen the rejection rates from poorly formatted files lately? Lucas: The data suggests that roughly thirty-five percent of qualified applicants are filtered out before a hiring manager ever logs in. That is not a typo. It is a structural failure of design, not a failure of skill. The ATS does not care about your clever headline or your creative layout. It cares about fields, dates, and keywords. Luna: So the danger isn't just looking bad, it's becoming invisible to the very first gatekeeper. What is the most common formatting sin you see right now? Lucas: Columns. Specifically, multi-column layouts in standard word processing documents. When you put text into columns, the parser reads left-to-right across the page. So if your skills section has 'Project Management' on the left and 'Strategic Planning' on the right, the system might read 'Project Strategic Planning Management'. It creates garbage data that fails keyword matching. Luna: That sounds like a nightmare for anyone trying to use a modern, aesthetic resume template. Do recruiters even realize they're losing good candidates over this? Lucas: Many don't. They think the ATS is a black box that magically finds talent. In reality, it is a rigid database. If the data doesn't fit the schema, it gets dropped. Think of it like filing taxes. You can write a beautiful memoir about your financial journey, but if the form isn't filled out in the exact boxes required, the government rejects it. Same logic applies here. Luna: I love that analogy. It makes the friction feel less personal and more procedural. Are there other visual elements that trip up the parsers? Lucas: Headers and footers. Designers love putting contact information in the header or footer of a document because it looks clean. But many older parsing engines simply strip those regions out. Your phone number and email address vanish from the parsed record. The recruiter sees a blank profile with no way to call you. Luna: So you could have the perfect experience listed, but if they can't reach you, you're effectively unemployed in their eyes. What about graphics? Like icons for proficiency levels? Lucas: Absolutely. Bar charts showing 'five stars' for Python coding? To the human eye, that is clear. To the parser, it is an image file containing zero text. The system cannot extract the skill 'Python' from a star rating graphic. It sees nothing. You must list the skill in plain text every single time. Luna: This feels like a harsh lesson in digital literacy. How do you balance clarity with personality when the machine demands blandness? Lucas: You separate the concerns. The resume is for the machine. The cover letter and the interview are for the human. Use the resume to pass the filter with precise, standard terminology. Then, use the interview to show your voice. Don't try to make the resume do both jobs at once. It will fail at both. Luna: So the strategy is essentially: optimize for the bot, then win the human. What about file types? Should everyone still be sending PDFs? Lucas: PDFs are tricky. A properly coded PDF preserves formatting, which humans love. But some legacy parsers struggle with them. The safest bet in 2026 is often a.docx file unless the application portal explicitly asks for a PDF. Check the instructions. If they say 'upload your resume', a docx is usually the path of least resistance for the backend system. Luna: That is such a simple tweak. Just checking the prompt instead of assuming the standard format. Does this mean all resumes should look identical? Lucas: They should look uniform. Standard headings like 'Experience', 'Education', and 'Skills'. No creative titles like 'My Journey' or 'What I Bring'. The parser looks for standard labels. If you rename a section, the parser might not recognize it as a work history block. Keep it boring. Boring works. Luna: Boring works. I wish I could tell my friends who spent weeks designing custom Canva templates to hear that. Is there any benefit to using keywords beyond the obvious ones? Lucas: Context matters. If the job description says 'customer success', don't just write 'support'. Write 'Customer Success Management'. Mirror the language of the posting. The ATS scores relevance based on lexical overlap. If the job requires 'stakeholder management' and you write 'client relations', you might lose points depending on how sophisticated the algorithm is. Luna: It feels like cheating, but it's really just translation. Translating your experience into the dialect of the employer. What about dates? I've heard horror stories about date formats causing rejections. Lucas: Yes. Ambiguity kills applications. Never write 'Jan 2020 - Present'. Write 'January 2020 – Present'. Some systems cannot parse abbreviated months. And avoid listing only years. If you list '2018-2020', a parser might calculate that gap as one year. If you leave a month off, it might calculate it as twelve months. Precision protects you from calculation errors. Luna: That level of precision is exhausting for someone already stressed about finding a job. How much time should someone realistically spend on this audit? Lucas: You should not be writing new resumes for every application. You should have one master resume, heavily loaded with keywords, and then trim it down for specific roles. The audit takes maybe twenty minutes. You check for columns, headers, standard headings, and date formats. Once that foundation is solid, you are safe. Luna: So the investment is upfront, and then it pays dividends across dozens of applications. What about the 'hidden' keywords? Things like soft skills? Lucas: Soft skills are harder to parse because they are subjective. 'Leadership' is a keyword. 'Team player' is vague. Instead of saying 'team player', describe a collaborative achievement. 'Led a cross-functional team of six engineers'. That gives the parser concrete nouns and verbs associated with leadership. Actions speak louder than adjectives. Luna: Actions over adjectives. That is a rule worth remembering. Does the industry matter here? Is tech more strict than creative fields? Lucas: Surprisingly, creative fields are stricter. Design agencies use heavy automation to filter thousands of portfolios. If your resume PDF has embedded fonts that the parser cannot read, you get auto-rejected. Finance and law are also extremely rigid. Startups might be more lenient, but they are moving toward standardized processes as they scale. Luna: So even if you think you're applying to a cool, relaxed company, they probably have a backend system that hates fun. Is there a tool to test this before hitting send? Lucas: There are free online parsers. Upload your resume, and see what text comes out the other side. If the output looks like a jumbled mess, your formatting is broken. Fix it until the parser outputs clean, logical blocks of text. It is the ultimate litmus test for machine readability. Luna: A sanity check for the machine. That seems like a powerful step that most people skip because they trust their own eyes. Why do we trust our eyes so much? Lucas: Because we are the audience for our own work. We want to impress the person reading it. But we forget that the first reader is code. Code does not have eyes. It has logic gates. You have to build for the logic gate first. Luna: Building for the logic gate. I need to start saying that. It changes the whole mindset from decoration to engineering. What about references? Should we include them on the resume? Lucas: No. References take up valuable space and are almost never requested in the initial screening phase. Save that page for later. Focus the limited real estate on achievements and metrics. Numbers are king. Quantified results survive parsing better than qualitative descriptions. Luna: Numbers survive. Because numbers are universal data types. Text can be interpreted differently, but a percentage increase is a percentage increase. This episode has been incredibly practical. Where should people go if they want to see an example of a 'broken' vs 'fixed' resume? Lucas: We link to a few resources in the show notes. Look for the before and after comparison. You will see the column issue immediately. It is shocking how much cleaner the data looks when you flatten the structure. Luna: And remember, the goal isn't to trick the system. It is to remove the friction so the system lets your actual talent through. If the barrier is lower, the opportunity is higher. Lucas: Exactly. Remove the barriers. Let the work speak. Next week, we will talk about how to handle the salary negotiation conversation after you finally get past that first gate. Stay tuned.