7 min read · Parsed record first
You hit submit and wait. Meanwhile the file gets text pulled into fields you've never seen. That's the screen recruiters sort before they download anything.
It isn't personal. The system's building a row it'll sort against hundreds of others, and you won't see that row unless you open preview.
Check your resume for free against the posting, then open the portal's application preview if it offers one. You're matching what they'll scan, not what your Word doc looks like on your laptop.
This won't get you hired for a role you're underqualified for. It stops a strong background from looking blank because a column shoved your latest title into a skills bucket.
Quick wins
- Open application preview and confirm current title and employer imported.
- Paste plain text from the file; if order scrambles, flatten to one column.
- Align knockout answers with the same facts on the resume header.
What happens in the first minute after submit
The portal stores your file, any screening questions you answered, and metadata like source and timestamp. A parser tries to map text into employer, title, start date, end date, school, and skills.
What gets captured besides the resume?
Form fields often override the file. Work authorization, salary expectations, and relocation answers can filter you before a human opens the profile. LinkedIn imports add a second timeline that recruiters compare to the PDF.
What if parsing stalls?
Some builds show a partial profile until processing finishes. Others let recruiters open the attachment while fields stay empty. Either way, an empty Experience block reads like no recent job, not like a formatting quirk.
Pattern to expect: upload completes, fields populate or don't, match band appears, your row lands in a sorted list. Recruiters work that list; they don't re-type your resume by hand.
Parsed profile vs the resume you designed
Your PDF can have clean margins and a color accent. The ATS view is closer to a database row: job three might show without bullets if the parser missed the section break.
Before: Two-column template. Left rail holds contact and skills. Right rail holds jobs. Preview shows skills duplicated and only two roles imported.
After: Single column. Contact on line one. Experience with Company, Title, City, Jan 2022 to Present, then bullets. Preview shows four roles in order.
I've screened Greenhouse queues where the attachment was polished but the profile showed a blank current title. Recruiters assumed a gap and moved on before opening the PDF.
Copy-paste header block for portal preview checks
Name | Target title from posting
City, ST | phone | email
Experience: Company | Title | Mon YYYY to Present
• First bullet mirrors a must-have from the job description
Read resume formatting errors that break ATS parsing when preview and PDF disagree.
What recruiters see after you click apply in the queue
High-volume reqs turn into tables. Recruiters scan columns before they read prose. Typical fields include name, current title, location, application date, match band, and status flags from knockout questions.
Do they see a match score?
Many teams sort on a match or ranking signal tied to posting language. It's triage, not a hire decision. Thin proof with keyword overlap can still rank oddly once a human opens bullet one.
When do they download the file?
After the row passes filters and the recruiter wants detail. Some never download and work entirely inside parsed fields. That's why empty imports hurt even when the PDF is strong.
Greenhouse ATS: how recruiters screen your resume walks one platform's flow if that's where you're applying.
When silence means the record broke, not the fit
No reply can mean volume, closed req, or internal hire. It can also mean your profile never presented as qualified because dates attached to the wrong employer or skills never left the sidebar.
Check these before you blame the market: current title field populated, last job end date not in the future unless you marked present, degree line readable, posting must-haves appear under a job with dates.
Before: Knockout answer says no sponsorship while resume header lists a work visa note in a text box the parser skipped. Record flags mismatch.
After: Same facts in plain fields on the form and in the resume header so humans and filters agree.
Test before the next apply
Run the export you'll upload through the free ATS resume checker and paste plain text from preview when the employer shows one. You're confirming fields, not font choice.
Then score your job match on the cleaned file so posting language ties to employer lines recruiters will actually sort on.
What to verify tonight
Recruiters live in the import view. Flatten layout, align form answers with the resume, and confirm experience order in preview. Then apply once with the file that matches the record.
Run a free resume check on that export. It's the same object the queue will sort tomorrow morning.
If a form question needs context the file can't carry, use the cover letter generator for one short paragraph that matches the imported timeline.
Read more
Frequently asked questions
Usually no. They see a candidate record built from your upload and any form answers. The PDF is often a second click. If parsing failed, the record looks empty even when the attachment looks fine.
Similar idea, not identical math. Their ATS also applies filters you cannot see from outside: location, work authorization, required degree fields, and knockout questions. A checker helps you test wording and parse. It does not show every gate.
Most portals lock the file. Some let you update profile data later, but the submission snapshot often stays. Treat the first upload as final. Reapply only when the posting still accepts new candidates and the employer allows duplicate profiles.
Headers, icons, and two-column layouts pull phone and email into the wrong field or drop them. Put name, phone, and email on plain lines at the top of a single column before you submit again.