Your Resume Sucks (and How to Fix It): The first half page

I have been unemployed for many months, but after over a hundred resumes sent out, I have been dismissed left and right as unsuitable. Many of my resumes did not even generate a rejection notice.  They were so bad, they probably got filed as spam. I've even interviewed once or twice but did not pass the first round, even for pretty much entry-level positions. 

So what was wrong? Apparently, my resumes really do suck. I used to just list what I did, cramming as many keywords in as possible. That does NOT work.  

Modern hiring managers and/or screener sdon't read the resumes from beginning to end. They don't have the time. Instead, they use a program called ATS (applicant tracking system). 

First, your resume goes through ATS (applicant tracking system), which uses AI and NLP to pull out keywords that supposedly match what the position is looking for and rates your resume, then dumps those that don't meet a certain minimum rating. 

BONUS TIP: If you applied but never got a reply, your resume sucks so bad, it was discarded by the ATS. 

The resumes that make it past the ATS will then be scanned (NOT read) by the hiring manager. And only the top 1/3rd, maybe 1/2 page, i.e. the name and initial summary of qualifications, will be scanned. You have a VERY LIMITED space to make a good impression on WHY they should read the rest of the resume. 

Once you caught their attention, THEN they would want to read the rest of your resume. If they decided it's not worth considering, you get the dreaded "After careful consideration, we are not moving forward..." rejection notice. If they decided you look interesting enough to warrant a look, a screener then calls you up and do a preliminary interview (aka "round 1"). 

If you are used to writing or scriptwriting, think of the top of the resume as the synopsis. You need to write enough (like an "elevator pitch") about yourself that the hiring manager or screener would want to read the rest of your resume to find out more about you. 

This also means you HAVE to tailor your story (aka your "branding") to fit the position... First, you need to fit in enough keywords to get past the ATS, then put in a summary interesting enough to catch the hiring manager's interest. Then finally, make the rest of your resume interesting enough to read instead of being round filed (i.e. recycle bin). 

Let's say you are applying for a webdev job. (This blog is "KC on WebDev", right?)

So tell me, why should I hire you for a webdev job instead of one of the bazillion candidates out there? What makes you special? 

If you reply with a standard pitch such as 
Software engineer with 5+ years of corporate app development and technical support experience, from requirement gathering to delivery and support; oral and written communication with all user levels; customer service experience, adaptable to rapidly changing environment

I'd just yawn... "Next!"

Why? You've not demonstrated anything really outstanding. Okay, you know DOS from Windows. You can read product specs. You can talk with users and your manager. You've written a few apps. You claim to be adaptable. Normal stuff, something everybody has or claims or does. And I am hiring a webdev, not tech support or app developer. This summary statement tried to cover "all bases" and is NOT tailored to a webdev position. It is just a LOUSY summary for a webdev position. 

You need to stand out, without lying. 

But if your pitch was instead:

Results-driven certified full-stack developer with experience in strategic problem-solving, process improvement, and out-of-box thinking. Excellent verbal and written communication skills with customer engagement. Innovative solutions with MS SQL and MySQL, Node.js, React.js, Bootstrap, RESTful API, Python, and more.    

Did you notice the difference? Now that tells me a lot more, even though it roughly says the same thing, as it crammed a lot more keywords and sounds far more impressive. I really know how to solve problems from specs to deployment! I'm certified in full-stack! I know how to engage customers and can speak and write nicely! I know that tech stack and more! Now there is someone I may want to hire!

There are tools like JobScan.co that will analyze a position's listing for you and tell you how suitable your resume is (i.e. its chances of making it past the ATS) by analyzing the listing and compare it against your resume. 

There is also software like Rezi or Resoume that helps you write such a resume. Whether they are any good is anyone's guess. 

But they aren't required. You can use JobScan, or you can highlight keywords in the position ad yourself and try to fit those keywords into your resume and cover letter. 

Then you will get your resume past the ATS. 

And the rest is up to you. 

The next post will be about how to word the rest of the resume to SUPPORT your story. But to give you a preview... 

If you are looking for a webdev position, and you listed a bunch of tech support jobs, you have to explain WHY those job experiences are relevant of you getting a webdev position. Did you do tech support for a webdev company? For a webdev tool provider? Or did you just answer questions about Windows and printers and stuff unrelated to webdev?   



Comments

Post a Comment

Popular posts from this blog

Yet another take on recursion

Recursion is often one of the hardest things to "get" in programming, so when you have your "aha" moment, it's that much more amazing. Conceptually, it's not that hard to see, but how do you actually program one such?  First, realize that " recursion is a method of solving a problem where the solution depends on solutions to smaller instances of the same problem." Let us try something simple. Let's say... I want you to sum up the elements of an arbitrary array, let's call it arr. It can have any number of elements, and each element is an integer. For the purpose of this exercise, let's just say it's [1,2,3,4], but it can be any integer, and the array can be any valid size. And I want to you use recursion, not loop (no for or while or such statements).  Now, remember the definition: "solving a problem where the solution depends on the solutions to smaller instances of the same problem".  Let's call this function rsum (...
Read more

How to Solve a Problem, with Examples

One of the fundamental tasks of a programmer is how to solve a programming problem, based on the specifications. Here is my attempt to solve such a problem, finally arriving at a validated answer.  If you've been on hackerrank.com, you may have seen this problem before. It's Fraudulent Activity Notifications .  TL;DR: given an array of arbitrary length (let's say it can go to 1x10^6). Each number in the array is expenditures for each day... It can range from 0 to 200 (and is always an integer). You are also given a number "d", that's the number of days you need to LOOK BACK to calculate the window. You need the median value of that window. If the next value is larger than or equal to twice the median, client is notified. Now, given arbitrary d, how many notifications had been generated, for a given array?  Example: you're given 6 4     10 20 30 40 50 60 6 is the size of the array: 6 entries. Window size is 4. First run, "10 20 30 40" Med...
Read more

Let's Make Dice Wars, Part 3

Image
We have previously created the skeletons of the game in part 1, and completed the game in part 2. We now add some "chrome" to the game, to make it look better, prettier, and so on.  And there are a LOT of things we can do, but we may need to rewrite a part of the program to accommodate the changes. This is normal and a part of the learning process.  Let's try making some simple changes. I am not going to show you ALL the changes as you can easily figure out the exact syntax with the steps I described. You can see the source code at the end. This is what it will look like: Change the Button Colors When you think about it, War button should be red, and maybe the reset button should be blue... and maybe rename it "Peace" as a joke?  Well, that's easy enough, with Bootstrap. btn-danger is red, and btn-primary is blue, so we just swap that around.  Keep a "log" of previous battles To clarify, we are adding ANOTHER field called "battle log" whe...
Read more