<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rolf Sehested</title>
    <description>The latest articles on DEV Community by Rolf Sehested (@rolfsehested).</description>
    <link>https://dev.to/rolfsehested</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4040635%2F6870781d-d7e0-4efb-b714-cb7068075253.jpg</url>
      <title>DEV Community: Rolf Sehested</title>
      <link>https://dev.to/rolfsehested</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rolfsehested"/>
    <language>en</language>
    <item>
      <title>Why Your Developer Resume Keeps Getting Filtered Out by ATS (and how to actually fix it)</title>
      <dc:creator>Rolf Sehested</dc:creator>
      <pubDate>Tue, 21 Jul 2026 20:07:42 +0000</pubDate>
      <link>https://dev.to/rolfsehested/why-your-developer-resume-keeps-getting-filtered-out-by-ats-and-how-to-actually-fix-it-mmd</link>
      <guid>https://dev.to/rolfsehested/why-your-developer-resume-keeps-getting-filtered-out-by-ats-and-how-to-actually-fix-it-mmd</guid>
      <description>&lt;p&gt;If you've applied to 50+ jobs and heard nothing back, the problem might not be your experience. It might be that a bot never let a human see your resume.&lt;/p&gt;

&lt;h2&gt;
  
  
  The ATS problem nobody explains properly
&lt;/h2&gt;

&lt;p&gt;Applicant Tracking Systems parse your resume into plain text before a recruiter ever looks at it. If your resume uses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Multi-column layouts&lt;/li&gt;
&lt;li&gt;Tables for skills or experience&lt;/li&gt;
&lt;li&gt;Text inside images or icons&lt;/li&gt;
&lt;li&gt;Fancy custom fonts with weird encoding&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;...there's a real chance it gets mangled or dropped entirely. You didn't get rejected. You got misread.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually works
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Single column layout.&lt;/strong&gt; Parsers read left to right, top to bottom. Two columns can scramble the order.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Standard section headers.&lt;/strong&gt; "Experience," "Education," "Skills." Not "My Journey" or "What I Bring."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plain text skills, not icon ratings.&lt;/strong&gt; A 4-out-of-5-star icon for "React" often just reads as nothing to a parser.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keywords from the actual job posting.&lt;/strong&gt; Not keyword stuffing, just mirroring the language they used for your tech stack and title.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PDF export from a real text layer&lt;/strong&gt;, not a scanned image or a design tool that flattens everything.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The annoying part
&lt;/h2&gt;

&lt;p&gt;Most people find out their resume is unreadable only after weeks of silence. There's no error message. No feedback. Just a black hole.&lt;/p&gt;

&lt;p&gt;I've been building on this problem for a while (it's why templates on &lt;a href="https://applygrid.site" rel="noopener noreferrer"&gt;ApplyGrid&lt;/a&gt; are built parser-first instead of pretty-first), and the biggest unlock for most people isn't a redesign, it's just knowing what to strip out.&lt;/p&gt;

&lt;p&gt;Curious what others have run into here. Anyone had a resume rejected for a formatting reason you only discovered by accident?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>career</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
