Latest / The Resume Room with Fexingo: Resume Writing, Cover Letters, and Application Strategy / Why Your Resume Is Ignored By Hiring Algorithms
Transcript
- Lucas: Let's talk about the single most frustrating part of the modern job hunt: the black box. You send out a perfectly crafted application, you tailor the cover letter, you hit submit, and then... nothing. Not even an auto-rejection email. Just silence. It feels like shouting into a void. Luna: It is maddening. I applied to three roles last week that felt like a perfect match, and I got zero responses. Did you ever wonder if there is actually a person reading those resumes? Lucas: The uncomfortable truth is that in many mid-to-large sized companies, there often isn't a human looking at your resume for at least the first thirty seconds. There is an algorithm. An Applicant Tracking System, or ATS, sitting between you and the hiring manager. And right now, as of October tenth, two thousand twenty-six, these systems are getting smarter, but they are also getting more aggressive about filtering. Luna: So it's not that our resumes are bad, it's that the gatekeeper is invisible? That changes everything about how we should be writing them. Lucas: Exactly. And this brings us to today's topic: the invisible audit. We have covered formatting and storytelling, but we haven't really drilled into the technical reality of how these systems parse language. The old advice was to stuff keywords everywhere. But recent data from LinkedIn shows that simple keyword stuffing is actually hurting candidates because the algorithms are now checking for context, not just presence. Luna: I remember reading that some recruiters can spot a resume that has been 'gamed' by AI or keyword tools instantly. It looks robotic. Lucas: It does. And here is the specific thing I want us to focus on today: semantic relevance. The system doesn't just look for the word 'project management.' It looks for the concept of project management demonstrated through specific actions and outcomes. If you list 'project management' next to 'social media scheduling,' the algorithm might flag you as irrelevant because the context doesn't align with the seniority level of the role. Luna: That is a really subtle distinction. So instead of just listing the skill, you have to prove you used it in the right environment? Lucas: Precisely. Let's look at a concrete example. Say you are applying for a Product Manager role. A traditional resume might say: 'Managed product roadmap, increased user engagement by ten percent.' Simple enough. But an advanced ATS in twenty twenty-six is looking for the infrastructure behind that. Did you use Jira? Did you work with engineering sprints? Did you analyze SQL queries? If those contextual words aren't there, the system might rank you lower than someone who didn't increase engagement quite as much but clearly spoke the technical language of the team. Luna: So it's less about being clever and more about speaking the exact dialect of the department you are trying to join. Lucas: It's about signal clarity. Think of the ATS as a very literal, slightly paranoid assistant. It is trying to protect the hiring manager from wasting time. If your resume is ambiguous, the assistant assumes risk and filters you out. Now, before we get too deep into the weeds of syntax, I want to pause for a quick moment. If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, we know how time-consuming job hunting can be, so keeping this resource free and accessible is really important to us. Thanks for supporting the show. Lucas: Thanks. Now, back to that semantic relevance. Because if you are listening to this, you are probably already doing the hard work of tailoring your resume. But are you tailoring it for the machine or for the human? The answer is both, but in a specific order. Luna: Right, because if the machine doesn't let you through the door, the human never gets to see how good your story is. Lucas: Exactly. So here is the actionable strategy I want you to try. Take your target job description and highlight every noun that represents a tool, a methodology, or a specific type of outcome. Then, go through your resume and ensure that those nouns appear in the same grammatical context. Don't just list them in a skills section at the bottom. Weave them into your bullet points. Luna: Like, instead of just saying 'Improved sales,' you'd say 'Used Salesforce CRM to track leads and improve sales by fifteen percent.' Lucas: Yes. See the difference? One is a generic outcome. The other proves you know the ecosystem. Salesforce is a massive part of the sales ecosystem. By naming it, you are telling the algorithm, 'I am already trained. I require less onboarding.' That reduces the perceived risk for the hiring manager. Luna: I love that. It turns a passive list of duties into active proof of competence. But what about the creative roles? Designers, writers? Do they face the same algorithmic wall? Lucas: They do, but the metrics are different. For a designer, it might not be about Jira. It might be about Figma, Adobe Creative Cloud, or specific design systems like Material Design. If you are applying to a tech company, and your portfolio link works but your resume doesn't mention the specific tools they use, you might still get filtered. It sounds harsh, but it's efficient for them. Luna: So even creativity has to be translated into technical compatibility. That is interesting. It feels like we are losing a bit of the artistry in the process. Lucas: It can feel that way. But I would argue that understanding the constraints of the medium is part of being a professional. In journalism, we learn the rules of style guides before we break them. In careers, you need to understand the rules of the hiring pipeline before you try to disrupt it. Luna: That's a fair point. It's not about hiding who you are; it's about making sure who you are can be found. Lucas: Exactly. And there is one more layer to this that most people miss. File format. In twenty twenty six, you should almost always submit a PDF unless the application specifically asks for a Word document. Why? Because Word files can render differently depending on the version of Microsoft Office the recruiter is using. PDFs lock the layout. But here is the catch: the PDF must be text-based, not a scanned image. Luna: Oh, I see. If you scan a paper resume and save it as a PDF, the computer just sees a picture. It can't read any of the text. Lucas: Correct. If it's an image, the ATS reads it as blank space. You might as well have submitted a napkin. Make sure when you export your PDF, you are exporting the editable text version. Most people don't even realize they are accidentally creating an image file when they save from certain design programs. Luna: That is a huge technical detail. I bet a lot of people have been accidentally rejecting themselves over a file format issue. Lucas: Probably. And while we are talking about formats, let's touch on the structure of the header. Stop putting your full address. City and state are enough. In fact, for remote roles, sometimes just your timezone is sufficient. The ATS doesn't care where you live; it cares about your eligibility to work and your proximity to the core team. Luna: Privacy is definitely a concern these days. Removing that street address makes sense. But what about the photo? Some countries still expect a photo on a resume. Lucas: If you are applying to a US or UK company, absolutely remove the photo. Many ATS parsers cannot handle images in the header and will choke on the file, corrupting your entire application data. Even if it doesn't crash the parser, it introduces bias. You want the hiring manager to focus on your skills, not your appearance. Keep it clean, keep it text-only. Luna: So, to recap: semantic relevance, proper file formats, and removing non-essential personal data. It feels less like writing and more like engineering a key for a specific lock. Lucas: It is engineering. And once you pass that lock, you still have to win the human. But that is a different problem. Today, we focused on getting past the invisible barrier. If you apply this audit to your next five applications, I think you will see a noticeable uptick in responses. Luna: I think that is a great place to stop for today. It shifts the focus from frustration to control. You can control how you present your data. Lucas: Right. And in a market that feels increasingly automated, taking ownership of that technical layer is one of the best ways to stand out. Thanks for tuning in.