So you sent your resume to your favorite tech companies and never heard back from any of them?
Guess what, you’re not alone. Top technology companies like Google receive over 2 million job applications a year and only hire about 5000 people. So the average applicant’s odds are only 1 out of 400, says Laszlo Bock, Head of People Operations at Google. Presumably this includes all roles at Google; it is quite possible the odds are even worse for their engineering positions.
Admittedly, this is at one of the premier technology firms in the world, but the situation is not much different at other companies. There is a good chance that your resume is going to be shelved without you ever learning the reason. To not end up in the rejected pile, you must at least avoid the following mistakes in your software engineer resume:
1. Not sending your resume via an employee referral
If you are applying directly via a company’s website or through a job board, please stop!
As per the Impact Group Study in 2010, job applications using networking or referrals are far more successful than applying online. 26.7% of external hires made by organizations came from referrals, making it the number one external source of hiring. 46% of men and 39% of women find their jobs through networking. The higher your salary, the more effective networking becomes.
2. Not tailoring your resume for each job application
One of the biggest mistakes you can make is to use the same resume for each job application. While most of the content will remain the same, it is easy to customize the headline and summary sections at the top where you can convey your fit for that particular position. You can highlight the relevant skills in your professional summary to enable an employer to quickly get a grasp of the most impressive and pertinent items in your profile.

3. Not mentioning your online presence
Given how easy and cheap it is to maintain a personal website, social media profile, or blog, it is inexcusable for a software engineer not to have one these days. A blog showcases your knowledge, the kind of work you’ve been doing, and how long you’ve been involved in it. It demonstrates your writing skills and how clearly you can communicate your thoughts. And with linking and discussions, you can show your level of connection with current trends and technologies. It also gives you a significant advantage when a prospective employer can look at your site or blog and assess your fit for their work, beyond the brief summary included in your resume (which will always need to be limited in length and scope).
If you don’t have a website or a blog yet, consider including your Stack Overflow, GitHub, or any other public profile link that could demonstrate your skills. At the very least, you should include your LinkedIn profile and make sure it’s more than just a stub.
4. Not highlighting relevant projects
Top tech companies and startups are looking for killer projects in your profile.
Anyone can build mundane school projects but what personal projects did you create? Did you build an expense sharing app to use among your friends? Or a budget app for your Mom? These projects show your passion for programming because you built them just for fun or utility. Good companies look for such passionate candidates.
These projects can make or break your shortlisting chances especially when your current job profile is not very relevant. If you are an enterprise application developer at a bank, for example, and are applying to Google or Facebook or Twitter, then your work is unlikely to impress them straight away. To make the cut and stay in contention, you need to differentiate yourself, and listing independent projects is certainly one way to do that.
To do this right, of course, you need to understand the job requirement first and then determine what kind of projects would be most relevant. Cut out old school projects and add these instead. If you don’t have any, don’t apply yet and first work on some projects that will be worth mentioning!
5. Not using the right keywords
Most big employers and job boards use applicant tracking systems to store and manage the huge number of resumes they receive. Keyword searching becomes a necessary evil here for screening and filtering out the best candidates. And since most jobs have at least one, non-negotiable requirement, including relevant keywords related to that requirement is essential (adding Hadoop, for example, for a Data Scientist position).
Keywords aren’t just restricted to tools and technologies, of course, but could also be functional titles such as ‘product manager’, ‘SEO’, ‘social media manager’, etc.
So think of what keywords are pertinent to the position you are applying for and include those in your resume to ensure that it is shortlisted during first-level ATS filtering.

6. Not removing irrelevant or unimpressive certifications
There are only a few companies or hiring managers impressed by a SCJP certification. In fact, there can be times when it serves as a negative signal. Ideally, your expertise in a technology should be reflected in your projects and not in the number of certifications under your name.
Unless a job opening specifically asks for a certification or it is extremely relevant, you should leave it off of your resume. For example, if you are applying for network engineering roles that involve working on Cisco switches and routers, including a certification like CCNA might be helpful.
At the end of the day, your resume is supposed to highlight your accomplishments and the skills relevant to the position for which you are applying. Every line should conform to these goals. Anything that does not add value to your candidacy should be mercilessly removed.
If you’ve done it right, your well-designed resume will prioritize the right information and get you past the initial screening. After that, during the interview, it’s all up to you!
Good luck!
Dear Software Engineer – This is why your resume was rejected | by Nistha Tripathi via Scholar Strategy.