9 min read · Parse, knockout, queue
The portal says received, then nothing. Your brain imagines one evil algorithm tossing résumés. In most US corporate reqs, the story's flatter: import text, knockout fields, and whatever filter a recruiter clicks first.
Check your resume for free on the file you plan to attach. If import can't read your current title on line one, later keyword edits won't matter. You're fixing gate three while gate one never opened.
Below you'll get grouped checklists by gate, a table you can scan in thirty seconds, two before-and-after import fixes, and a copy-paste pre-upload block. Job searching's draining; this isn't a pep talk. It's a sequence you can run once per application.
When the posting wants a letter, draft it after import passes using the cover letter generator so you don't polish prose on top of scrambled job titles. If you're rushing, run gate one only and come back for the rest.
Quick Wins
- Copy extracted text from your export before you open the portal.
- Answer knockout questions honestly; don't chase reqs you can't clear.
- Mirror posting job title language in your header when it's accurate.
Three gates hiring software uses before you get a call
Import, knockout fields, recruiter filters. Vendors differ, but the sequence repeats. Each gate drops people for different reasons. Chasing keywords while import mangled your employer name is the most common time sink.
| Gate | What it checks | Typical symptom |
|---|---|---|
| 1. Import | Can the system read titles, dates, contact lines | Blank employer fields, merged words, missing skills block |
| 2. Knockout | Hard reqs on forms: geo, auth, years, license, salary band | Instant rejection email before attachment review |
| 3. Recruiter view | Search terms, sort order, status tags, manual review | Applied status forever while posting stays open |
I've screened stacks of applicants in Greenhouse after import, and the file that survives is never the fancy one. It's the boring single column that still reads employer and title on line one.
For the visibility story after import, read how hiring software decides who gets seen . This page is the pre-upload checklist so you know which gate to fix when silence hits.
How hiring software filters candidates: checklist by gate
Work gate one to three in order. Stop when something fails and fix before you continue. Times are targets for a file you already tailored once.
Gate 1: Import and layout (about 4 minutes)
- Export the PDF or DOCX you will upload, not the editable draft with track changes.
- Paste all text into a plain editor. Job titles and employers should appear in work-history order.
- Use a single column, 11-point Calibri or Arial, standard headers: Experience, Education, Skills.
- Remove tables, text boxes, and icons that replace phone or email text.
Before: Two-column header puts name left and contact right; extracted text shows phone before current title.
After: Contact block stacked under name; extracted text reads title, employer, then dates on the next lines.
Gate 2: Knockout and portal fields (about 3 minutes)
- Read required questions before you attach. Salary, work authorization, and relocation are common hard stops.
- Match years of experience to what your resume dates support. Don't round up into a senior band you can't defend.
- Type employer names exactly as they appear on the resume. Payroll abbreviations confuse later search.
- Skip reqs with licenses or degrees you don't hold. No attachment saves a false yes on a knockout.
Before: Portal asks for five years of SaaS sales; resume dates show three years in retail plus one year SaaS.
After: Candidate applies to a mid-level posting that matches three years SaaS, or updates bullets to show SaaS scope without inventing tenure.
Gate 3: Recruiter match signals (about 3 minutes)
- Highlight three must-have phrases from the posting. One should land in the first eight words of bullet one.
- Align headline job title with posting language when truthful. Internal payroll titles can stay in parentheses.
- Put tools you used in bullets, not only in a long Skills comma list.
- Save as FirstName-LastName-Role.pdf with no version numbers in the name.
Copy-paste pre-upload block (fill before submit):
File I will upload: _______________________
Parser read title on line 1? Y / N
Knockout questions answered honestly? Y / N
Posting phrase in bullet one? _______________________
Employer names match portal fields? Y / N
Filename: FirstName-LastName-Role.pdf
Numbers inside sample bullets elsewhere on HireFlow are illustrations, not market stats. Your checklist is about readable structure and honest answers, not stuffing keywords into white space.
When import keeps failing, start with resume rejected by ATS: what to fix first for parser fixes before you rerun gate three edits.
Fixes aimed at the wrong gate
Keyword stuffing Skills while import drops your title. Gate one still failed. Fix layout, then move posting language into bullet one.
Uploading a new Canva template under deadline. Fresh layouts reorder sections on import. Tailor in place on the file that already parsed once.
Lying on authorization or years to clear knockout. You might get past the form and still fail background or the hiring manager screen. Apply where answers stay true.
Chasing hidden text tricks. Modern imports flag odd encoding. Honest wording in visible bullets beats invisible strings.
Mass applying with one generic file. Gate three match signals need posting language in the top bullets. One file for every req keeps you at the bottom of sort views.
Match file to posting before filters run
Run the free ATS resume checker on the export you will attach. Confirm employer lines and skills survived import. That is gate one in software form.
Then paste the posting into job match score to see which requirements still sit only in Skills instead of bullet one. Move one proof line up before you submit.
Run the list tonight
How hiring software filters candidates stops being a black box when you name the gate. Import, knockout, recruiter view. Fix the earliest failure first, then rerun the copy-paste block on the next application.
- Read extracted text before every upload.
- Answer knockout questions only on reqs you truly match.
- Put posting proof in bullet one, not a Skills paragraph at the bottom.
When you're ready to submit, run a free resume check on the final PDF so gate one passes before the portal timer starts.
Read more
Frequently asked questions
Most corporate stacks run import first, then apply knockout rules on location, work authorization, or years of experience, then show recruiters a filterable list. Scoring labels vary by tenant. A strong file can still sit untouched if nobody opens the req or clears filters.
File import. If the parser drops your job title, merges employer lines, or scrambles dates, later keyword logic works on bad data. Fix export and layout before you worry about Skills density.
Yes, when the posting requires answers the system treats as hard requirements. Salary above band, missing license, or location outside the geo fence can end the application before attachment review. Answer honestly and only apply when you truly match.
Often yes if they widen search or sort by apply date. Default views highlight posting matches. Low overlap can leave you at the bottom of a long list even though your row exists.
Use what the portal requests. When PDF and DOCX are both allowed, test extracted text on the file you will upload. Format swaps without a parser check can introduce new layout bugs under deadline pressure.
