Resume PDF Checklist Before You Upload to a Job Portal
Portals are picky in boring ways
Company sites still reject files over a size cap, or they parse only the first page, or they strip headers. You can't control their software. You can control whether your PDF is a real text document named like an adult sent it.
Five minutes before Submit
- Highlight your name. If you can't, re-export from MineResume — don't screenshot a template.
- Search the PDF for the main tool in the posting. If it's missing and you used it, add it to Skills or a bullet.
- Click email, phone, and LinkedIn on a phone.
- File name: Firstname_Lastname_Role.pdf, not ResumeFinalNEW(3).
- A4 preview: nothing clipped, no heading alone at the bottom of page one.
Keyword check without stuffing
Split-screen the job description. Highlight tools and must-have duties. Your file should contain those phrases where they are true. Once is enough. Repeating “project management” eight times looks like a bot wrote it, because it often did.
If the portal also asks you to paste the same work history into text fields, paste it. Don't type a shorter version that conflicts with the PDF. Mismatched dates are an easy reject.
How portals fail, and which failures you can prevent
The rejection messages you can't see come from a small set of mechanical causes. File-size caps — some legacy portals bounce anything over 1 MB, and a resume with an embedded photo or logo export can quietly exceed it; compress or drop the image, not the content. File-type strictness — ".pdf or .doc only" means a .docx from a 2021 template may parse into confetti; when both are allowed, PDF is the safer bet because you control the layout, and Word only wins when the recruiter visibly edits resumes. First-page parsing — systems that extract fields only from page one will never see your skills if you placed them under two pages of job history, which is a placement decision with machine consequences. Header/footer stripping, as covered in the header article — anything load-bearing in the letterhead region of the PDF may as well be in invisible ink. None of these are the portal's secret malice; they're known quirks with known workarounds, and the five-minute pass below is built to catch every one of them before Submit.
The sixty-second text test, expanded
You've heard "make sure the text is selectable"; here's the actual procedure, because a quick glance misses the common failures. Open the PDF. Click and drag across your name — it should highlight word-clean, not as one blue rectangle (a rectangle means it's an image; a missing chunk means it's in the letterhead). Drag across your email: letter by letter correct, no zero-for-O in a typed address, no trailing space that will break the mailto. Press Ctrl+F, type your current employer's name: if the find does nothing, the text isn't there for a parser either, however pretty it looks. Then scroll every section boundary: headings should be real text, not decorative dividers with the words as graphics (the tell is that you can't select the word "Experience" itself). Total time: under a minute. What it catches: the entire genre of "looks great, extracts nothing" files, which is most of the resumes that vanish into portal black holes without ever reaching a person.
File naming like the adults in the room
The naming rule sounds trivial until you see it from the other side: a hiring manager's folder on a shortlist day contains "Resume.pdf," "resume final.pdf," "resume-2026(2).pdf," "RAVI.pdf," and one file that reads "Ravi_Kumar_DataAnalyst_HDFC.pdf." That last name is already answering three questions the others make someone open and hunt for. The format that works: Firstname_Lastname_Role.pdf, add the company only when a referral demands it, keep it under ~40 characters because some systems truncate. Two no-nos with real costs: no version numbers you send ("_v3" on an application file just says "I have a life outside this"). And no cute naming at all; also check the file's properties while you're there — some exports carry the author name from an old laptop login, which is a small privacy leak with a cheap fix (rename in your PDF tool, or export from the builder where the metadata is clean).
The Workday text-field problem
The most annoying modern application step: after uploading a perfect PDF, the portal demands you paste your entire history into dated text boxes anyway — usually because the company wants structured data, not your file. The failure mode is copying the PDF text in and getting mangled bullets and orphaned dates, then giving up and typing a summary; the second mistake is worse, because now the machine is matching the short version and your elegant PDF is decorative. The professional approach: keep a plain-text master of your history (bullets as lines, dates written out, no columns) and paste it field by field, keeping every fact identical to the PDF — same titles, same months, same employers. Repaste, don't retell. If the box has a character limit, cut the oldest role rather than paraphrasing the newest one, and put your best matching bullet in the first line the box allows, because that's what the extraction reads. Five tedious minutes per portal, but the parser doesn't care about your design, and consistency between the two versions is what makes you look organized instead of evasive.
Track what you sent, where
The follow-up call is the moment this whole system pays for itself, and it arrives without warning: three weeks after applying to Company X, someone says "I have your application in front of me" — and you have no idea which of four files that was. The tracker is a boring sheet, columns only: date, company, role, file name used, referral or portal, follow-up-due date, status. That's the whole design. It does three jobs: answers the "walk me through what you sent" call with the actual document open; stops the double-application disaster (same req, two different resumes, ATS shows both — this is a real rejection reason and now entirely preventable); and gives you the honest funnel data our job-search system article wants, because "I applied a lot" is a feeling and "14 sends, 3 calls, 0 onsites, all to the same role family" is a diagnosis you can act on. Revisit the sheet when updating the master: every role that got a call tells you which bullets actually worked, in writing, for free.
When the portal asks for more than the file
A growing share of applications are effectively database entries with your PDF attached as a receipt, and the mismatch between the two is where careful people still fail. The portal pulls your name, current title, and dates out of the file after you've already typed them into boxes — and if the typed "Current Company" says one thing and the PDF's first line says another because you updated one and not the other that morning, you've written yourself a puzzle nobody wants to resolve. The fix lives in the same "repaste, don't retell" habit from the Workday section, just widened: fill the structured fields from a plain-text master first, attach the PDF from the same master second, and never let a portal session start while the resume is mid-edit. Three field-level details that quietly affect real systems: name fields split first and last, so don't paste "Kumar, Ravi" into First Name out of habit; work-authorization and visa questions get matched against your answers months later when an offer is prepared, so a careless "No" that costs you the screen now beats a "Yes" that dies in paperwork; and when the portal asks for a salary expectation, that's a negotiation question wearing a forms costume — answer it in the tracker article's frame, a range anchored to research, not to whatever you typed last. The PDF is one part of the record you're creating; every box you fill that day is part of the same record, and consistency across it is the whole game.
After submit: the two-day and two-week windows
Two checkpoints keep the process honest after the button is pressed. The two-day check: log into the portal and confirm the application actually shows as submitted with your file attached — a real percentage of applications die in a form tab that closed early or an upload spinner that never finished, and "I definitely applied" isn't a record. The two-week check: one polite follow-up against the tracker, email to the recruiter or referral, three sentences — role, when you applied, one line reasserting the single best true match from your summary; nothing apologetic, nothing new. If there's no reply, the answer is no and moving on is the process working, not failing. What you don't do: re-submit a different resume to the same req (see the double-application note above) or apply twice hoping the second attempt parses better — if the file was broken, fix the file and apply once to the next posting. The re-application never rescues the first one; the ATS remembers both.