Can a machine read your résumé? Watch one try.
The same reader that fills real application forms runs right here, inside this tab. Give it your PDF and it shows you every line it recovered from your file, and every one it could not.
Drop your résumé here
PDF only · up to 2MB
Nothing is uploaded · no score out of 100
Product Engineer
Experience
- Shipped a self-serve billing flow used by 40,000 members.
- Led the move of the patient portal to TypeScript and React.
- Mentored two engineers through their first production launches.
- Built map tile caching that halved median load time on mobile.
- Owned the on-call rotation tooling for a team of eight.
Education
Skills
As a machine reads you
Everything below is what came out of your file, not what is in it. Anything missing here is a field we cannot fill for you from this file.
Name
Jordan Rivera
Contact
- Email: read
- Phone: read
- Location: not found
- Link: read
2 roles
Product Engineer
Software Engineer
A job you still hold and a job whose end date we dropped both read as no end date here. The file does not tell us which one it is.
1 school
BS, Computer Science, Colorado State University
6 skills
- TypeScript
- React
- Node.js
- Postgres
- GraphQL
- Figma
The file
1 page · 11 pt body type · single column
The part that is different
Your résumé never leaves this tab.
There is no upload on this page. The reader is code that runs on your own machine, so the file is opened in your browser's memory and never crosses the network. Check it yourself: open your network panel and drop a file. Requests do fire, and they are this site sending you its own PDF reader, because the code that reads a résumé has to arrive before it can read one. None of it carries your file.
Every other résumé checker we know of asks you to send the file to a server first. That is the step we removed, and it is the reason this page needs no account.
Said precisely, because the difference matters: that is a claim about this page. Make an account and add your résumé there and we do store that copy, because the agent needs it to fill forms. The privacy page says exactly what we keep.
Straight answers
- Is this an ATS check?
No, and we will not pretend otherwise. Nobody outside a company can tell you what its applicant tracking system did with your file, so any tool showing you an ATS score is guessing at one. What runs here is our own parser: the same code that fills real application forms for our users.
- Why is there no score out of 100?
Because we cannot produce one honestly. A single number implies we know how you rank against other applicants, and we do not. What we can prove is mechanical: which checks passed, which did not, and the exact line in your document that caused it. When a parse is too thin to judge, you get no number at all and a reason instead.