By J.M. Auron Quantum Tech Resumes
These days, apparently, most job seekers are afraid of the Big Bad ATS.
And, with the endless drumbeat of horror stories about the ATS destroying careers? It's pretty understandable that people are nervous. So I'd like to follow up my earlier post on IT resume misinformation, and try to relieve some of the anxiety that's come to surround Applicant Tracking Systems.
Now, don't get me wrong. ATS systems are far from ideal. But I believe - based on many years as a professional IT resume writer, as well as my own research - that the ATS may not be the bogeyman it's often made out to be.
What is ATS and how to deal with it
People often see "getting through the ATS" as the biggest challenge in the job search. It's really not, though. Getting through the ATS - and I know this goes against the conventional "wisdom" - isn't that difficult, and shouldn't be the focus of your resume writing.
So let's break it down a bit.
1) Getting Through the ATS isn't that Hard
I know. I just said that. It bears repeating, though, given the fear-mongering online and on social media.
From the research I've done, 80%-95% of all decently written, decently formatted resumes get through the gatekeeper.
Decently formatted just means a simple, readable, reverse chronological framework with clear section headings. The problem comes when there are multiple columns, tables, graphics, or very unusual fonts. The ATS can't read that, but, honestly, they're hard for humans to read, too.
So keeping things simple, clear, and straightforward is likely to improve your chances with both the ATS and the humans who are really making the decisions.
2) You Don't Need a 100% Keyword Match
In fact, a keyword match that high (if it's even possible) looks over-optimized, as though you've just copied and pasted the job description.
Recruiters are hip to that - so even if you do get through the ATS with an overly optimized IT resume, you may well not get past the human being making the decision.
It's a bit like Google. Keyword stuffing is more likely to get a site lowered rather than raised.
The general rule of thumb is that you need a keyword match around 70%-80%. That's not really that hard, though it sounds like a high number. If you're a Cloud Architect, for example, a lot of what you've done is going to overlap with any decently written job description (I know, of course, that not all are decently written, but that's not something we can control).
So if you talk clearly about what you've done, and naturally weave in the skills and tools you've used, the keyword matching will actually happen fairly automatically.
I'm not suggesting that you don't read job descriptions carefully, but focus on the places where all the job descriptions match, rather than on a few outliers.
3) AI Hasn't Taken Over the Hiring Process!
I'm not, in general, a big fan of AI - or at least of the AI hype we're all bombarded with.
But from everything I can find, AI has not taken over ATS systems. They are still pretty close to what they've always been. AI is used to automate some tasks nowadays. More importantly, AI may be used for more semantic keyword matching - "cloud computing" can now match "AWS expertise" - for example. That's actually a positive; semantic keyword matching makes writing a resume that reads naturally much, much easier.
But AI has not become a demonic (or hopelessly inefficient) entity committed to destroying your careers. It's not even mucking up the works as much as in some other areas - at least at this point.
Bottom Line?
There's a lot to be concerned about in the job search. Things aren't easy. But the hype about the Big Bad ATS, in my view, is just adding to the many worries that job seekers already have. That's not a good thing.
So I recommend writing a good, solid, clear IT resume that tells your career story. If you do that well, the keywords - and the ATS - should take care of themselves.
Bio:
I'm J.M. Auron and I've owned one of the to...