Module 9: Final Checklist and Submission — Pre-Send Verification and File Format Rules
Table of Contents
← Return to the Resume Optimization Course
This is the final module. Before you click submit on any application, run through this checklist. It takes 5–10 minutes and catches the kind of mistakes that are invisible when you’ve been staring at your resume for hours.
This module also includes the two quick-reference tables — common resume mistakes and word replacement — that belong on your desk for every revision.
Page Count Rules
One Page
Use a one-page resume when:
- You’re a new grad or have under 5 years of experience
- The company or role explicitly asks for it
- The industry culture favors brevity (some startups, design roles, certain sales environments)
Two Pages
Two pages is the standard for 5–15 years of experience. Use it when:
- Your professional history genuinely requires the space
- You have significant projects or publications worth listing
- You’re in a senior IC, staff, or management role with a longer track record
Three Pages or More
Almost never appropriate unless:
- You’re an academic submitting a CV (different document type, different conventions)
- You’re a C-suite executive with 20+ years and a board member / advisory history
- Your field requires a full publication or patent list
The universal rule: every line should earn its place. If you’re struggling to fill page two, stop at page one. If you can’t get under three pages, cut the oldest and least relevant roles first.
File Format and Submission
When to Submit PDF
Almost always. PDF preserves your formatting exactly as you designed it. The human recruiter sees what you intended them to see.
When to Submit .docx
When the job posting or ATS explicitly asks for Word format. Some older ATS systems parse .docx better than PDF. If both are accepted and you’re unsure, submit the PDF.
Naming Your File
FirstLast_Resume.pdf
or
FirstLast_Resume_CompanyName.pdf
Never:
resume_final_v3_FINAL_USE_THIS.pdfMy Resume.pdfresume(2).docxuntitled.pdf
A recruiter’s downloads folder has dozens of resumes named “resume.pdf.” Yours should be findable the moment they go looking.
Email Submissions
- Subject line:
Application for [Job Title] — [Your Name] - Keep the body to 3–4 sentences. The resume is attached — don’t re-summarize it.
- If you were referred, mention the referrer’s name in the first sentence.
The Pre-Send Checklist
Run through this before every submission:
- Contact info is current — email, phone, LinkedIn, city/state (not full address)
- No typos — run spellcheck, then read it out loud
- Dates are consistent and accurate — same format throughout, no gaps you haven’t addressed
- Every bullet starts with a strong action verb
- ATS keyword match is at least 60–70% — use the ATS Resume Improver against the job description
- No tables, text boxes, or multi-column layouts
- No graphics, photos, or skill rating bars
- File is named correctly — FirstLast_Resume.pdf
- PDF opens correctly on a different device or in a browser
- LinkedIn profile matches your resume’s dates and titles
- A second person has read it — fresh eyes catch errors you’ve become blind to
- You can speak to every item on this resume confidently in an interview
- Summary is tailored to this specific role — not generic across all applications
- Most relevant experience appears first within each role
Run this checklist, not as a formality, but because most errors that reach recruiters are things the checklist would have caught.
Common Mistakes Reference Table
| Mistake | Fix |
|---|---|
| Objective statement for experienced candidates | Replace with a targeted summary |
| “References available upon request” | Delete it — always assumed |
| “Responsible for / Assisted with / Helped” | Use action verbs with outcomes |
| Listing every job since high school | Go back only 10–15 years |
| Personal info (photo, age, marital status) | Remove — not appropriate in US hiring |
| Unexplained acronyms | Spell out at least once |
| Skills listed with no context or depth | Group by category, let bullets prove depth |
| Using “we” throughout | Say “I” or own the action in the verb |
| One resume for every job | Tune the summary and keywords per role |
| Saving only as .doc or .docx with unusual fonts | Submit PDF for human review |
| Sections named creatively | Use standard names: Work Experience, Skills, Projects |
| Dates using years only (2019–2021) | Use month-year consistently (Jan 2019 – Mar 2021) |
| Contact info in page header/footer | Put it in the document body |
| GPA below 3.5 listed | Remove it — it doesn’t help |
| Tutorial projects listed | Replace with real projects solving real problems |
Word Replacement Reference
Use this table when editing bullets and your summary:
| Don’t Use | Use Instead |
|---|---|
| Responsible for | Led, Owned, Built, Managed |
| Assisted with | Contributed to, Co-led (with specifics) |
| Worked on | Developed, Shipped, Refactored |
| Helped improve | Improved (own the verb) |
| Was part of a team that | Led / Collaborated on (specify your role) |
| Passionate about | (just show it through your work) |
| Leverage | Use |
| Utilize | Use |
| In order to | To |
| Due to the fact that | Because |
| At this point in time | Now |
| Synergize / leverage synergies | (describe the actual collaboration) |
| Results-driven | (show a result instead) |
| Detail-oriented | (demonstrate it in your bullets) |
| Team player | (show a collaboration in a bullet) |
| Hard worker | (show a hard thing you completed) |
Congratulations
You’ve completed the Resume Optimization Course. Here’s what you’ve covered:
Now use the tool: ATS Resume Improver — upload your resume, paste the job description, run the keyword check, get the score, and optimize.
Read the tool guide: ATS Resume Improver: Full Feature Walkthrough
Return anytime: Resume Optimization Course Start
