Have all the skills require to be a great Software Engineer? Here are 9 tips to make your résumé look just like how the Tech Companies want them to be. After all, your résumé is the most powerful ship to a perfect job, suitable for your skills.
1. The Opening: If your résumé starts with “Objective: To utilize my knowledge, skills and abilities as a Software Engineer” then you can definitely bid the job a farewell.
2. Long = Boring: Unless you have 10+ years of experience, your résumé’s length cannot exceed one page. When the HR professional has only get 15 seconds to read someone’s resume, paragraphs would simply get overlooked. Use bullets which are short (1-2 lines) and ideally, no more than half of the bullets should be 2 lines.
3. Always provide specifics: You can speak about all the positions you held and companies you worked for, but it may all go in vain. Most HR professionals don’t have time to interview you just to bring those specifics out. Focus on specific accomplishments, not responsibilities. Just that one point, arguably, can give you an edge over most people in the pile of résumé.
4. Grammar Voes: I know we have endlessly told this (Read Your résumé is your sharpest sword, keep it sharp and clean ), but it deserves repetition. Grievous spelling errors = trash can. As simple as that. In today’s world, poor mastery of the English language is not acceptable – even if your job is related to coding and developing software.
5. Ignore the obvious: You have experience with Windows and MS Office? Please tell the person more, because that definitely is uninteresting. Furthermore, No acronyms on the résumé unless the word is very popular in the industry.
6. Best format for experience: Unless the company you’re applying for is huge, where you are sure that only keyword matching systems can get your résumé from the mail box to the HR official’s table please avoid listing every single programming language that you’ve worked with on your resume. Here’s a good example of a format which provides the key words that Applicant Tracking Systems search for, at the same time giving any recruiter a better idea of how you used each technology at each of your jobs.
What it should be like:
Software Engineer, Company X 2007- present:
– Designed and implemented a JSON/REST API to allow access to the Company database
What it shouldn’t be like:
7. More content, less space: Use a good resume template, with columns. This will allow you to fit more content on your resume while making it easier to scan for key information like company names and titles.
3 lines –
2008 – 2011
1 line –
Software Engineer Microsoft Corporation 2008 – 2011
8. Team vs. You: The HR guy knows that most of your work in companies must be team work. But, he is hiring you. So, tell them what you specifically built, created, implemented, designed, programmed. But showing that you are team focussed and good with adapting to team work is also a good thing to do
9. Failure can be great: To conclude, we advise you to stop thinking about what does and doesn’t belong on a resume and start thinking about whether something makes you look more or less awesome. For example, a large number of people decide not to include meaty projects because they were for a class assignment/independent projects/unfinished/unsuccessful. But coding is coding, and your exposure to real work rather than courses at college can put you in a really good position. Links to code (having a GitHub link is a great thing), portfolio work, or publicly visible projects can also act as positive things on your résumé.
This article is powered by TopTalent.in .
If you like GeeksforGeeks and would like to contribute, you can also write an article and mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks