5 Resume Mistakes That Get You Filtered by ATS (And How to Fix Them)

Jules — Sun, 29 Mar 2026 05:55:12 +0000

If you have ever applied to a job and heard nothing back - not even a rejection - there is a decent chance your resume never reached a human. Applicant Tracking Systems filter out resumes before a recruiter ever sees them, and most of the reasons are fixable in about 20 minutes.

Here are five mistakes I see constantly, especially from developers who assume the content speaks for itself.

1. Using Headers or Text Boxes for Contact Info

ATS software reads documents top-to-bottom, left-to-right. When you put your name and email inside a header, footer, or text box, many systems skip it entirely. Your resume gets parsed as an anonymous document with no contact info, and the recruiter has no way to reach you even if your qualifications are perfect.

Fix: Put your name, email, phone, and LinkedIn URL in the main body of the document. Plain text, no special formatting containers.

2. Fancy File Formats

That beautifully designed PDF you exported from Figma or Canva? Some ATS platforms choke on it. Complex layouts with columns, icons, progress bars, and custom fonts get scrambled during parsing. The system reads "Python" as "Py th on" and your skills section becomes gibberish.

Fix: Use a single-column layout. Standard fonts (Arial, Calibri, Times New Roman). If you want to use a PDF, export from a word processor, not a design tool. When in doubt, submit a .docx file.

3. Missing Keywords (or the Wrong Ones)

ATS platforms often filter by keyword match against the job description. If the posting says "React" and your resume says "ReactJS," some systems treat those as different terms. If they ask for "CI/CD" and you wrote "continuous integration and deployment," the parser might miss it.

Fix: Mirror the exact language from the job description. Read the posting carefully and use the same terms they use. This is not keyword stuffing - it is making sure the system correctly identifies skills you actually have.

4. Non-Standard Section Headings

"Where I Have Worked" instead of "Experience." "My Toolkit" instead of "Skills." Creative section names confuse ATS parsers that are looking for standard headings to categorize your information.

Fix: Stick with conventional headings: Experience, Education, Skills, Certifications, Projects. You can be creative in your cover letter. Your resume's job is to be parseable.

5. Listing Responsibilities Instead of Impact

This one will not get you filtered by software, but it will get you filtered by the human who reads it after. "Responsible for maintaining the CI/CD pipeline" tells a recruiter nothing about whether you were good at it.

Fix: Use the format: [Action verb] + [what you did] + [measurable result]. "Reduced CI/CD pipeline run time from 45 minutes to 12 minutes by migrating to parallel test execution" tells a story. Numbers and specifics are what make a resume scannable.

Test Your Resume Before You Submit

Before sending your resume into the void, run it through an ATS compatibility check. Scoutify's resume checker will parse your resume the way an ATS does and flag issues before they cost you interviews.

For a deeper dive on making your resume actually stand out (not just pass the filter), check out this guide on how to make your resume stand out. Getting past the ATS is step one. Impressing the human on the other side is step two.

The Reality Check

Here is the thing that frustrates me about ATS filtering: it penalizes people for cosmetic issues, not qualifications. A brilliant engineer with a badly formatted resume loses to a mediocre one with clean formatting. It is not fair, but it is how the system works. Spend 20 minutes fixing these five things, and you remove a barrier that has nothing to do with your actual ability.

Your resume is a document optimized for two audiences: a parser and a human. Satisfy the parser first. Then impress the human.

I Built a System That Alerts Me About New Jobs Before They Hit LinkedIn

Jules — Sun, 29 Mar 2026 05:53:30 +0000

I was mass-applying on LinkedIn last year when I noticed something annoying: by the time a job showed up in my feed, it already had 200+ applicants. Some had 500+. I was applying to roles that were effectively closed before I even saw them.

So I started digging into why.

The Delay Problem

Most job boards work by aggregating postings from company career pages. LinkedIn, Indeed, Glassdoor - they all crawl or receive feeds from ATS platforms like Greenhouse, Lever, Ashby, and Workday. The problem is timing. A company posts a role on their careers page, and it can take anywhere from a few hours to a few days before it shows up on the big boards.

By then, the recruiter has already received a pile of applications. Yours is buried.

Monitoring Career Pages Directly

The idea is simple: instead of waiting for aggregators to pick up new roles, you monitor the source. Company career pages publish new jobs through their ATS API endpoints. Greenhouse has a public job board API. Lever has one. Ashby, SmartRecruiters, Workday - they all expose their listings through predictable URLs.

If you are a developer, your first instinct might be to write a scraper. I did that. It worked for about three companies. Then I realized the actual hard part is not scraping - it is everything else:

Deduplication: Jobs get updated without changing. Titles change slightly. Locations get reformatted. You need fingerprinting to avoid sending yourself the same alert five times.
Classification: Not every new posting is relevant. You need some way to filter by role type, seniority, location, and other criteria.
Scale: Monitoring 10 companies is manageable. Monitoring 1,000+ requires actual infrastructure.

I got about a week into building this before I realized I was building a full product, not a weekend script.

What I Actually Use Now

I ended up switching to Scoutify, which does exactly what I was trying to build but across thousands of companies. It monitors career pages directly and sends push notifications within minutes of a new posting. The key difference from LinkedIn alerts is the timing - you are seeing roles when they go live on the source, not when an aggregator picks them up hours or days later.

The notification part matters more than I expected. Email alerts get buried. A push notification on my phone while I am having coffee means I can apply before most people even know the job exists.

Does It Actually Help?

Honestly, yes. My response rate went up noticeably when I started applying within the first hour of a posting going live. Recruiters have confirmed this anecdotally - the first batch of applicants gets the most attention because the recruiter is actively reviewing as they come in. By day two or three, they are already screening candidates from the initial wave.

If you are curious about getting LinkedIn alerts working better (they are still useful as a secondary source), there is a solid walkthrough on setting up LinkedIn job alerts that covers the filters and notification settings most people miss.

The Takeaway

The best advantage you can have in a job search is not a fancier resume or a better cover letter. It is simply being early. When you are one of the first 20 applicants instead of one of 500, everything about the process changes in your favor.

Building things to solve your own problems is the most developer thing there is. If you are job searching, the single highest-leverage thing you can optimize is speed.

DEV Community: Jules