<?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>Forem: Aneesh Ajithkumar</title>
    <description>The latest articles on Forem by Aneesh Ajithkumar (@aneesh).</description>
    <link>https://forem.com/aneesh</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1393386%2Fc432c56e-67cb-4e2c-b1e2-f5c38f6fc071.png</url>
      <title>Forem: Aneesh Ajithkumar</title>
      <link>https://forem.com/aneesh</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/aneesh"/>
    <language>en</language>
    <item>
      <title>How I built a Free ATS Resume Checker using React and Laravel</title>
      <dc:creator>Aneesh Ajithkumar</dc:creator>
      <pubDate>Wed, 08 Apr 2026 12:16:24 +0000</pubDate>
      <link>https://forem.com/aneesh/how-i-built-a-free-ats-resume-checker-using-react-and-laravel-2kdl</link>
      <guid>https://forem.com/aneesh/how-i-built-a-free-ats-resume-checker-using-react-and-laravel-2kdl</guid>
      <description>&lt;p&gt;If you've applied for a tech job recently, you already know the pain: you spend hours crafting the perfect developer resume, tweaking your GitHub links, hit submit, and then... nothing. You get thrown into the Applicant Tracking System (ATS) black hole.&lt;/p&gt;

&lt;p&gt;Over 75% of resumes are automatically rejected by bots before human eyes ever see them because of bad formatting or missing exact-match keywords. I got so frustrated by this that I decided to solve it. &lt;/p&gt;

&lt;p&gt;I recently launched &lt;a href="https://atsense.online/resume-grader" rel="noopener noreferrer"&gt;ATSense, a 100% Free ATS Resume Checker and Builder&lt;/a&gt;. It mimics the exact parsing algorithms used by systems like Workday and Greenhouse, scores your resume, and uses AI to fix it. &lt;/p&gt;

&lt;p&gt;In this post, I want to break down the technical architecture of how I built it using React, Laravel, and the OpenAI API, and why building an ATS parser is surprisingly difficult.&lt;/p&gt;




&lt;h3&gt;
  
  
  The Tech Stack
&lt;/h3&gt;

&lt;p&gt;I needed a stack that allowed for lightning-fast frontend interactivity (for the drag-and-drop resume builder) with a highly secure, scalable backend (to handle PDF extraction and API rate limiting).&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frontend:&lt;/strong&gt; React, Vite, Tailwind CSS, Lucide Icons&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; Laravel 11 (PHP 8.2), MySQL&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI Engine:&lt;/strong&gt; OpenAI GPT-4 API&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deployment:&lt;/strong&gt; GitHub Actions CI/CD to cPanel&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Challenge 1: The UI and "Guest-First" Architecture
&lt;/h3&gt;

&lt;p&gt;As a developer, I hate signing up for things just to test them. I wanted ATSense to be a "Guest-First" application. You arrive, drop your PDF, and get your score instantly without handing over your email or a credit card.&lt;/p&gt;

&lt;p&gt;Because of this, the React frontend handles a lot of heavy lifting. I used &lt;strong&gt;Tailwind CSS&lt;/strong&gt; to build a responsive, two-column "Recruitment Cockpit" where users can view their PDF on one side and the dynamic ATS scoring HUD on the other. &lt;/p&gt;

&lt;p&gt;By keeping state management centralized in React, users can tweak their bullet points and watch their ATS Match Score update in real-time.&lt;/p&gt;

&lt;h3&gt;
  
  
  Challenge 2: Parsing the PDF and The ATS Logic
&lt;/h3&gt;

&lt;p&gt;The hardest part about building an ATS checker is that PDFs are notoriously terrible at preserving text structure. A human sees a cleanly formatted "Experience" section, but a parser might just see a jumbled string of coordinates.&lt;/p&gt;

&lt;p&gt;To solve this, the Laravel backend steps in. When a user drops a resume:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Extraction:&lt;/strong&gt; Laravel accepts the &lt;code&gt;multipart/form-data&lt;/code&gt; upload and extracts the raw text. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Structuring:&lt;/strong&gt; Using regex and Laravel's elegant collection pipelines, the backend looks for standard ATS headers (e.g., &lt;em&gt;Experience&lt;/em&gt;, &lt;em&gt;Education&lt;/em&gt;, &lt;em&gt;Skills&lt;/em&gt;) to reconstruct the document into a readable JSON schema.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Score:&lt;/strong&gt; We run the extracted data against standard ATS compliance rules. (Are there weird graphics? Are contact details stuck in a header? Are there quantifiable metrics?)&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Challenge 3: Injecting AI for Gap Analysis
&lt;/h3&gt;

&lt;p&gt;Knowing your resume failed is only half the battle. I wanted the tool to actually fix it.&lt;/p&gt;

&lt;p&gt;When a user drops a Job Description into the UI, Laravel takes the parsed resume JSON and the Job Description and ships them to the &lt;strong&gt;OpenAI GPT-4 API&lt;/strong&gt; using a highly restrictive, low-temperature prompt system.&lt;/p&gt;

&lt;p&gt;The AI performs a "Gap Analysis"—it cross-references the hard skills the employer is asking for against what the user actually wrote. It doesn't just tell you that you are missing "React Hooks"; it actually generates a suggested, optimized achievement bullet to insert directly into your resume.&lt;/p&gt;

&lt;h3&gt;
  
  
  What's Next?
&lt;/h3&gt;

&lt;p&gt;Building the core infrastructure took a lot of late nights, but seeing people finally bypass the dreaded ATS bots makes it worth it. &lt;/p&gt;

&lt;p&gt;If you are currently job hunting or just want to see how your resume holds up against the bots, I would love for you to try it out!&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://atsense.online/resume-grader" rel="noopener noreferrer"&gt;Test your resume on the ATSense Grader here&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Let me know what you think of the stack, or roast my UX in the comments below! I'd love to hear your feedback. &lt;/p&gt;

</description>
      <category>career</category>
      <category>laravel</category>
      <category>react</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
