How we engineer résumés that survive the ATS at F1Jobs.io

Every job application at a mid-size or large US employer passes through an applicant tracking system before it reaches a person. For international students — filtered by visa questions, squeezed by OPT timelines, and often carrying résumés formatted for another country’s conventions — the ATS is where most applications quietly end. At F1Jobs.io, the NeuraScribe company built for exactly this population, résumé engineering for the ATS is the first thing we do for every candidate, and it is the reason the rest of the pipeline works.

This is a first-party piece: F1Jobs.io is our product. What follows is how the system actually works, because the mechanics are the argument.

What an ATS actually does with a résumé

The folk model of the ATS — a robot that reads your résumé and rejects it — is wrong in a useful way. What actually happens is closer to an ETL pipeline:

1. Parsing. The document is converted into structured fields: contact block, work history entries with dates and titles, education, skills. Parsing quality is the single biggest hidden variable. Two-column layouts, text inside tables or images, headers and footers, and decorative section names (“Where I’ve Made Impact”) all degrade extraction — and a field the parser missed is a field that does not exist.
2. Enrichment and matching. Parsed fields are normalized (titles mapped to canonical roles, skills to taxonomies) and scored against the job requisition. Modern systems increasingly use embedding similarity alongside keyword matching, but the job description’s own vocabulary remains the strongest signal.
3. Knockouts and ranking. Application questions — work authorization, sponsorship requirements, years of experience — act as hard filters. Everything that survives is ranked into the queue a recruiter actually reads, usually top-down under time pressure.

Nothing in that pipeline reads for elegance. It reads for extractability and relevance. That is an engineering target.

The F1Jobs.io résumé pipeline

Our pipeline is hybrid by design: LLMs do structure and coverage, recruiters own judgment and truth.

Parse-first formatting. Every résumé is rebuilt into a single-column, semantically-headed layout that parses cleanly in the systems that matter. We verify by round-tripping: parse the rendered document with the same class of extraction tooling the ATS uses and diff the structured output against ground truth. If a job entry loses its date range in the round trip, the layout is wrong, whatever it looks like.

Requisition-driven targeting. For each application, an LLM pass aligns the résumé’s vocabulary with the specific posting — the titles, skills, and phrasing the requisition itself uses — constrained to facts the candidate has verified. This is the line between optimization and fabrication, and it is enforced by a human recruiter, not a system prompt: nothing ships that the candidate cannot defend in an interview.

Knockout strategy. Visa and authorization questions are answered accurately and strategically — accurately, because lying to a knockout filter wastes everyone’s time including the candidate’s; strategically, because which roles to apply to at all is where recruiters earn their keep. A candidate with 18 months of OPT runway should not spend it on requisitions whose filters were always going to fire.

Execution and preparation. Résumé engineering feeds the rest of the service: recruiters run the application volume, and the interview side — preparation dossiers, mock interviews, positioning of LinkedIn and GitHub profiles — takes over for everything that survives the funnel. Candidates have landed interviews across technology, finance, automotive, and enterprise employers on this pipeline.

What we refuse to do

ATS folklore is full of tricks that used to circulate on forums: white-text keyword blocks, invisible fonts, stuffing the skills section with every framework ever released. We don’t do any of it. Parsers flag hidden text, duplicate-keyword density reads as spam, and every trick that survives the parser still has to survive the recruiter reading the ranked queue. The durable edge is boring: clean structure, honest content, requisition-specific vocabulary, and enough application volume executed consistently. Machines read first; people decide. Engineer for both, in that order.