The interview-question test
A recruiter reads a skill and asks: can I build a question from this line? If not, it reads as a claim. Evidence is scope plus tools plus a dated role. You supply the numbers; we never fill them in for you.
Add your resume and the role you are aiming for. You get three lists: the skills your resume proves, the ones it mentions without backing up, and the ones it never shows. You can read the result without an account.
PDF, DOC or DOCX, up to 5 MB. Or paste the text instead.
Here is what the result looks like, on an example resume.
How to read it
A recruiter reads a skill and asks: can I build a question from this line? If not, it reads as a claim. Evidence is scope plus tools plus a dated role. You supply the numbers; we never fill them in for you.
A skill dropped into a list with nothing behind it is the fastest way to lose credibility, and it wins interviews you then fail. We show you where a skill is unbacked so you can evidence it, and we never offer to paste words in for you.
What quietly breaks an application is a file nothing can read: two columns, contact details in the header, tables. We show you what the parser actually extracted so you can see it for yourself.
You can read your result without an account. Create an account to save and export your base resume; job-specific tailoring is an optional next step.
No. A skill is only marked as proved when your resume shows it. Anything else is marked as mentioned or absent, and we tell you to leave it off if you have not done it.
A title works when you are still exploring because it creates a general role-based shortlist. If you have the ad, paste it to compare against its exact words.
The result suits any experience level. You can build, edit, and export a base resume, then choose whether to tailor it to a specific job.
Most resumes do not need new experience. They need the experience already there to be readable.