Sample report
This is a real scan of a made-up resume against a made-up job posting. Nobody’s real data is on this page. Captured 14 Oct 2026 with gemini-3.5-flash; scoring rubric rubric-v2.1.0.
Recruiter Relevance Score
How a recruiter would judge the fit.
ATS Readiness
Whether the software can read your resume at all.
Two different questions. A resume can be a perfect fit and still be unreadable, which is why we score both.
A strong match. Tighten the few gaps below and this is worth your evening.
A recruiter searching for this role's skills would probably not surface your resume yet.
A parser reads this resume the way you wrote it.
Your top third survives a seven-second scan: the title lines up and the structure is readable.
Nothing here is a hard requirement you fail.
Can the machine read it?
ATS parse check
Not a score out of 100 - a real ATS ranks you against everyone else who applied that day, and nobody outside it can see that pool. What we can check is whether a parser recovers what you actually wrote. 9 of 10 checks pass.
Your name, email and phone all came out of the parser cleanly.
Parsed 2 titles in order: Frontend Developer, Web Developer.
Parsed 2 date ranges, so your experience length computes correctly.
Read 13 discrete skills, which is how a keyword search wants them.
Single column, which every parser reads top to bottom as written.
No table structures in your content regions.
The PDF carries real text, not a picture of text.
No standard section headers recognised, so the parser has to guess which text is experience and which is education.
PDF, 0 KB, 1 page - within every portal norm we know of.
Every character decoded cleanly.
What the parser sees
Everything below was recovered from your file by the same kind of text extraction an ATS runs. Compare it with your resume: anything missing here is missing for them too.
- Name
- Aakash Varma
- recovered, hidden on this public page
- Phone
- recovered, hidden on this public page
- Section headers
- nothing recovered
- Titles, in order
- Frontend Developer · Web Developer
- Date ranges
- Jan 2022 - Present · Aug 2020 - Dec 2021
- Skills, as discrete items
- React, JavaScript (ES6), Redux, HTML5, CSS3, SCSS, Bootstrap, jQuery, REST APIs, Git, WordPress, Figma, handoff
The part no rewrite fixes
Hard requirements
Must be authorised to work in India; no visa sponsorship is available
This role states an authorization or notice-period requirement. We cannot verify it from a resume, so confirm it before you spend an evening here.
What to fix
1 you can rewrite, 5 you cannot
The difference matters: one is wording, the other is experience. We only ever rewrite what you already wrote.
css is a must-have here and your resume does evidence it, but not where a recruiter will see it.
Your line
“Delivered 11 client websites in HTML, CSS, jQuery, and WordPress”
Try this instead
Move css out of the skills list and into the bullet where you used it, e.g. start that bullet with "css: " so a keyword search finds it in context. Your current evidence is "Delivered 11 client websites in HTML, CSS, jQuery, and WordPress".
jest is a must-have for this role and your resume does not evidence it. This is a learning gap, not a wording gap - we will not write it in for you.
We won’t write this in for you. It isn’t in your resume, so putting it there would be a claim you can’t back in an interview.
next.js is a must-have for this role and your resume does not evidence it. This is a learning gap, not a wording gap - we will not write it in for you.
We won’t write this in for you. It isn’t in your resume, so putting it there would be a claim you can’t back in an interview.
tailwind is a must-have for this role and your resume does not evidence it. This is a learning gap, not a wording gap - we will not write it in for you.
We won’t write this in for you. It isn’t in your resume, so putting it there would be a claim you can’t back in an interview.
typescript is a must-have for this role and your resume does not evidence it. This is a learning gap, not a wording gap - we will not write it in for you.
We won’t write this in for you. It isn’t in your resume, so putting it there would be a claim you can’t back in an interview.
A recruiter scanning for your experience will not find a section labelled as one.
We won’t write this in for you. It isn’t in your resume, so putting it there would be a claim you can’t back in an interview.
That was a sample. Yours takes thirty seconds.
Paste a job description and upload your resume. No account needed to see your score.