I had been applying for frontend developer roles for six weeks with almost no responses. My resume had been reviewed by two friends who both said it looked "solid." I had a decent portfolio. My experience was relevant. And yet: silence.
On a Friday afternoon I uploaded my resume to Gaply's Spark AI Resume Analyzer. I was expecting generic advice. What I got was specific, uncomfortable, and immediately actionable.
The Score That Explained Everything
52%. That was my ATS compatibility score. For context, most ATS systems filter resumes below 60% without a human ever seeing them. I was below the cut. Six weeks of applications had been disappearing into a void, not because my experience was wrong, but because the system was literally not reading my resume properly.
The analyzer broke down exactly why.
What the AI Found in My Resume
Skills gap (Critical): The roles I was applying to consistently listed "TypeScript," "React Testing Library," and "CI/CD pipelines" in the requirements. My resume had "JavaScript (including TypeScript experience)," "testing frameworks," and "deployment automation." Different words, same skills — but the ATS does not know that. It scans for exact phrases. I scored zero for three of my strongest skills because I paraphrased them.
Summary section (High priority): My summary said "Experienced frontend developer with a passion for building user-friendly applications." The AI flagged this as keyword-sparse. It contained no specific job title, no years of experience, no technology stack, no measurable impact. Every element the ATS ranks a summary on was either absent or vague.
Work experience bullets (Medium): Half my bullets described responsibilities rather than results. "Maintained the company's internal dashboard" instead of "Rebuilt the internal analytics dashboard reducing page load time by 60%, used daily by 200 staff members."
Missing skills (Medium): Roles I was targeting mentioned "Webpack configuration" and "accessibility standards (WCAG 2.1)." I had both skills but neither appeared anywhere in my resume.
The Fix (One Afternoon)
I worked through the analyzer's learning plan section by section. It gave me three immediate actions, four short-term fixes, and two medium-term improvements. I tackled the immediate ones first:
- Rewrote my summary to include: "Frontend Developer with 4 years of experience building production React/TypeScript applications, specialising in performance optimisation, accessibility (WCAG 2.1), and CI/CD pipeline management."
- Updated my skills section to use exact terminology from job descriptions: TypeScript (not "JavaScript including TypeScript"), React Testing Library (not "testing frameworks"), GitHub Actions (not "CI/CD tools").
- Rewrote my top five bullet points from responsibilities to results: "Reduced initial page load time from 4.2s to 1.1s by implementing code splitting and lazy loading — resulting in 23% improvement in user session duration."
I re-uploaded the edited resume. 88%.
What Changed in My Job Search
In the two weeks after fixing my resume, I received four phone screens. That was more than the previous six weeks combined. Two of those converted to first-round interviews. One is still active as I write this.
The content of my experience did not change. My skills did not change. Only the way I described them changed — specifically, to match the language that ATS systems and recruiters are actually scanning for.
The Gap Analysis: A Roadmap for the Next Six Months
Beyond the immediate fixes, the analyzer's Gap Analysis showed me two skills flagged as Critical gaps: Docker/containerisation and GraphQL. Both appeared frequently in the roles I wanted but were absent from my experience.
One click generated a learning roadmap from those gaps. I started it the following Monday. Both skills are now on my resume because I spent six weeks actually building projects with them. My next round of applications went out with those skills genuine — not just present.
That is the difference between a resume tool that patches keywords and one that actually helps you grow into the role you are targeting.