The file
Contact details sit in the body of the page: name, email, phone and city. The headline says “Software Engineer”. One employer, from March 2018 to now, with the title Software Engineer. A B.Tech from 2014 to 2018. Skills: Java, Spring Boot, PostgreSQL, REST and Git. Dates are written as month and year, and the layout is a single column with no sidebar.
- Cut nightly batch runtime from 40 min to 12 min by rewriting the settlement jobResultAction verb
- On-call for 3 services handling paymentsResult
- Responsible for REST APIs used by the mobile app
- Worked with the team on monthly releases
- Involved in code reviews for new joiners
- Part of the move to PostgreSQL for reporting
Parse: 25 of 25
Parse asks whether hiring software can pull the fields out of the file. Contact details in the body earn 8 points, the Experience, Education and Skills headings earn 9, dates written the same way with month and year earn 5, and a one column layout earns 3. This file gets all of them. A scanned PDF or a two column design would lose points here, even if the career behind it were stronger.
Impact: 4 of 15
Impact is what a recruiter takes in during a quick skim. Up to 9 points go to bullets that show a measurable result (money, time saved, people, volume or a percentage) and up to 6 go to bullets that start with what you did. Two of the six bullets carry a number and only one starts with an action verb, so this part is the weakest. The rest describe duties: “Responsible for”, “Worked with”, “Involved in”. Swapping in a strong verb helps a little; a real result helps more.
Tenure: 15 of 15
Tenure checks that every role has dates a parser can read, because a timeline is what hiring software extracts. This file has one role with clear dates, so it earns the full amount. For freshers, dated projects and internships count too.
The Kaabil Score: 80
Parse, Impact and Tenure add up to 44 of 55 points, which scales to 80 out of 100. Impact is the weakest part, so that is what the editor points to first.
Job match is a separate number
We also compared the resume with an SDE-2 (Java) posting that asks for Java, Spring Boot, Kafka, PostgreSQL and AWS, plus 4 or more years. Job match gives up to 12 points for the job title and 33 for the posting’s hard skills. “Software Engineer” is not the posting’s title, so the title points stay at 0. 3 of the 5 skills are on the resume; Kafka and AWS aren’t, and we never add them for you. That makes 20 of 45 for this posting.
The Kaabil Score stays at 80 with the job attached. Job match changes from one posting to the next; the health of the resume doesn’t.
What we would tell this person
- Turn two more duties into results, but only if they are true: for example “Built 14 REST APIs used by the mobile app” or “Shipped 12 monthly releases with a team of 5”. That alone would take Impact from 4 to 9 and the Kaabil Score from 80 to 89.
- Use the posting’s title in the headline only if it matches the level they actually hold.
- Add Kafka or AWS only if they have used them. We will not put words from a posting into a resume.
What this page is not
It is not a promise of interviews, and it is not a score from Workday, Greenhouse or Lever; those systems don’t give candidates a score. It shows the same parts the editor shows, with a concrete file instead of another slogan.
MM NAUMAN, founder