Skip to content
Related Articles

Related Articles

Improve Article
Save Article
Like Article

Tips to Get Your Resume Shortlisted For Top Tech Companies

  • Difficulty Level : Expert
  • Last Updated : 02 Dec, 2021

A lot of students and a lot of professionals have a dream to get into big tech companies like Google, Microsoft, Facebook, Amazon, or Netflix. You worked hard, you got enough experience, made a lot of projects still no call for the interviews. Why is that?? What’s wrong with your resume? Have you mentioned enough experience?? How did you try to apply?. 


There might be a lot of reasons why your resume not getting shortlisted for these big tech companies. We are going to share some tips and some mistakes that most people do in their resumes. First, you need to understand that these companies get lakhs or millions of resumes every day which is firstly scanned by some algorithms. This algorithm shortlists some resumes based on a few keywords that are relevant for the job. For example “Java Developer“, the algorithm considers the keyword Java and it will scan all the resumes that will have this word included and the same goes for the other profile. The rest of the resume gets filtered out and after that, these resumes get into the hands of the hiring manager for the further process. 
Now we are going to discuss three sections that will help you to get your resume shortlisted in these tech companies. 

To write a good resume, you will need to focus on the main facts of your professional bio. Therefore, your professional business card should look like this:

  • Position
  • Contact details
  • Work experience
  • Education
  • Professional skills
  • Recommendations
  • Additional information

Get the Right Experience

If you have completed your education from a reputed college or you have worked for a reputed company then it will help you a lot otherwise you can boost your resume with some projects and participation in hackathons. 

  • You can build some mobile app, web app or you can also include your ML project. Honestly, it doesn’t matter that much what you’re building as long as you’re building something. You should have good command with at least one programming language such as Java, Python, Ruby on Rails, C++, etc.
  • Instead of building 5-6 tiny projects (you can build initially but that won’t showcase enough experience) be to build some big projects which you are most proud of especially when you have no programming background. Doing a project is important to get enough experience and to showcase that you have built something.
  • Participate in hackathons or open-source projects. If you are a college student participate in ACM-ICPC or Google Summer of Code. Participating in these competitions helps a lot in applying for dream companies.
  • Build a website/portfolio and show your experience. A lot of people have a question that where they can find some project ideas or what kind of project they can build. Check open source and it has a plethora of projects which you can build. You can also contribute to some existing open-source projects. Contribution to open-source showcase that you can work in a team.

Build a Great Resume

  • Create your resume of only one page (at most two pages if you have more than 10 years of experience). A recruiter only takes 10-15 seconds to scan a resume so if your resume is too long, it just takes your best stuff – the stuff that would have made the “one-page cut” – and dilutes it with more mediocre content. It doesn’t matter how many years of experience you have, be precise and clear in just a one-page resume.
  • As a fresher, if you are confused about whether to write your experience first or your education at the top. So you have to make this selection in such a manner – if you have more experience of internship/freelancing and if you have done an internship in any well-reported or any well-known company then you first write your experience section because you should mention the best things about yourself highlighted at the top. But if your education section is more powerful like your marks are very good or your college is very prestigious, then definitely you should keep your education section above.
  • Use a real resume format. Don’t create your own — it tends to waste space and look sloppy. Use the right template which can have multiple columns (It will help you to showcase all your skillset). You can take help from the link Rachit Jain.
  • If you’re using Microsoft Word to create your resume (which you probably should), use Microsoft Word’s “tables.” Just make sure to hide the borders afterward.
  • Mention 3-5 projects, hackathons, or open-source profiles. Projects can be academic required projects or independent projects. They do not need to be completed or launched either. As long as you’ve done a “meaty” amount of work on them, that’s good enough.
  • If you mention some bullets in your resume then keep it short. Bullets that are 3 or more lines look like paragraphs and won’t be read. Use the word built, created, implemented, designed, architected, optimized in the first line of each bullet.
  • Mention your accomplishment in your resume instead of responsibilities. It shows your enthusiasm for your work and the impact you have made.
  • Quantify your accomplishments for example if you have optimized something then mention how much.
  • You don’t need to mention the objective in your resume. The company already knows what position you are applying for so it will just waste space. At worst, it’ll limit you since it’ll exclude other positions that might have been interesting to you.
  • Be careful when you mention the programming languages because it’s a “fair game” for the interviewer to test. So it’s better to mention something like “C++ (Proficient), C# (Prior Experience), …”
  • If a project is not finished yet or not official still if it’s great then mention it (you shouldn’t just list everything you’ve ever done).

Necessary Checks Before Submission 

  • Whether there are grammatical and lexical errors in it. Ask a friend to read your resume before submitting it or use the online spell checker.
  • The description of the present place of work should contain the verbs of the present tense: work, design, manage.
  • Descriptions of previous jobs should contain verbs in the past tense.
  • The entire resume should have one style of narration, the same applies to abbreviations – if you used abbreviations somewhere, then use them throughout the text (although it is better to abandon abbreviations and write the names in full).
  • The resume format should be easy to read (large margins, not small print, but not too large print, sufficient line spacing, etc.).
  • Use good quality white paper for the printed version.
  • Always save your resume in pdf format and send resume in pdf format to companies.

Submit the Resume

A lot of people just stick with one avenue. They apply once, and then figure that’s enough. Try all available avenues.  

  • If you’re active on Github, Stack Overflow, LinkedIn, etc, there’s a chance a recruiter will come to you. So it’s good to keep updating your profile and stay active on these platforms.
  • Apply online which means the career page of these companies. It’s tough, but people do get their resumes selected that way.
  • Make connections and take references from your friend or someone who is working in these companies. If someone working in these companies refers you then chances will increase to get shortlisted for the interviews.
  • Try reaching out to Google engineers on Twitter, Quora, or other social media. Remember that your first contact with them is, effectively, a cover letter. Don’t just say “Hi, I’m interested in Google, will you refer me?” Reach out to them and tell them about some of the things you’ve done, and then link them to your resume.

Note: All the tips apply to all the big tech companies, and much of it to many positions as well. 

Important Link: Resume Building – Resources and Tips 

My Personal Notes arrow_drop_up
Recommended Articles
Page :

Start Your Coding Journey Now!