Before I was a web developer, I was an HR guy who taught software developers how to grow their careers. Today, I wanted to share some behind-the-scenes info about how the hiring process work.
Did you know that most resumes aren’t ever seen by an actual person?
Let’s dig in!
Most resumes aren’t actually seen by a human at all
Before the internet, if you wanted to apply for a job you had to browse through job listing in the local paper and physically mail in your resume. It was time-consuming and friction-filled, and as a result, companies received a pretty manageable amount of applicants for jobs.
The web makes it insanely easy to find and apply for jobs. You can search by keyword for jobs anywhere in the world, and then apply with just a few clicks.
Originally, this was awesome.
You could easily find the perfect job, and employers could access a larger pool of applicants more easily.
And then the economy got bad
Suddenly, businesses were getting flooded with hundreds or thousands of resumes.
People were desperate for work. Many weren’t really qualified for the roles they were applying for. But the process is so frictionless, they sent their resumes in anyway.
There’s no way a recruiter could actually sort through all of those resumes.
So people built software to do it for them
An Applicant Tracking System (or ATS) is a piece of HR software that collects and tracks resumes.
It’s most powerful feature: automatically filtering resumes. Recruiters can provide keywords for each role, and the ATS scans resumes for those keywords and tries to determine how good of a match for the job the person is.
If the ATS doesn’t think you’re a close enough match, your resume never gets seen by a real person.
You’ve got 7 seconds
Depending on the role and the company, hundreds of resumes might still make it through the ATS. The role you’re applying for may be one of dozens that the recruiter is responsible for.
Your resume has an absurdly difficult task.
First, it has to make it past the ATS and get seen by a real person. Then it has to convince that person—in just seven seconds—to keep reading instead of putting it back in the stack.
Here’s the good news: now that you know how this process works, you can design for it.
In future articles, I’m going to share some of the things you can do to hack around this deeply flawed system.