How a Job App Letter Actually Gets Read
A Job App Letter is just a document that travels through a stack of filters before a human ever sees it. Most people write it like they are writing to a person sitting across a desk. That does not work because usually nobody sits there. It gets parsed by software, matched against keywords, scored, and then stacked in a pile that someone scrolls through quickly if they open it at all. I learned this the hard way with a candidate who sent me a beautifully formatted two-column PDF with icons, shading, and a skills chart. The ATS ate half the text, scrambled the order, and mapped her name to the date field. When I tried to read it, it came out as a wall of jumbled paragraphs with no structure. I asked her to resend it as a plain text file with section headers. She did, and suddenly the system parsed her experience correctly. That single change moved her from the rejected pile to the reviewed pile.
Building a Job App Letter That Survives Parsing
Start with the format, not the prose. Use a single column, standard fonts like Arial or Calibri at 10 to 12 point, and save as DOCX or PDF with selectable text, not an image-based PDF. Headers should use simple headings like Experience or Skills that the parser can recognize. Avoid tables, text boxes, columns, graphics, or anything that breaks the reading order. Screen readers and ATS engines read left to right, top to bottom, so anything that disrupts that flow disappears into garbage output. The content follows a very narrow structure. Open with one sentence stating the role you are applying for and where you found it. That matters more than you think because some systems tag your letter to a specific requisition code. Then go straight into the body. Three to four short sections work best: what you have done, what you can do for them, and a closing line. Here is a detail most people miss. The header of your document should include your name, phone number, email, and the job title you are targeting. Some ATS systems use the document filename and header metadata to auto-populate fields. I have seen a candidate named on the page but missing from the applicant profile because the system could not locate the name in the parsed text. Putting it at the very top of the letter in a standard format like Name: Jane Doe | Phone: 555-0100 | Email: jane@example.com solves that problem entirely.
For the experience section, do not paste your resume. Reference it and connect the dots. Recruiters already have your resume attached. They want to know why you are writing and which two or three achievements prove you can do this specific job. Pick numbers. Specific metrics travel better than vague claims. "Reduced processing time by 40 percent" tells them something. "Helped improve efficiency" tells them nothing. The keywords matter, but not the way people assume. Stuffing a job description verbatim into your letter is obvious and often counterproductive. Senior ATS systems have moved past simple keyword matching into semantic analysis. They look for context around terms, not just their presence. Instead of copying phrases from the posting, describe how you actually used those skills. If the job mentions "cross-functional collaboration," write about a time you worked with engineering and marketing to ship a feature, not just the phrase itself. There is a bottleneck most people do not anticipate. Some companies use multiple ATS platforms across divisions. A letter that parses cleanly in Greenhouse might fall apart in Workday or Taleo. If you are applying to a large organization, check whether they list a preferred application format on their careers page. Some explicitly state "PDF only" or "no more than 500 words." Ignoring those instructions gets your application filtered out before any human judgment enters the process.
Get the Full Details
Writing the actual prose is simpler than most people make it. Keep sentences short and direct. One idea per sentence. No flowery language, no exaggeration, no filler phrases like "I am thrilled to apply" or "I believe I would be a perfect fit." Those lines consume word count without adding information. Replace them with a factual statement about what you want and what you bring. "I am applying for the senior data analyst role because my three years of experience building SQL pipelines aligns with your team’s current migration project." That is one sentence that does the job of five. Length matters more than people realize. A Job App Letter between 250 and 400 words is the sweet spot for most systems. Anything over 500 words starts getting truncated by poorly configured parsers or ignored by overworked recruiters scanning hundreds of applications. I have read letters that were essentially short essays disguised as cover letters. They got rejected not because the content was bad, but because the recruiter spent eight seconds on them and moved on. Brevity is not a stylistic choice here. It is a survival mechanism. One edge case that catches people off guard. If the job posting asks for a writing sample, portfolio link, or specific response to a prompt, your Job App Letter needs to address that directly in the first paragraph. I once had a candidate who wrote a strong generic letter and attached the requested portfolio separately. The recruiter never found the attachment because the application portal had a separate upload slot that she forgot to use. The letter itself was fine, but the incomplete application sunk her. Always cross-check the posting requirements against your submission before you hit send.
If you want a template to start from, download a plain-text version with section breaks and placeholder fields already formatted for ATS compatibility. Save it in your own style, fill in the real details, and verify the output by copying the text into a plain notepad viewer to check the reading order. That alone catches most formatting problems before submission.
