Latest / The Resume Room with Fexingo: Resume Writing, Cover Letters, and Application Strategy / How to Fix a Resume That Gets No Interviews
Transcript
- Lucas: You know what drives me crazy? I see people spending forty-five minutes on font selection for their resume. Like, does anyone really care if you use Calibri versus Garamond? Not anymore. Luna: Right? It’s like painting the walls of a house that has no foundation. The problem isn’t the paint, it’s that the door won’t open. Lucas: Exactly. And today we are talking about that door. Specifically, the Applicant Tracking System, or ATS. This is the software middleware that sits between you and the hiring manager. If you don’t speak its language, you’re invisible. And here is the kicker: most candidates think they are writing for a person, but they are actually writing for a database. Luna: It feels dehumanizing, doesn’t it? Writing something that has to be decoded by an algorithm before a human ever sees your face. Lucas: It is dehumanizing, but it’s also just logistics. Large companies receive thousands of applications. A human cannot read them all. So they set up filters. Keywords, dates, degree types. If your resume doesn’t match the pattern, it gets auto-rejected. I want to walk through a specific case from last week where we fixed a candidate’s profile, and the results were immediate. Luna: I remember that one. She was a senior project manager, highly qualified, but getting zero responses after applying to thirty roles. Lucas: That’s right. Her name is Elena. She had been sending out polished, beautifully formatted PDFs with columns, icons, and even a small photo header. Beautiful design. Completely useless for the ATS. When she applied, the system couldn’t read the layout, so it saw a blank page. We rebuilt her resume from scratch, focusing entirely on structure and keyword density. Luna: So the first step is realizing that design is the enemy of retrieval. Lucas: Precisely. The first rule of ATS optimization is simplicity. Single column. Standard headings. No graphics. No tables. No text boxes. You want your document to look like a plain text file that happens to have some bolding. Why? Because the parser reads left to right, top to bottom. If you put your skills in a sidebar, the parser might miss them entirely or jumble them into the wrong context. Luna: It’s funny because candidates obsess over aesthetics, but the machine only cares about sequence and clarity. Lucas: And sequence matters more than you think. Let’s talk about keywords. This is where most people make the mistake of 'keyword stuffing.' They take a list of buzzwords from the job description and paste them at the bottom of their resume. But modern ATS algorithms are smarter than that. They look for context. They want to see those keywords used naturally within your bullet points, not just listed in isolation. Luna: So instead of listing 'project management' as a skill, you have to show it in action? Lucas: Yes. For example, Elena’s original resume said: 'Skills: Project Management, Agile, Scrum, Budgeting.' Generic. Vague. Our fix was to rewrite her experience bullets to say: 'Led cross-functional teams using Agile and Scrum methodologies to deliver projects under budget.' Now the system sees 'Agile' and 'Scrum' connected to actual leadership outcomes. It’s not just a tag; it’s proof of competency. Luna: That’s such a subtle shift but it completely changes how the data is indexed. Lucas: It does. And there is another trap people fall into: acronyms. Should you write 'Search Engine Optimization' or 'SEO'? Or both? The best practice is to use the full term first, then the acronym in parentheses. So, 'Search Engine Optimization.' This covers both bases. If the recruiter searches for the full phrase, you show up. If they search for the shorthand, you still show up. Luna: It’s basically hedging your bets against different search behaviors. Lucas: Exactly. But let’s go deeper. There is a specific type of resume failure that happens when people use non-standard job titles. If your company calls you a 'Ninja Coder,' but the job description asks for a 'Software Engineer,' the ATS might not match them. You need to translate your title for the market, not just keep your internal corporate branding. Luna: Is it ethical to change your title on a resume if it’s different from your official HR record? Lucas: It is ethical if the new title accurately reflects the scope of the work. If your official title was 'Customer Success Wizard' but you were managing a team of twelve analysts, putting 'Team Lead, Customer Success' on your resume is honest translation. You are helping the reader map your experience to their mental model. Just don’t lie. Don’t say you were a VP if you were a director. The background check will catch that. Luna: Okay, so we’ve covered layout, keywords, and titles. What about the summary section? Everyone writes these long, fluffy paragraphs about their passion. Lucas: Avoid that. The summary is prime real estate, but it should be a data dump, not a poem. Think of it as a metadata block. List your core competencies, your years of experience, and your industry focus. Keep it tight. Three to four lines max. The goal is to give the parser enough context to categorize you correctly before it moves on to your work history. Luna: It’s almost like treating the summary as a tag cloud rather than a narrative hook. Lucas: A tag cloud is a great way to think about it. Now, let’s pause here for a second. If we’ve helped you think through a career move or decision, consider supporting the show. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo. It helps us cover the time spent researching these trends so we can bring you better insights every day. Luna: Yeah, it makes a real difference in keeping the research deep and the advice practical. Lucas: Thanks for that. Anyway, back to the technical side. Once you have your content optimized, you need to think about file format. This is a huge point of confusion. Should you send a Word document or a PDF? Luna: I always thought PDF was safer because it preserves formatting. Lucas: PDF is safe for humans, but it can be risky for older ATS systems. Some parsers struggle with PDFs, especially if they are scanned images or complex layouts. The safest bet is usually a.docx file. It’s the native language of Microsoft Office, which powers most legacy recruitment software. Unless the job posting specifically says 'PDF preferred,' stick to Word. Luna: That is a surprising reversal of the usual tech advice. Lucas: It is. Technology lags behind common sense. But wait, there is one more layer. Even if your resume passes the ATS, you might still get rejected because of 'date gaps.' Modern systems flag any employment gap longer than six months as a red flag. So how do you explain a gap without looking suspicious? Luna: Do you just hide the dates? Or do you explain it in the resume itself? Lucas: Don’t hide it. Address it. If you took time off for caregiving, education, or health, you can list that period as 'Independent Study' or 'Professional Development.' Include relevant courses, certifications, or volunteer work. It shows you stayed engaged. The goal is to show continuity of growth, not just a blank space on the timeline. Luna: So you frame the gap as a deliberate choice rather than a passive void. Lucas: Exactly. Control the narrative. Now, let’s talk about the final piece of the puzzle: the cover letter. Many people think cover letters are dead. They aren’t. They are just different. The resume is for the bot. The cover letter is for the human who eventually sees your file. Luna: So the cover letter is where you add the color that the resume strips away? Lucas: Yes. Use the cover letter to explain the 'why.' Why this company? Why now? Connect your dots in a narrative way that the resume’s bullet points can’t. If you have a gap or a career pivot, the cover letter is the place to tell that story with nuance. The resume lists the facts; the cover letter provides the context. Luna: It’s interesting how the two documents complement each other so perfectly. Lucas: They are a team. One gets you in the door; the other gets you the interview. Let’s circle back to Elena. After we made these changes, what happened? Luna: She didn’t just get one interview. She got three in two weeks. From companies she had been ignored by for months. Lucas: Because she stopped trying to impress a designer and started speaking to the system. She aligned her keywords, simplified her layout, and clarified her title. It wasn’t magic. It was mechanics. The market is competitive, but it is also predictable if you understand the rules of engagement. Luna: It’s a reminder that sometimes the most creative thing you can do is be boringly clear. Lucas: Boringly clear wins. Clarity is kindness, especially when you are asking someone to hire you. If you are stuck in the black hole of online applications, stop tweaking the font. Start auditing your keywords and structure. Luna: Try the simple, single-column, keyword-rich approach. See if the phone starts ringing. Lucas: Give it a shot. And if it works, let us know. We love hearing from listeners who turn things around. Luna: Until next time, keep your resumes clean and your narratives strong. Lucas: Good luck out there. You’ve got this.