The feedback your friends were too nice to give.
Before a person sees your layout, their software flattens it into a database row — and that row is what gets searched. Here's one, built from a resume that looks completely normal as a PDF:
PRIYA RAMASWAMY
priya.r@protonmail.com
SKILLS EXPERIENCE
JavaScript Frontend Engineer 2020 - 2024
React Nimbus Health
TypeScript • Shipped a scheduling UI used by 40k patients
AWS • Cut bundle size 61% by code-splitting routes
Node.js • Owned the design system rollout
EDUCATION Junior Developer 2018 - 2020
BS Computer Science Fathom Labs
Rutgers University • Built internal tools in React
Two jobs are plainly on that page. The parser recorded none of them, because the layout is two-column — "EXPERIENCE" came out welded onto the skills heading beside it, so there was no section for a parser to anchor on, and her phone and location came out empty. She looks perfect as a PDF and does not appear in a search for three years' experience. Example resume, real parser — this page runs the same code your upload does.
file:// address. Open
roast.cactusco.org instead.
PDF, DOCX, DOC, RTF, TXT, or Pages — up to 20MB
Paste the posting and the feedback changes completely: which requirements you never answered, where a keyword screener drops you, and whether this earns a phone screen for that role.
That's a job title, not a posting. Paste the actual description — requirements and responsibilities — or leave this blank. As is, it'll be ignored.
Analyzing your resume...
Want the cleaned-up version? I'll rebuild it into a properly organized document you can download and edit — same jobs, same dates, same you, just written the way it should have been. Modern or Harvard formatting, your pick.