The Screening Questions That Come Before Parsing

A large part of what feels like resume screening is not screening your resume at all. Application forms ask structured questions — work authorisation, degree level, licence held, years with a specific tool, salary expectation, notice period — and the answers are stored as clean fields that filters can act on directly. Those fields are more decisive than your parsed document, and unlike your document, they are entirely under your control at the moment you fill them in.

Why employers ask instead of parsing

Consider the alternative. To establish from a resume whether a candidate holds a current nursing licence in Ohio, a system must extract the text, classify a section, recognise a credential name, resolve a jurisdiction, and interpret an expiry date — five inferences, each fallible, as described in how a degree requirement gets checked.

Or it can ask: “Do you hold an active RN licence in Ohio?” One dropdown, no ambiguity, one field.

Anything an employer genuinely needs as a yes/no gets asked. Parsing is for the messy, valuable, unstructured part of your history — what you did and when. It is not the mechanism for eligibility.

What gets asked, and how it is used

The common structured questions fall into a few groups:

Hard eligibility. Work authorisation, visa sponsorship, right to work in the country, minimum age, licence held, security clearance. These are typically genuine knockouts: a disqualifying answer removes the application from the pool, and often before a human sees anything.

Threshold questions. “Do you have a bachelor’s degree or higher?” “How many years of experience do you have with Python?” Often presented as a dropdown of ranges. These may be knockouts, may be scored, may be advisory.

Logistics. Notice period, earliest start date, willingness to relocate, on-site days, shift availability. Usually not knockouts, sometimes used for sorting, always read by a coordinator eventually.

Compensation. Expected salary, current salary where it is legal to ask. Handling this is a negotiation question that belongs to a different kind of site; mechanically, note only that a number typed into a field is stored and reused, and that “negotiable” or a range may or may not be accepted by the form’s validation.

Voluntary demographic questions. Ethnicity, gender, veteran status, disability. In many jurisdictions these are collected separately for reporting and are not meant to reach the hiring decision. They are almost always genuinely optional, and declining to answer is a normal response.

The custom-question trap

The questions most likely to catch you out are the ones the hiring team wrote themselves. A common shape:

How many years of hands-on experience do you have with [specific tool]? 0 / 1–2 / 3–5 / 5+

There is no partial credit, no context, and no place to explain. If you have two and a half years, you pick 1–2 or 3–5, and one of those is wrong. Round down: the answer you can defend in an interview is the one to give, and being asked to substantiate 3–5 when you have thirty months is a bad start.

Similarly common:

Are you willing to work on site five days per week? Yes / No

A No here can end the application even if the posting is advertised as hybrid, because the question was written by someone with a different assumption. There is nothing to be done about that except to answer truthfully and accept the outcome. A Yes you do not mean produces an offer you have to decline or a job you resent, which is worse.

Why accuracy here matters more than anywhere else

Two reasons, and both are practical rather than moral.

These answers are structured, so they are checkable. A claim buried in resume prose is fuzzy. A dropdown that says you hold an active licence, or that you have five or more years with a named tool, is an unambiguous assertion recorded with a timestamp. It is precisely the kind of statement that gets verified — licences directly with the issuing body, degrees with the institution, employment dates with the employer.

They are usually the first gate. A dishonest answer that clears the gate puts you in front of a technical interview built on the assumption that the answer was true. The gap surfaces in the first twenty minutes, and the wasted time is yours as well as theirs.

Where the form and the resume disagree

A specific and avoidable failure: the form says one thing and the parsed resume says another. Common versions:

• The form’s experience dropdown says 5+ years; the parsed date ranges add up to three, because two jobs lost their dates. See how software counts your years of experience.
• The form’s location is the city you are moving to; the resume’s contact block is the city you live in.
• The form’s current title is your normalised guess; the resume’s is your official internal title.

Sometimes the discrepancy is a parsing error and sometimes it is carelessness, and from the outside they look identical. A recruiter noticing a mismatch has to resolve it, and the cheapest resolution is to move on.

The fix is to fill in the form from the resume, deliberately, rather than from memory — and if a field on the form cannot be reconciled with the document, correct the document.

The autofill problem

Many forms offer to populate themselves from your uploaded file. This is parsing made visible, and it is the most useful diagnostic in the entire application process: what appears in those boxes is very close to what the parser extracted.

Read every prefilled box before submitting. If your most recent employer is wrong, or your title is a fragment, or a date is blank, you have just been shown a defect in your document — and you can fix both the form and the file. This is worth a post of its own; see when the application form autofills from your resume.

What none of this means

It does not mean the form is a filter to be beaten. Structured eligibility questions exist because employers have real constraints — legal ones, in the case of work authorisation and licensing — and answering them accurately is the only version of this that ends well.

It also does not mean your resume is unimportant. The form decides eligibility; the document and the record it produces decide whether anyone is interested. Both have to be right, and they have to agree.

Check it

Before you submit, screenshot or note your answers to the structured questions, then read the plain-text version of your resume against them. Every number, date, title, and location should match. Any field where you had to guess is one to check against the document rather than your memory — and any field where the document is wrong is a document to fix before the next application.