11 min read
You clicked submit and Greenhouse threw an error, or the upload looked fine until the preview showed half your jobs missing. That panic is common on US corporate reqs. Most Greenhouse resume upload issues aren't mysterious server bugs. They're file type limits, oversized exports, or layouts the parser can't read in order while the green checkmark still appears.
Check your resume for free after you fix the file, not before you re-upload the same PDF ten times. If Notepad paste shows Skills before your current employer, Greenhouse already lost your Experience block even when the attachment icon looks healthy. You'll waste an hour if you don't fix layout first.
Below: three symptoms, the cause behind each, how to tell which one is yours, and the fix that actually sticks. You don't need a new design subscription. You need a plain export recruiters can search. Job searching is already draining. You don't need a portal that accepts a file nobody can read in order.
Quick Wins
- Rename the file First-Last-Resume.pdf with no symbols in the name.
- Export single-column PDF from Word at under five megabytes.
- Paste PDF text into Notepad and confirm employers read top to bottom.
- Open Greenhouse parsed preview before you fill knockout questions.
What happens when Greenhouse accepts your resume
Greenhouse stores the attachment and runs an import pass that tries to map employer, title, dates, education, and skills into searchable fields. Recruiters filter on those fields, not on the PDF thumbnail. Upload success only means the file landed on the server. Parse success means your latest role shows up where keyword searches expect it.
Two different failures hide behind the same symptom. A hard rejection never creates a profile row. A soft failure creates a row with empty Experience while the attachment icon looks fine. Candidates often chase the first problem with browser tricks when they actually have the second problem in a two-column Canva export.
US startups and mid-size companies run Greenhouse beside Lever and Ashby. Enterprise teams sometimes pair Greenhouse with other HRIS tools, but the upload screen behaves the same: attach, preview, answer questions, submit. The fixes below target what breaks on that attach step and the preview pane right after it.
Edge case: the posting asks you to paste LinkedIn instead of uploading. Treat that as a separate workflow. This page covers file upload failures and parse gaps on reqs that still want a PDF or Word attachment.
Edge case: you're re-applying to the same company within six months. Greenhouse may pre-fill old answers while still letting you swap the resume. Replace the attachment and open preview again. An old parsed profile can linger in recruiter view until the new file parses cleanly.
Edge case: the req includes a portfolio link plus resume upload. Portfolio sites do not replace parse quality on the PDF. Recruiters still filter on imported Experience. Keep the resume self-contained with dated roles even when Behance or GitHub links are optional fields.
A composite customer support lead kept failing uploads until she dropped an embedded video thumbnail from a Word resume. File size fell under one megabyte and preview populated on the second try. The video wasn't the problem on paper. The export bloated the PDF enough to timeout on mobile upload.
Read how to preview your resume like an ATS in the US when you want a parse check outside the employer portal. Same logic, less pressure while the req timer runs.
Greenhouse resume upload issues by symptom
Start with what you see on screen, not with random formatting tips. Each branch below pairs a symptom with a likely cause and the fix that stops the loop.
Symptom: upload error or spinner that never finishes
Cause: file type, size, or name blocked before parsing starts. Greenhouse commonly rejects Pages exports, huge portfolio PDFs, and filenames with commas, hashtags, or non-ASCII characters. Mobile uploads on weak signal sometimes fail silently.
Before: Marketing candidate uploads Resume_Final_v7.pages from an iPhone; error says unsupported format.
After: Exports DOCX from Google Docs, saves as Jordan-Lee-Resume.pdf at 420 KB on desktop Chrome; upload completes in one pass.
Fix: convert to PDF or DOCX from Word or Google Docs, rename with letters and hyphens only, compress if above five megabytes, retry on desktop Chrome with extensions off. Screenshot persistent errors and email the recruiting contact on the posting.
Symptom: upload succeeds but preview is blank or missing jobs
Cause: layout the importer cannot map. Tables, text boxes, sidebar skills columns, icon headers, and multi-column templates reorder text on import. Greenhouse may keep the PDF while leaving Experience empty.
Before: Operations analyst resume in a two-column Canva template; upload checkmark green; preview shows contact line and Skills only.
After: Single-column Word file at 11-point Calibri; preview lists Harbor Logistics | Operations Analyst | Mar 2022 to Present with four bullets attached.
Fix: rebuild in one column with standard headings (Experience, Education, Skills), Month Year dates on the same line as employer and title, no graphics. Run Notepad paste test. Re-upload once. Do not submit knockout answers until preview shows your current employer.
Symptom: fields autofill wrong employer, title, or dates
Cause: inconsistent date formats, stacked headers, or employment entries split across table cells. Parsers grab the nearest text block, not the visually correct column. Mixed 01/2022 and Jan 2022 on the same page makes end dates land on the wrong job.
Before: Software engineer resume lists 03/21 to 08/22 beside one role and March 2021 to August 2022 beside another; Greenhouse maps both ranges onto the oldest employer.
After: Every role uses Mar 2021 to Aug 2022 on one line under the company name; autofill attaches dates to the correct title.
Fix: pick one Month Year pattern, put employer | title | dates on a single line per role, delete footer repetition of old jobs. Read how to stop ATS from misreading dates in the US when date scramble is your main preview problem.
How to tell which cause is yours in five minutes
If the portal never accepts the file, you're in branch one. If it accepts but preview is empty, branch two. If preview shows jobs but titles or dates attach to the wrong row, branch three. Export PDF, paste all text into Notepad, and read top to bottom without formatting. Skills before employers means branch two even when the PDF looks polished.
Open Greenhouse preview side by side with Notepad output. Matching order means you can focus on keyword gaps. Mismatch means layout fix first, always.
If you're unsure after Notepad paste, email yourself the PDF and open it on a second device. Sometimes local preview caches an old attachment while the server stored the new one. Log out, log back in, and confirm the timestamp on the uploaded file before you spend an hour rewriting bullets on the wrong version.
Symptom: required fields stay empty after autofill
Cause: headings the importer does not recognize. Creative section titles like Where I've Work or My Journey instead of Experience can leave autofill blank even when body text exists. Same for icons replacing words.
Before: HR coordinator resume labels section Professional Story; Greenhouse autofill offers no employers to select.
After: Section renamed Experience with plain text headings; autofill populates three prior employers for knockout questions.
Fix: rename sections to Experience, Education, and Skills. Remove emoji headers. Re-export and test autofill before you manually retype ten years of history into tiny boxes.
Copy-paste Greenhouse-safe file header
[Full Name]
[City, ST] · [phone] · [email] · [LinkedIn URL if used]
Experience
[Company Name] | [Job Title] | [Mon YYYY] to [Mon YYYY or Present]
• [Metric bullet with tool from posting in first eight words]
• [Second bullet]
[Next employer block same pattern]
Education
[Degree], [School], [Mon YYYY]
Skills
[Comma-separated tools already proven in bullets]
Upload habits that keep Greenhouse resume upload issues alive
Re-uploading the same PDF after every rejection. If preview already failed, the layout is the problem. A tenth upload does not rewrite the parser.
Trusting the attachment icon over the preview pane. Recruiters search parsed fields. A stored PDF nobody mapped is invisible in name filters.
Using image-only scans for text roles. OCR in employer systems is uneven. Typed PDF exports beat phone photos of printed pages.
Stuffing keywords into hidden white text or tiny footer lines. Some imports strip footers entirely. Terms need to live in Experience bullets recruiters can open.
Applying on mobile while commuting. Uploads fail more often on cellular handoffs. Finish attach and preview on stable Wi-Fi when possible.
Ignoring duplicate profile warnings. Multiple incomplete uploads can clutter recruiter view. Fix the file once, upload once, then submit answers.
Read Greenhouse resume formatting what breaks and why for deeper layout teardown when preview keeps dropping sections after you fix file size.
Submitting before preview loads. Slow connections sometimes let you click continue while import still runs. Wait until employer lines appear or refresh once. Half-imported profiles are harder to fix after knockout answers lock in.
Using password-protected or certificate-signed PDFs. Security wrappers block parsers the same way they block edits. Export an unprotected copy for applications. Keep the signed version for your records only.
Test the file before Greenhouse eats it
Run the free ATS checker with the job description pasted in. It won't replicate Greenhouse field maps, but it flags missing must-have terms and layout edges before you burn an application on a broken export.
Rebuild in the free resume builder if your current template uses columns, icons, or text boxes. Export plain PDF, run Notepad paste, then return to Greenhouse for one clean upload.
If the req also wants a letter, draft structure in the cover letter generator, then upload the resume only after preview shows Experience populated. Cover letters do not fix parse failures on the attachment.
Your Greenhouse upload checklist tonight
Greenhouse resume upload issues in US apps usually split three ways: file rejected, preview empty, or fields mapped wrong. Match your symptom, fix the cause once, confirm in preview, then answer knockout questions. You don't need a new template marketplace subscription. You need a boring PDF the parser can read.
Export single column. Rename cleanly. Paste into Notepad. Re-upload once. I've seen more callbacks after layout fixes than after fifth attempts with the same Canva file.
Open the req on your list with the closest deadline. Fix that file first. Greenhouse won't wait while you perfect a portfolio PDF nobody parses.
Read more
Frequently asked questions
Most rejections come from unsupported file types, files over the size cap, or names with special characters. Greenhouse accepts PDF and Word in most US reqs. Pages, RTF, and image-only scans often fail before parsing starts. Rename to First-Last-Resume.pdf, keep under five megabytes, and export from Word or Google Docs instead of a design tool.
Upload success is not parse success. A blank or partial preview usually means the PDF used text boxes, columns, or embedded fonts the importer skipped. Open the parsed field view if the employer exposes it. If Experience is empty, rebuild single-column layout and re-upload. Do not assume recruiters see the PDF thumbnail you see.
PDF from a clean Word export is the safer default for US corporate reqs. DOCX can work when the template is plain, but styled Word files sometimes lose headings on import. Avoid password-protected PDFs and scanned image resumes unless the posting explicitly allows them. Run Notepad paste test on whichever format you choose.
Yes. Ad blockers, stale cache, mobile Safari quirks, and unstable connections can interrupt uploads or drop attachments. Try Chrome or Firefox on desktop, disable extensions for the session, and retry on stable Wi-Fi. If the file uploads elsewhere but not on Greenhouse, screenshot the error and email the recruiting inbox listed on the posting.
No. If the preview already scrambled employers or dates, the parser read what it could from that layout. Change the file: single column, standard headings, Month Year dates, no tables or icons. Re-upload once after paste test shows employers in order. Repeated uploads of the same broken PDF waste time and sometimes duplicate incomplete profiles.