Case Study: Glovis America — IT Security Analyst Before touching a single line, I checked the "Apply Here" URL on the job posting — it pointed to a Workday-hosted careers page, which told me exactly which ATS was parsing this resume before a human ever saw it. Workday's parser is notoriously literal: it rewards clean section headers, exact keyword matches to the job description, and standard date formatting — and it silently mangles tables, columns, and graphics that look great to the eye but return as garbled text on the recruiter's end. So the rebuild focused on what Workday actually reads: a single-column layout, skills grouped under headers that mirror the posting's own language (SIEM, NIST CSF, ISO/IEC 27001), and metrics pulled to the front of every bullet instead of buried at the end. Nothing flashy — just legible to the machine and compelling to the human who reads it next. Result: callback within a week of applying.

Case Study: Raytheon (RTX) — Senior Federal & Defense Sales Leader

Before editing anything, I checked the "Apply Here" link — it routed through RTX's Workday portal, so the resume had to survive an automated parse before any recruiter saw it.

Defense sales postings are dense with compliance language (FAR, IDIQ, BAFO, capture management), and Workday weights exact keyword matches heavily. The original buried contract vehicles, compliance terms, and dollar figures mid-paragraph instead of leading with them.

I restructured every bullet to open with the outcome and number — $1.6B task order, $65M program capture, $2B+ in federal offerings — and pulled procurement terms into a dedicated skills block mirroring the posting's own language. That gave Workday exact-match hits while staying readable for the hiring manager next.

Result: callback shortly after submission.