How to Find Out What ATS a Company Uses Before You Apply

Finding a company ATS before applying matters because ATS records start with extracted text, not the polished page you see in Word, Figma, or a PDF viewer. Workday uses the uploaded file to populate fields like title, skills, company, and dates, so greenhouse.io URLs must appear as selectable text instead of a decorative label. You'll get a cleaner record when the section order matches the job description.

how to find what ats company uses becomes easier to optimize when you separate mechanism from myth. You can often identify the ATS from application URLs, embedded forms, source code, and browser-plugin signals before you upload a resume. For example, lever.co postings and myworkday.com portals should sit in body text near Experience or Skills, because Greenhouse can miss signals buried in sidebars, images, or odd reading order. Short checks catch this fast.

The practical detail recruiters notice is rarely the fanciest design choice. In Workday, the title line, date order, and first six skills either line up or they don't, and a resume that says SmartRecruiters embeds clearly beats one that relies on a stylish graphic. That small ordering habit protects the candidate record before a human skim begins.

The first failure pattern hides the strongest keyword in a visual element. Workday may extract a title and dates while losing greenhouse.io URLs, which makes the resume look less relevant even when the page looks polished. You don't need a louder design; you need the same term visible in the raw text.

The second failure pattern uses a broad substitute for the exact field. A resume that says lever.co postings loosely can miss a Greenhouse filter written for what ats does company use, find company ats system, or myworkday.com portals. The human observation after a few applications is plain: the rejected resume often used softer words than the posting.

The third failure pattern exports a file that changes reading order. Greenhouse can show SmartRecruiters embeds after Education, Bullhorn can append agency notes after the skills list, and Workday can drop header or footer content depending on the file. Use /ats-checker after export, because the final file is the only version that counts.

The correct approach starts with the job description and ends with a parse check. Pull what ats does company use, find company ats system, and identify company applicant tracking system into real bullets where they describe work you actually did, then place greenhouse.io URLs and lever.co postings near the role most likely to be filtered. Exact terms work best when they sit beside evidence.

You should keep the format intentionally plain where the ATS reads first. Use standard headings like Experience, Skills, Education, Certifications, and Projects, because Workday and Greenhouse map those labels faster than clever section names. The page can still look clean; it just can't make myworkday.com portals depend on a graphic.

Use ProfileOps after the rewrite, not only at the end of the week. Upload the file, run /ats-preview, and compare the extracted text to the posting while SmartRecruiters embeds is still fresh in your mind. The five-minute check usually exposes one missing term, one broken date, or one weak title.

Testing works because it shows the same evidence the system sees first. Open /upload, add the final file, and inspect whether greenhouse.io URLs, lever.co postings, and myworkday.com portals appear in the first half of the parse. Workday won't credit a skill that disappeared during export.

Then compare the raw parse to the job description instead of rereading the designed PDF. If the posting repeats what ats does company use three times and your extract never shows it, Greenhouse has a weaker match to score. This is where many strong applicants discover that a header, footer, table, or text box stole the term.

Finish with a recruiter-style skim. Read the parsed text for 30 seconds and check whether the first role, first skills, and first credential tell the same story as the job title. When SmartRecruiters embeds appears late or out of order in Greenhouse, move it up and test again before submitting.

The first mistake treats how to find what ats company uses as a design preference instead of a data problem. A polished PDF can still lose greenhouse.io URLs in Workday, and a plain one-column file can score better because every term remains searchable. The parser rewards text discipline before taste.

The second mistake stuffs the keyword list without proof. Greenhouse and iCIMS both give recruiters enough context to spot a Skills section packed with what ats does company use, find company ats system, and identify company applicant tracking system but no matching bullets. Use fewer terms and attach them to real work.

The third mistake skips the final export check. Google Docs, Word, Canva, Illustrator, and PDF converters can all change reading order, so yesterday's clean draft doesn't guarantee today's upload. Test the exact file, especially when LinkedIn Apply flow sits near a margin or graphic.