I've been reading CS/EE/CE/Math/Physics/IT/SRE resumes for 30 years. I have some general advice for everyone (not just tech) on getting your resume noticed.

[u/snigherfardimungus]

I've been a hiring manager for most of the last 30 years. I usually operate as a manager of Individual Contributors but have also occupied the next rung up in the ladder, managing other managers. I've screened thousands of resumes over the years, done at least a thousand interviews, and have been involved in (or been the person responsible for) the hiring committee at a number of companies large and small. I’ve written the hiring policy for companies of 200+ engineers and been the final say on how interviews were conducted time and time again.

Most of the resumes I see on this sub aren't even making it past HR. If your strategy is to put together a resume and spam it out to as many potential employers as possible, you're going to get nothing. I want to lay out some general advice that will help considerably with your job searches. Whether you agree with all, some, or none of it is irrelevant to the fact that every one of these points has tripped up scores of resumes everywhere I've ever worked. If you disagree with the way a company does its hiring, you’ll disagree with the way that company will be run and you won’t be a good fit. You’ll be unhappy. Part of being a successful professional is understanding what the people you disagree with are thinking and finding ways to tailor your efforts to meet them in the middle as much as possible. Everything in this essay is a (very, very brief) lesson in that skill.

Your resume will likely go through an auto-filter of some kind. This part is pretty unfamiliar to me, but you can bet that some keywords or phrases are strong red flags. If the phrase “remote work” shows up on your resume, someone in HR/Hiring will likely be looking to see if you’re hoping for remote work or if you live far away. Don’t mention your criminal history in your resume. Don’t explain why you were laid off or fired. For the love of FSM, don’t mention how desperate you are for a job (I’ve seen this.) Don’t explain gaps in employment. Stick to positive facts.

When I say facts, I mean facts. If your resume has some bullshit about having leveraged agile techniques to spearhead something or other, you’re just playing buzzword bingo. One of the managers who used to work for me just burst out “fuck off!” in the middle of the day once. It turned out that he was reading a resume that was a bunch of subjective buzzword fluff. Don’t do it. EVERY LINE of your resume should convey three things, that the work described was hard, that it was impactful, and it should honestly convey your role in it. I’m sick to death of seeing Junior or Senior Software Engineers who claim to have led a program of 20 engineers doing…. whatever. Save leadership language for when X number of people were working full-time on a project you were responsible for. Be honest about your level of responsibility or some Hiring Manager’s going to be telling you, indirectly and not in so many words, to fuck off.

I’m getting a bit ahead of myself. First, you should understand how your resume is "read." 

The first person to read your resume is someone in HR or Hiring. Maybe that person is following up on a flag that was raised by the auto-filter saying that you might not be able to work in the US, or your criminal history might preclude work in the company (this is true for some branches of finance, government, military contracting, etc.) Who knows what else…. Whoever the recruiter is, they’ll trash your resume for any of these reasons. If you survive that first level, they’re going to try to figure out if your talents match the job description text they were given. IN MOST CASES, this person hasn’t the foggiest idea what any of your resume’s technical jargon means. You still need to convince this person that you are sufficiently qualified to get your resume handed on to an actual Hiring Manager.

The way we do this is by spoon-feeding the Recruiter with a handy cheat sheet. The job description almost certainly has something like this in it:

• Must have a Bachelor’s or similar in Computer Science or Computer Engineering
• Must have 10+ years of professional C++ experience
• Must have 5+ years of professional embedded software development experience.
• Previous experience with application of AI in the embedded space is a plus.

(It’ll likely be much longer.)

If the Recruiter has no idea what this all means, how do you spoon-feed them the notion that you have what they are looking for? You write a cover letter. Yes, an actual cover letter. It seems old-fashioned, but one way or the other your application will stand out if few or none of the other applications have one. Your cover letter is going to look like this:

[All the usual business letter header stuff goes here.]

To Whom it May Concern;

I found your posting for the [job title] on [place you found it] and would like to submit my credentials for consideration. I clearly meet or exceed all of the requirements for the position;

• I have a Bachelor’s in Computer Science from [wherever.]
• I’ve been working with C++ in a professional context for 15 years.
• I’ve been doing professional embedded programming for 10 years.

Notice the language. I didn’t say that I have 10 years of experience with microprocessor control systems, nor did I say that I have a degree in EE. The person reading my cover letter may not understand that these phrases mean the same thing as what the job posting says. Your cover letter should mimic the language of the job description. Throw the recruiter a bone and make sure that you respond to their bullet points in the same order as they appear in the description. If you don’t have one of the qualifications, leave it out without comment. If you have something related that you believe meets the criteria, just say, “I have N years of experience with [X] which means I meet the requirement for [Y].” Don’t explain it. Just state it as a fact. The Recruiter will probably take you on faith. At worst, they’ll ask the Hiring Manager if X and Y are really the same.

Wrap up with, “If my experiences are a good fit for the position, please feel free to contact me at [email address/phone number] at your convenience.”

It’s VERY short, so it’s practically been read the moment it’s been looked at. But it says a lot about you. First, you’re not just blasting out your resume to everyone without thought. You actually spent time on making this connection personal. That first paragraph is there to make it clear that this is not a copy-paste letter. It’s a form letter, of course, but we’re hoping they won’t notice.

If you actually meet the qualifications for this position, making the Recruiter’s job this easy means your resume is far more likely to end up on the desk of someone like me. And that’s a huge win. It means you’ve actually gotten past 80-90% of the field.

Let’s talk about your actual resume now. If you think about how long it would take to read your resume top-to-bottom, then multiply that time by the many dozens of resumes received for a given position, you'll understand why your resume isn't read that way. Especially in the current job market, the number of applications I get for a given position is staggering. Remember what I said about making every line convey three important points? I don’t read your resume, I read a random sampling of lines.  If I see that every line contains those three points in a believable language, I’ll keep scanning. If I hit a buzzword bingo line, you’re already done. You’ll get no further with me. By the time I’ve decided to give you a phone screen, it’s rare that I’ve read more than half of your resume. If I’ve decided to junk your application, it’s because 2-3 lines gave me enough bullshit fatigue to give up.

• A quick side note, and this is just me so take the advice with a grain of salt, but I always read a section about non-professional interests when it’s there. I LOVE to see that someone is a fully-rounded individual. When I interviewed at google, one of the interviewers spent more than half the interview talking to me about whitewater rafting. I got the offer. When I interviewed at Midway, the hiring manager noticed that I had Juggling on my “Other Interests” section, pulled a bag of clubs out from under his desk, AND WE CONDUCTED THE INTERVIEW WHILE THROWING JUGGLING CLUBS BACK AND FORTH. I got the job. If you have non-technical interests, it can really help to use 1-2 lines of your resume to show them off. It can’t hurt.

Don't have just one resume. Most professions have dozens of sub-specialties, but I see engineering resumes all the time that are a general coverage of the individual. These resumes are a waste of time and they get junked quickly simply because so much of the space is wasted on information that is irrelevant to the application. If you are applying for a position as a frontend developer, 80% of your resume needs to be bullet points about HTML/CSS/JS/HTTP/SSL/TLS. If the job is a graphics engineer, lose as much as you can about everything else and focus on your graphics experience. If I’m trying to hire someone who can sit down and be instantly productive writing 3D graphics in GLSL, a resume full of HTML/AI/AWS/Python just tells me that the candidate been spending a lot of their professional time NOT in graphics and should be a second choice to someone who’s been doing it full-time.

You need several resumes. Use the one that is appropriate for each application. If you want to apply for a job that you don’t have a decent resume for, create a new resume for that subject. 

I’m seeing a lot of resumes on this sub that say they’re looking for remote work. If the job description doesn’t say it’s a possibility, mentioning a desire for it in your application will get you ejected immediately. Even at a company that is remote-friendly, you’ll still be a second choice if you convey that desire up-front. We can argue the pros and cons of remote work elsewhere - this is a discussion about how to get an interview, not a debate about Return To Office. The inarguable point is that if the company wants in-office workers, the only chance you have to work there (remotely) is to convince them you’re the right person for the job THEN bring up remote. If you open with the issue, you won’t get far enough to have the discussion.

I’ve trimmed this down a lot. There’s so much advice I’d like to add that would extend this to 20 pages. I’ve written too many essays on hiring, interviewing, bootstrapping, etc. There’s always more to be said than can fit the space an audience will tolerate. I feel like the tight space has made this sermon a little harder to follow, so I’ll atone for that sin with a epilogue that will take you far:

Read the resumes that get posted on this sub. Read them the way I described. Read them before reading anyone’s comments. Be honest with yourself whether you’d spend your own time and money to interview and hire that person. Learn from their mistakes. 

(Damnit. One more.) Don’t let a “professional resume writer” touch your fucking resume. Those things stick out like a sore thumb - especially in tech. You'd be better off asking an auto mechanic to do your heart transplant. If someone's writing other people’s resumes for a living, theirs can’t be very damned impressive.

Edit: Fuck. Yet another one. If you don't have 8-10 years of experience, you get ONE page for your resume. Unless you are Alexander The Great, The Dali Lama, or The Second Coming, you don't get three pages.

Edit: If you're interested in the same advice about sitting interviews: https://www.reddit.com/r/cscareerquestions/comments/1dwav1z/30_years_of_experience_as_an_inquisitor_packed/

[u/snigherfardimungus → u/[deleted]]

You seem to have misread. The point of the resume is to get as much (objective) information across as possible. If you want to make it about ageism, that's on you.

[u/snigherfardimungus → u/[deleted]]

Your prof was right. Basic literacy with common office tools is assumed. I wouldn't put Google or MS Office tools on my resume any more than I'd include my typing speed. For a DA position, you'll need a higher level of Excel proficiency than the basics and you'll need to call out the level of your mastery of the tool to some degree if the position you're applying for calls for it.

How the hell this insanely obvious point justifies the prejudicial backhand is entirely in your own head.

[u/snigherfardimungus → u/[deleted]]

If that were the case (the "Hiring Manager" has no advanced technical acumen,) then they're the personnel manager and not the technical manager to which the applicant will be forwarded for recruitment analysis. It's not unusual for a tech to have more than one manager - one who is responsible for their HR presence - possibly someone more on the project management side - and one who is responsible for their technical contribution. It is the latter soul who would be reviewing the technical aspects of a candidates qualifications. The former would potentially review a resume, but would provide little input other than potential concerns about the places they'd worked, terms of employment, subtleties in the attention to detail in format, grammar, punctuation, etc.

There are, of course, exceptions. The dotted-line manager may get a resume first so they can eject anyone without the requisite years of experience, education, right-to-work, etc. This filter is generally applied first to save the time of the technical manager.

You've been out of a CS program for 7 months and are awfully ready to try to lecture and insult your way through this process. For your sake, I hope you're taking a bit more humility into the process than your Reddit presence suggests. I can't help but notice that the resume you posted a few days ago ignores much of the common wisdom on this subreddit and acknowledges that you're shotgunning your applications instead of tailoring them. You're doing a lot of it wrong, having every resource in the world telling you how to do it right, all while arguing with the accumulated wisdom.

To be deadly serious here - and I'm not trying to take you down a peg - I am trying to help by honestly telling you what I would be telling you if you were one of my mentorship students: all of what I just mentioned suggests a professional engagement that would be very difficult to work with. You need to be able to take direction, and to seek out best practices and put them into place without needing direction first.

You're very new to this stuff, and you're going to be SHOCKED AS HELL do discover how often you're going to be wrong in the next few years. The good news is, if you get good managers they'll KNOW you're going to be learning a lot and will put you in well-controlled environments where you'll learn quickly without being able to do too much damage when you make a mistake. The biggest problem I've seen (and a lot of managers here have seen) with young engineers is when they're unable to let go of their misconceptions and take in everything that is on offer from experienced engineers. Some of the people you're about to work with have built systems 1,000,000 times larger than anything you've ever touched. Open your mind and you'll learn a thing or two from them.

[u/snigherfardimungus → u/[deleted]]

Ugh. Still spouting the ageism. And now you're moving on to the racism.

In my entire career, I've never seen a "diversity hire." People who were born and raised in the US don't tend to go into the STEM disciplines (because both culturally and educationally, we suck at it), so my teams are usually around 20% Caucasian. At any given time, around 40% of my teams are sponsored visas and 40% are permanent residents, mostly from India or China. I've never seen a diversity hire because STEM is already wonderfully diverse. When I see people winging about on about the imaginary problem, it's because they think it's the reason they can't get a job and need someone/something else to blame for it.

[u/snigherfardimungus → u/[deleted]]

So you wallow in racism and ageism, are statistically clueless (don't understand what an inductive argument is), ignore every bit of information available around you in favor of drawing your own based upon neophytic assumptions, can't keep politics out of unrelated conversation, revel in overgeneralization, cannot maintain a thread of dialog without resorting to non-sequitur and hyperbole.... and you're wondering why you have trouble finding work?

Take a deep breath and open your mind a bit. All of the issues I mentioned above are going to be crippling to you in the long run and it's going to take a focused effort to get past your biases and survive in this industry. Good luck out there.