About this template
The ATS Pipe Contact template is an ATS-safe cover letter where contact details run on one horizontal line separated by pipe characters: email | phone | city | LinkedIn. Saves vertical space without compromising parsing — every recruiter sees the contact block at a glance, and every parser extracts the four elements as a standard text line with Unicode separators. The rest of the letter follows the classic ATS layout: neutral sans-serif, one column, three paragraphs.
Who is it for?
It suits candidates with a dense profile (multiple roles, certifications, languages) who need every line for the message itself. Particularly suited to senior engineers (mechanical, electronics, embedded software), technical consultants (IT architecture, cybersecurity), data profiles with multiple cloud certifications (AWS, GCP, Azure), and PMP-certified project managers. Any context where a verbose contact block would waste line space better spent on quantified achievements.
How to use it
Order the contact items by recruiter priority: email first (primary channel), phone (second), city (location filter), LinkedIn (profile validation). Avoid adding a fifth item (portfolio, GitHub) that overloads the line — keep it for the footer signature. For engineers applying to Boeing, Lockheed Martin, Raytheon or BAE Systems, the city (Seattle, Marietta, Waltham, Preston) acts as a mobility signal. For technical consultants applying to Accenture Technology, Capgemini, IBM Consulting or DXC, add the metro area if you are in a major hub — a recruiter sees the difference between Manhattan and Newark in commute terms. The 'one-line contact ATS cover letter' search is niche but converts on technical roles.
Frequently asked questions
Do pipe characters pass every ATS?
The pipe character (|) is standard ASCII (code 124) and read by every modern parser (Workday, Taleo, SmartRecruiters, iCIMS, Lever, Greenhouse). Ornamental visual substitutes (typographic separators ⫶ or ❘) do not pass — stay on the standard ASCII pipe. For a softer alternative, the em-dash (—) also works but consumes more horizontal space.
Should there be spaces around the pipes?
Yes, mandatory: 'email | phone | city' not 'email|phone|city'. Parsers recognise space-separated items more reliably, and human readability is markedly better. English typography uses a standard space around the pipe; a thin space is overkill in practice. Spaces around the pipe are the universal standard.
Should the ZIP code follow the city?
For US applications in metro areas where multiple cities share a name (Springfield Illinois vs Springfield Massachusetts), yes — ZIP code after the city to remove ambiguity. For New York, Chicago, Los Angeles, San Francisco, the city name alone suffices. Avoid the full nine-digit ZIP+4 which reads bureaucratic — use the five-digit ZIP, or for UK applications the outward postcode (SW1, EC2) is the standard convention.
