Name your resume file FirstName-LastName-Resume.pdf, or add the target role: FirstName-LastName-Product-Manager.pdf. The file name is visible in recruiter inboxes, ATS records, and shared-drive folders long after upload, and Resume_Final_v3 (2).pdf tells a hiring team exactly how much care went into the application.
You see the file name once, at upload. The hiring side sees it repeatedly: as an email attachment when a recruiter forwards your application, in the ATS document list next to your profile, in the interview-panel folder where six resumes sit side by side, and in the download bar when a hiring manager opens it before your call. In every one of those places, the name either identifies you instantly or forces someone to open the file to find out whose it is.
That is the whole argument. resume.pdf becomes one of forty identical resume.pdf files in a folder. Jane-Doe-Data-Engineer.pdf is findable, forwardable, and quietly professional in every context it travels through.
Use your name, optionally the role, and the word resume, separated by hyphens: Jane-Doe-Resume.pdf or Jane-Doe-Senior-Data-Engineer.pdf. Hyphens beat underscores because some systems display underscores poorly and URLs handle hyphens cleanly. Skip dates, version numbers, and company names — a file named Jane-Doe-Google.pdf forwarded to a different company is an awkward artifact.
Keep it under about 50 characters, use normal capitalization, and never include characters that trip file systems: slashes, colons, hash signs, emoji. If you tailor per application, tailor the content and keep the name stable except for the role word; the version bookkeeping belongs in your own folder structure, not in the name the employer sees.
Resume_FINAL_final_2 (1).pdf is not neutral. It says the document has been through desperate revisions, that the sender does not notice what the receiving side sees, and that the version you sent may not even be the right one. None of that is fatal on its own — but hiring decisions between comparable candidates turn on accumulations of small signals, and this one is free to fix.
There is also a parsing footnote: some ATS platforms use the file name as the default document title in your candidate record, and a few older ones choke on special characters. A clean, plain name removes even that small failure surface. Thirty seconds of renaming is the cheapest polish available on the entire application.
It helps when you are applying for one clear role: Jane-Doe-Product-Manager.pdf reads as tailored and is easy to find. If you use one resume for varied roles, name-plus-resume is safer than a title that mismatches half your applications.
Rarely. Parsers read the file contents, though some systems display the file name as your document title and older ones mishandle special characters. The real audience is human — recruiters seeing the name in inboxes and folders.
No. Dates and version numbers age the document and leak your revision history. Keep versioning in your own folder names or a drafts directory, and send a file whose name contains only your name, optionally the role, and the word resume.
File name fixed? Make sure the contents hold up too — the free scorer runs your resume through 60+ recruiter-grade checks.
