12 min read
Your PDF looks fine. Greenhouse shows a paragraph. That's Greenhouse parsing: why your bullets disappear on most US uploads isn't a missing keyword trick. Custom bullet glyphs, experience blocks inside tables, and text boxes flatten on import. Recruiters still open your file, but the parsed view they skim has no line breaks between achievements. You're losing skim points, not proof.
Check your resume for free with the posting pasted in after you paste your export into Notepad. If bullets merged into one line, fix structure before you add another skill to the footer. Parsers read text order, not your margin design. You won't rescue a wall of text with more Skills rows.
You've probably blamed the ATS for ignoring your best bullet. Often the bullet never arrived as a bullet. Job searching through Greenhouse portals is already opaque. This teardown shows the bar strong files clear, six before/after pairs across roles, what weak versions share, and a copy-paste export rule you can run in ten minutes.
Don't assume the recruiter will open your PDF attachment when the parsed view looks empty. Many coordinators skim Greenhouse first. If your metrics sit inside a wall of text, they won't hunt for them. You'll fix more screens by rebuilding bullets than by adding another keyword row.
Open your master file. Select all bullets. Paste into Notepad. If you see one long line where you expected four, keep reading. Greenhouse parsing why your bullets disappear starts in your export settings, not in a hidden score. You can't keyword-stuff your way past a flattened paragraph. Line breaks are the fix.
Quick Wins
- Rebuild lists with Word's bullet button or hyphen-space, not pasted symbols.
- Remove tables and text boxes around Experience blocks.
- Export DOCX when Greenhouse allows choice; otherwise PDF from Word only.
- Paste export into Notepad and confirm each bullet starts on its own line.
The bar Greenhouse bullets must clear on import
Greenhouse attaches your upload to a candidate profile recruiters skim inside the platform. They see a parsed text view alongside or instead of your original PDF. Bullets exist to create skim points: scope, tool, outcome, one per line. When import flattens them, every metric competes in one paragraph and ctrl-f still works but the six-second scan fails.
The standard your file is judged against: each role shows an employer line with Month Year dates, then three to five bullets where each line starts with a plain character and a line break the Notepad paste preserves.
A composite product manager whose PDF shows neat arrows beside each win but Greenhouse imports one block reading owned roadmap prioritized features launched campaigns loses to the same content with hyphen bullets and line breaks intact. Same facts. Different skim surface.
I've screened Greenhouse stacks where the candidate's top bullet held a seven-figure revenue line buried mid-paragraph because Canva exported the experience section as a single text box. The recruiter never reached the number because the parsed view looked like duties prose.
Edge case: resume built in Google Docs then downloaded as PDF. Docs lists usually parse fine if you used the native bullet button. Problems start when you paste bullets from a website or PDF into Docs without clearing formatting. Strip formatting, reapply native lists, download again.
Edge case: LaTeX or academic CV templates. They often produce beautiful PDFs with parser-unfriendly encoding. For US corporate Greenhouse reqs, keep a parallel Word plain export with hyphen bullets even if you send the academic PDF elsewhere.
Read Workday vs Greenhouse vs Lever parsing differences when you apply through multiple ATS types and need one master file that survives each portal.
Greenhouse parsing: six before/after bullet pairs
Each pair keeps the same candidate facts. Only bullet structure changes. Run Notepad paste after every fix.
Pair 1: Software engineer
Before: Arrow glyphs and tab-indented lines inside a two-column template. Greenhouse import: one paragraph under Senior Engineer.
After: Plain lines: Rebuilt billing service in Java on AWS for 2.1M monthly invoices; cut P99 latency from 840ms to 310ms. Each bullet on its own line with Word list style.
Pair 2: Marketing manager
Before: Experience rows in a Word table with bullets inside cells.
After: Table removed. Company line plain text. Bullets: Ran HubSpot nurture for 38K-contact list; lifted MQL-to-SQL from 11% to 16% in two quarters.
Pair 3: Registered nurse
Before: Checkmark bullets copied from a template site.
After: Standard round bullets: Staffed 32-bed med-surg unit in Epic; averaged 5:1 ratio on day shift and precepted 4 hires in 2025.
Pair 4: Operations lead
Before: Bullets typed as manual dots with spaces, mixed with hard line breaks inside a text box.
After: Hyphen-space at line start, no text box: Ran 220K sq ft DC with 85 staff; lifted on-time ship from 94% to 98% in two quarters.
Pair 5: Financial analyst
Before: PDF exported from InDesign with custom bullet font.
After: Rebuilt in Word: Built SQL and Tableau pipeline for 9-entity forecast; shortened monthly variance review from 5 days to 2.
Pair 6: Customer success manager
Before: Semicolons instead of bullets to save space in a one-page design.
After: Full bullets restored even if file runs to two pages: Owned $4.2M ARR book in Gainsight; lifted gross retention from 91% to 96% in FY2025.
Pair 7: Project manager (hybrid role)
Before: Bullets inside a shaded text box with custom wingding markers from a downloaded template.
After: Plain list: Delivered SAP cutover for 3 warehouses on time; reduced downtime tickets 28% in first quarter post-launch. Each line survives Notepad paste.
Copy-paste Greenhouse bullet export rule
Copy-paste before every Greenhouse apply:
1. Select Experience section → Clear formatting
2. Reapply Word bullet list or type hyphen-space at each line start
3. Remove tables, text boxes, and sidebar columns
4. Save DOCX; if PDF required, export from Word only
5. Paste file into Notepad: each bullet = its own line
6. If lines merged, fix source file before upload
Read impact-first resume bullets US hiring teams prefer once structure survives import and bullet one still needs scope language.
What flattened Greenhouse files still share
Designed templates from graphics tools. Pretty PDF, single import block. Rebuild in Word for Greenhouse uploads.
Bullets as semicolon chains. Saves space on paper, removes skim points in parsed view. Use real line breaks.
Mixed bullet types per job. Arrows on job one, hyphens on job two. Pick one style for the whole file.
Nested lists three levels deep. Sub-bullets often flatten or drop. Flatten to single-level bullets with compound sentences if needed.
Assuming keyword density fixes structure. Stuffing Skills while Experience stays in a text box changes nothing in the recruiter skim view.
Edge case: mobile apply through Greenhouse where you upload from phone gallery. Camera PDFs sometimes OCR badly. Email yourself the Word export from desktop, then upload from a laptop when possible.
Edge case: resume parsing preview looks fine but recruiter still sees issues. Some companies run a second parser on forward. Keep the plain Word master as the source of truth and re-export after every content edit.
Greenhouse isn't punishing your content. It's reading the file you gave it. When startups scale hiring, they rarely customize parser settings per req. Your export either survives the default import or it doesn't. Plain structure is the lowest-friction path through a default pipeline used by thousands of employers.
Coordinators forwarding candidates to hiring managers often paste parsed text into Slack or email. If your bullets flattened, the forward shows a paragraph your champion can't skim. Fix line breaks and your internal advocate can quote bullet one without retyping your wins.
When you interview and the hiring manager says they loved your background, ask which version they read: attachment or parsed profile. If they only saw the paragraph, offer to resend a clean export. That's not awkward. It's fixing a technical failure they didn't know you had.
Candidates often rewrite bullet text five times while the export method stays the same. If Notepad still shows one paragraph, new verbs won't help. Swap the container first: out of tables, out of text boxes, into Word's native list. Then tune the words inside each line.
Greenhouse isn't the only ATS that flattens bullets. The same fixes survive Lever and many Workday imports because the failure mode is shared: decorative structure that doesn't survive text extraction. Build one plain master and you're covered for most US corporate portals you'll touch this quarter.
Parse check before you reapply
After you rebuild bullets, run a free ATS check with the job description pasted in. Confirm must-have terms still appear inside parsed Experience lines, not only in a Skills footer that imported cleanly while bullets flattened.
When the req asks for a cover letter in Greenhouse, generate a cover letter that repeats bullet one scope in prose. Letter and resume should match; neither rescues a flattened bullet block on its own.
Rebuild bullets before the next Greenhouse apply
Greenhouse parsing why your bullets disappear comes down to import flattening, not a secret keyword penalty. Custom glyphs, tables, and text boxes merge line breaks recruiters depend on. Plain Word lists, hyphen bullets, and a Notepad paste test fix most US uploads without touching your achievements.
Open your master file tonight. Clear formatting on Experience. Rebuild bullets. Paste into Notepad. Upload when each line stands alone. This won't fix applying to roles you're not qualified for. It stops strong bullets from dying as a paragraph nobody skimmed.
Keep a Greenhouse-safe master and a designed copy if you need both. Label them in your folder so you don't upload the wrong one at midnight. Boring filename Greenhouse_Export.docx next to Designed_Networking.pdf saves you from repeating the same flattening mistake on every apply.
Read more
Frequently asked questions
Greenhouse reads a text stream from your upload, not the visual PDF. Custom bullet glyphs, text boxes, and table cells often flatten into one paragraph or drop line breaks entirely. Your screen still shows dots. The recruiter view shows a wall of text with no skim points. Rebuild bullets with Word's standard list button or plain hyphens, then re-export and paste into Notepad to confirm each bullet starts on its own line.
Try DOCX first when the portal allows it. A clean Word file with built-in list styles usually preserves line breaks better than a designed PDF from a graphics tool. If the employer requires PDF, export from Word after you fix bullets, not from Canva or InDesign. Always verify with a plain-text paste before you assume the portal sees what you see.
No. Keywords inside a single flattened paragraph still read as one block. Recruiters ctrl-f terms but skim bullet boundaries first. If every achievement merged into one line, scope and outcomes hide together. Fix structure, then tune keywords in bullet one under each employer.
Standard round bullets from Word or a simple hyphen with a space at line start. Avoid arrows, checkmarks, stars, and emoji. Avoid manually typed bullet characters copied from websites; they sometimes encode as special symbols that import as blanks. When in doubt, hyphen-space at the beginning of each line parses more reliably than decorative symbols.
Yes if the portal lets you replace the resume or if a recruiter asks for an updated copy. Rebuild the file, paste into Notepad to confirm line breaks, re-upload or email the corrected PDF with the req title in the subject. Note in one sentence that you fixed formatting so bullets parse cleanly. Do not resubmit five times without a change.