{"id":34,"date":"2023-03-06T02:59:00","date_gmt":"2023-03-06T02:59:00","guid":{"rendered":"http:\/\/fem.flywheelsites.com\/?p=34"},"modified":"2023-11-12T00:20:56","modified_gmt":"2023-11-12T00:20:56","slug":"technical-resume","status":"publish","type":"post","link":"https:\/\/frontendmasters.com\/blog\/technical-resume\/","title":{"rendered":"5 Tips For Writing A Great Technical Resume"},"content":{"rendered":"\n

How often have you scrambled to assemble a resume, only never to hear back from the company you applied to? You\u2019re not alone. Often your resume competes against hundreds (or even thousands!) of other resumes. So\u2026how do you get noticed?<\/p>\n\n\n\n

A resume isn\u2019t something most people regularly update (even though we probably should). When you suddenly apply for jobs, throwing one together at the last minute can be overwhelming.<\/p>\n\n\n\n

First and foremost, your resume is a representation of you. Just like you\u2019re on your \u201cbest behavior\u201d for a job interview, your resume should present the best possible version of yourself.<\/p>\n\n\n\n

On average, recruiters spend about seven seconds<\/a> reviewing your resume, so it\u2019s imperative to put the most relevant information at the forefront and have a visually appealing presentation.<\/p>\n\n\n\n

Let\u2019s look at some of the most common resume mistakes and how to fix them, which will ensure you present the best possible version of yourself to recruiters and land a job interview.<\/p>\n\n\n\n

Tip #1. Your Contact Information Should Be Easy To Locate<\/h2>\n\n\n\n

Recruiters must be able to contact you. If your contact information is listed at the bottom of your resume, it will be a hassle for them to find it, and likely, they\u2019ll move on to the next candidate.<\/p>\n\n\n\n

Include your full name, phone number, and email address; your physical address is only necessary if you apply for an international role. Additionally, if you are applying for an international position, include the country code with your phone number.<\/p>\n\n\n\n

You may also include links to your personal website, Twitter, blog, or LinkedIn page if they\u2019re focused on your professional experiences.<\/p>\n\n\n\n

Two layouts that work well include the two-column layout, where the left sidebar includes your contact information and relevant skills. In contrast, the main column includes your work experience and education.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The second layout that works well is the one-column layout, where your contact information is at the top, followed by the content.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Whichever layout you choose, make sure your contact information is up-to-date and easy to find.<\/p>\n\n\n\n

Tip #2. Focus Your Work Experience On Your Direct Impact<\/h2>\n\n\n\n

One of the biggest \u201cmistakes\u201d with resumes is not listing your direct impact on a product or team. Let\u2019s take a look at an example. Can you see the difference between the following two resumes?<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Looking at these two examples, it\u2019s clear that resume two has provided more detailed information. It has included concise bullet points and leveraged data where applicable (i.e., \u201c\u2026which reduced page load time from 2.3 seconds to 0.5 seconds\u201d).<\/p>\n\n\n\n

Resume two also clearly explains the \u201cso what\u201d recruiters are looking for when reviewing your resume. You should clearly define your direct impact on a project or team. These are called \u201cimpact statements.\u201d<\/p>\n\n\n\n

When writing your impact statements, you should use action verbs. Here is a list of helpful action verbs you can use when writing your impact statements:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Using impact statements with action verbs and data will drastically improve your ability to catch a recruiter\u2019s eye.<\/p>\n\n\n\n

Your impact statements should always be written in first-person, but omit the subject \u201cI.\u201d So instead of writing: \u201cI aided two new team members to submit a pull request,\u201d skip the \u201cI.\u201d The statement should read: \u201cAided two new team members to submit a pull request.\u201d<\/p>\n\n\n\n

Here are a few examples of effective impact statements. You\u2019ll notice a few critical components across each of the examples.<\/p>\n\n\n\n