12 min read
Greenhouse gave you a green confirmation screen. Your inbox stayed quiet. You assume the req was competitive. Often the break happened in a portal field recruiters filter on before they open bullet one.
I've screened Greenhouse queues where the PDF thumbnail looked sharp and the experience tab was empty. That's not a keyword problem. That's parse and profile data that never stored. This US ATS application checklist for Greenhouse maps five failure layers to fixes you can run tonight.
Before you rewrite your summary again, check your resume for free with the posting pasted in. Confirm Greenhouse can copy employers and dates out of the file you'll attach.
Quick Wins
- Paste-test your PDF into Notepad before Greenhouse upload.
- Match employer names and month-year dates in the file and every form row.
- Answer custom screening questions, including optional salary and sponsorship fields.
- Open Greenhouse preview after upload and confirm experience populated.
The symptom: Greenhouse accepted you but recruiters never filtered to you
Confirmation email arrives. The careers page still lists the role. You refresh and assume you're in a long queue. Behind that screen, recruiters often work from filtered candidate lists built from parsed fields, profile rows, and screening answers. Blank employer names mean blank rank. A knockout answer marked wrong removes you before anyone reads bullet one.
Job searching is hard enough without guessing whether silence means fit or portal data that never stored. Greenhouse failures feel invisible because nobody emails you saying your PDF was a scan or your work history duplicated with wrong dates.
The pattern: most automated-layer rejections on Greenhouse trace to five portal fields, not keyword density. Fix the field layer first. Tailor bullets second.
Read why your resume never reaches a human for what happens after parse succeeds but rank still fails. This page stops you earlier, at the Greenhouse form layer.
US ATS application checklist for Greenhouse: five causes and fixes
Cause 1: Resume upload parse failure
Greenhouse reads your PDF or DOCX and tries to populate experience, education, and skills. Two-column layouts, tables, text boxes, and image-only scans break reading order. The thumbnail looks fine. The parsed experience tab is empty or scrambled. Recruiters who filter on job title or years never see your name.
Before: Canva two-column PDF where job titles appear below dates in the Greenhouse preview.
After: Single-column Word export, 11-point Calibri, month-year dates in the left margin, paste test clean into Notepad.
Fix: Rebuild in Word or Google Docs. Export text-based PDF. Upload again. Open Greenhouse post-upload preview. If employers are still blank, the file is still the problem.
Cause 2: Profile and work history mismatch
Many Greenhouse postings parse your resume then ask you to confirm or retype each role. Candidates click through with parsed garbage or skip rows assuming the PDF is enough. Recruiters see duplicate employers, overlapping dates, or a current job listed as ended.
A mid-level marketing coordinator once had "Marketing" parsed as employer and "Coordinator" as company. She didn't fix it because the PDF was attached. The recruiter's title filter for coordinator never matched her record.
Before: Parsed row shows "Manager" as company and "Retail" as title; candidate hits Next without editing.
After: Each row shows Company: RetailCo, Title: Store Manager, Dates: Mar 2021 to Present, matching the PDF line for line.
Fix: Treat the manual history section like a second resume. Edit every parsed row. Add missing roles the parser skipped. Use US month-year format consistently.
Cause 3: Custom screening and knockout answers
Greenhouse lets employers add custom questions: salary range, work authorization, willingness to relocate, years with a specific tool, driver's license, shift availability. Some are knockouts. Answer no to authorization when you need sponsorship and the role says no sponsorship, and you're out before review. Leave salary blank on a required field and submit may block entirely.
Optional questions tempt speed. Recruiters who read every response notice blanks. A blank commute answer on a hybrid role in suburban Atlanta tells them you didn't read the location line.
Fix: Read each question as a filter, not paperwork. Match honest answers to the posting. If sponsorship is required and the role says no, don't burn the apply. If salary is optional, still give a researched range instead of leaving it empty.
Cause 4: Contact, LinkedIn, and source fields
Greenhouse contact blocks look simple. Email typos, phone numbers without area code, and profile URLs that 404 break recruiter outreach. The how-did-you-hear-about-us dropdown left on default job board loses referral credit when an employee referred you. Some teams prioritize referred candidates in their Greenhouse queue.
Mismatched email between resume header and application form creates duplicate candidate records. Recruiters search by email. Two profiles with slightly different addresses make you look like you applied twice with different files.
Before: Resume says [email protected]; Greenhouse form typed [email protected]; source left as generic job board when a friend referred you.
After: Same professional email in header and form, full phone with country code, working profile URL, source set to Employee Referral with name if the form allows.
Fix: Copy contact info from your resume header into the form. Test the profile link in a private window. Pick the most accurate source option before submit.
Cause 5: Wrong document in the resume slot
Cover letter uploaded where Greenhouse expects a resume. Last year's PDF without the new role title. A blank page exported by accident. Tracked-changes Word doc still showing redlines. Greenhouse stores whatever binary you attach. Recruiters open the file tab first. Wrong document means right experience never gets read.
Greenhouse often has separate fields for resume and cover letter. Pasting cover letter text into the resume upload slot is a common midnight mistake when both files sit in Downloads with similar names.
Fix: Open the file locally. Read the header. Name it LastName_FirstName_ShortReqTitle.pdf. Use Greenhouse's cover letter text box or upload field for the letter, not the resume slot. Generate a cover letter as its own PDF when the posting asks for a separate file.
How to tell which cause is yours
Greenhouse preview shows blank or scrambled experience after upload: start with Cause 1. Run paste into Notepad. No selectable text means scan or lock. Titles below dates means layout fight.
Preview looks fine but recruiter view would show duplicate or nonsense employers: Cause 2. Scroll every manual row before you hit submit.
Instant rejection email or submit blocked on a red field: Cause 3. Read the exact question. Knockout logic often fires on authorization and license questions.
Recruiter emailed asking for your resume after you applied: Cause 5 or a contact mismatch from Cause 4. They received something, but not the file or email they expected.
Copy-paste: Greenhouse pre-submit checklist
Run this list before every Greenhouse submit:
1. Resume is text-based PDF or DOCX per posting instructions.
2. Paste test into Notepad: employers, dates, and skills appear in order.
3. Post-upload preview: experience section populated, not blank.
4. Manual work history rows match the PDF: company, title, month-year dates.
5. Every custom question answered; salary and sponsorship filled honestly.
6. Contact email and phone match resume header; profile URL opens.
7. Source/referral field reflects how you actually found the role.
8. Correct resume file in resume slot; cover letter in letter field or text box.
9. Filename: LastName_FirstName_ShortReqTitle.pdf.
10. Screenshot confirmation page with date for your records.
Composite: software engineer with scrambled parse
Before: Sidebar skills table; Greenhouse preview shows React where employer names should be; manual history left untouched.
After: Single-column rebuild, Node and AWS in bullet one, manual rows edited to match, preview clean.
Composite: registered nurse knockout miss
Before: Selected no on compact state license question despite valid RN license; didn't type license number in the text field.
After: Yes on license question, number entered, one bullet on Epic documentation on a 28-bed unit in the PDF.
Edge case: Greenhouse posting allows portfolio or work sample links
Some startups add a URL field for portfolio or code samples. A broken link or login-walled personal site wastes the field. Use a public PDF portfolio or a direct GitHub repo link. Test in an incognito window before submit.
Edge case: reapply after a bad Greenhouse submit
Many employers block duplicate applications to the same req. Withdraw the broken one if Greenhouse allows it, then submit fresh with the fixed file and aligned form. If withdraw isn't available, email recruiting with one corrected PDF and the confirmation ID. Don't upload four versions in one afternoon.
Edge case: mobile apply on Greenhouse
Phone uploads often become image-only PDFs. Custom questions get rushed. Wait until you're at a laptop with the real export and time to read each knockout line.
Edge case: Greenhouse education fields parse wrong
Degree title and graduation year sometimes land in the wrong row after upload. A bachelor's degree parsed as an employer name breaks education filters. Scroll the education block the same way you scroll work history. Fix school name, degree string, and month-year or year-only dates before submit.
Edge case: cover letter text box vs upload
Some Greenhouse reqs want pasted text. Others want a separate PDF. Pasting a letter into the resume slot is a common mistake when both attachments sit in Downloads. Read the label on each field. A one-page PDF named CoverLetter_LastName_ReqTitle.pdf belongs in the letter upload, not the resume slot.
Read how to stand out when 1,000 people apply once your Greenhouse fields pass parse and screening. That's where tailoring starts to matter.
What broken Greenhouse applications still share
Trusting the upload spinner. Greenhouse can finish uploading while parse fails. Preview is where blank fields show up.
Assuming the PDF is enough. Manual history and custom questions still feed recruiter filters even when the file looks great.
Speed-running optional questions. Blanks on salary, commute, and sponsorship read as low effort to recruiters who scan every answer.
Default source dropdown. Referral credit matters to hiring teams. Job board when a friend referred you loses queue priority.
Same generic resume for every Greenhouse posting. File parse may work while knockout answers still fail on role-specific requirements.
Skipping the confirmation screenshot. When something breaks later, you need the application ID and submit date to fix it with recruiting.
Ignoring EEO voluntary surveys. Those sections are separate from screening. Skipping them is fine when marked voluntary. Don't confuse them with required custom questions above the submit button.
Score the file before Greenhouse stores it
Portal field fixes only matter when the content inside the file is worth parsing. A clean PDF with weak bullets still loses after you enter the ranked list. A strong resume in a locked scan still dies at upload. Check both layers.
Run a free ATS resume check with the job description pasted. Fix parsing gaps in bullet one, re-export, paste-test, then upload to Greenhouse. Score your job match on the same posting so required skills land in experience with dates before you touch custom questions.
Run the US ATS application checklist before you tailor again
A US ATS application checklist for Greenhouse isn't a keyword cheat sheet. It's five portal fields: parse, manual history, screening answers, contact and source, and the right file in the right slot. Fix the one that matches your symptom tonight. Then tailor bullets for the ranked list you actually entered.
Export one clean PDF from your master doc. Edit every Greenhouse work history row. Answer custom questions honestly. Open the preview. Screenshot the confirmation. Stop rewriting your summary when recruiters never got your employers into the system.
This won't land you roles you're not qualified for. It stops qualified files from dying in Greenhouse before anyone reads them. That's worth twenty minutes before every submit.
Save the confirmation screenshot in a folder named with company and date. When a recruiter replies asking for a corrected file, you have the application ID ready. One clean resubmit beats three anxious follow-ups with different PDF versions attached.
- Parse test before upload; preview after upload.
- Manual rows match PDF line for line.
- Screening answers honest and complete.
- Right file in resume slot; letter separate.
Read more
Frequently asked questions
Greenhouse stores parsed resume text and application answers in searchable fields. Recruiters often filter on title, location, keywords, and screening responses before opening attachments. A file that parses blank may never enter the filtered view even when the PDF thumbnail looks fine.
Yes when the form requires it. Many Greenhouse postings parse your PDF then still ask you to confirm employer rows. Mismatches between parsed data and typed fields create duplicate or empty records. Align company, title, and month-year dates in both places.
Required questions block submit. Optional ones left blank signal low effort to recruiters who read every answer. Salary, sponsorship, and commute questions often feed filters. Answer honestly; a wrong knockout wastes less time than a recruiter call you cannot pass.
Text-based PDF exported from Word or Google Docs is the default US choice. DOCX works when the posting requests Word. Avoid scanned image PDFs, password locks, and multi-column Canva exports. Run a paste test into Notepad before upload.
Most Greenhouse portals lock edits after submit. Some allow withdraw and reapply. If you caught a parse failure or wrong file, email recruiting with one corrected PDF and your confirmation number. Do not attach four versions in one thread.