The application portal doesn't care that you ran a team of 80.

I had a moment last year that I think about a lot. I was in the middle of my own job search, applying for a Head of Infrastructure role at a fintech I'd genuinely admired for years. The application form had a field labeled "Years of experience with Kubernetes." A dropdown. The options went 0, 1, 2, 3, 4, 5+.

I had eleven years of production Kubernetes experience by then, including running it at a scale that most of the engineers reading my application hadn't seen. The dropdown had no way to communicate that. I picked "5+." I lost a recruiter screen to a candidate the system thought was a closer match because their resume listed Kubernetes more times than mine did.

That moment crystallized something I'd been suspecting for years: ATS systems were never designed for executives. They were designed to sort high-volume entry-level applications efficiently. They got bolted onto executive hiring pipelines because nobody wanted to maintain two systems.

What ATS was actually built to do

Workday, Greenhouse, Lever, iCIMS — these systems were built around a specific problem: a recruiter at a large company gets 800 applications for a software engineer role, and 750 of them are unqualified. The ATS exists to filter out the obvious noes so a human can spend their time on the maybes.

That logic works at the IC level. The signal-to-noise ratio is genuinely terrible. Keyword matching is a crude tool but it's better than nothing.

At the executive level, the math inverts. A VP Engineering search at a Series C company might get 40 applications. Most of them are at least roughly qualified. The bottleneck isn't filtering — it's understanding. Did this person actually scale an org from 25 to 120, or did they sit on top of one that was already 100? Did they own that platform migration or just attend the meetings? An ATS literally cannot answer those questions.

"The systems we have for filtering executives are the systems we built for filtering interns. We're surprised it doesn't work."

What "trying to game the ATS" actually does

The cottage industry of "ATS optimization" tools — Jobscan, Resume Worded, half a dozen others — exists because senior people sense that the system is broken and want a fix. The fix they're sold is: stuff your resume with the exact keywords from the JD. Match the percentage. Get past the filter.

This works approximately as well as you'd expect. Three problems:

• Keyword stuffing makes your resume worse for the human reading it. If you list "stakeholder management, executive communication, cross-functional collaboration" three times in different sections, you've made yourself sound like a LinkedIn buzzword generator. The hiring manager sees the same JD you did. They notice.
• Most senior roles bypass the ATS anyway. When a CTO search firm submits you, they upload your resume directly to the hiring manager. When you get warm-introduced by a board member, the hiring manager opens your PDF themselves. The ATS only kicks in for cold applications — which is the lowest-yield channel for senior roles.
• You spend the wrong time on the wrong problem. Every hour you spend trying to outwit a Workday parser is an hour you didn't spend on warm introductions, hiring manager research, or interview preparation — all of which actually move the needle.

What works instead

The senior leaders I've watched land roles in the last 18 months had three things in common. None of them involved the ATS:

1. They had a tight master narrative. A specific positioning statement they could say in 90 seconds, with three or four real accomplishments backing it. When they applied for a role, they tailored from this narrative — not from scratch, not from a generic resume. The result was applications that felt purpose-built rather than mass-produced.

2. They worked the warm path before the cold one. For every cold application they submitted, they tried to find a warm path first. Board member who knew the CEO. Former colleague at the company. VC who had recently led their round. The ATS path was a fallback, not a default.

3. They prepared for interviews the way executive recruiters prepare candidates. They researched the hiring manager. They read the company's recent press. They identified what the role's "hidden anxieties" were — what the company was really worried about beneath the JD's polite language. They walked into screens already knowing what to talk about.

None of this scales as a hack. It's just the actual work of running a senior search well.

Where I came out

I built JobSearchPrep because the tools available to me during my own search treated me like a fresh grad with a chip on my shoulder, and I knew the people in my situation deserved better. The product takes the three things above — master narrative, warm path discovery, interview preparation — and makes them tractable for someone who has eight other things going on.

It does not try to beat the ATS. It accepts that for senior roles, the ATS is the wrong battlefield, and focuses energy on the channels and steps that actually predict outcomes.

If you're in the middle of a search right now and you're spending more than 30 minutes per application optimizing for keyword density, please stop. Go work the warm path. Or, if you don't have a warm path, get the application out fast and spend the recovered time preparing for interviews you haven't been called for yet. The market is going to call you eventually if you're qualified — what matters is what you do when it does.