General

How to Write a Strong Resume That Will Be Read by Hiring Managers and Recruiters

Jessica Wilkins
7 min read
How to Write a Strong Resume That Will Be Read by Hiring Managers and Recruiters
This article was written over 18 months ago and may contain information that is out of date. Some content may still be relevant, but please refer to official documentation for the latest information.

Applying for software jobs can be stressful and time consuming. One of most stressful components is writing a resume. A lot of people struggle to write strong resumes and end up paying the price by getting passed over for tech interviews.

In this article, I will provide tips on how to write a strong resume and how to avoid common mistakes made by applicants.

What is the applicant tracking system?

The applicant tracking system will collect and sort through thousands of resumes and help determine which ones match the job description posted. The program will look for keywords in the job listing and search for those keywords in the resume. If there are a lot of missing keywords and skills from your resume it will be rejected by the ATS software. But if your experience and skills match the job listing then it a recruiter or hiring manager will take a look.

Why are ATS programs used?

When companies post job listings online, they will often receive hundreds of resumes and it can be overwhelming for hiring managers to go through all of them. The role of the ATS program is to filter out applicants who don't meet the listed criteria for the job.

How to get past the ATS programs

When you are applying or jobs, it is important that you list of few key skills and keywords mentioned in the job listing so you will have a better chance of making it past the ATS program. It is best to tailor your resume for each job instead of sending out generic resumes to hundreds of companies.

You should also use consistent formatting and use standard fonts like Helvetica, Garamond, or Georgia. Lastly, avoid using tables or columns because they don't always work best for ATS programs.

How to format your file for ATS programs

It is important to submit a resume in either a .docx or .pdf file so it can be easily read by ATS programs. Submitting our resume in a format that dosn't work well for ATS programs can lead to automatic rejection by the software.

What to include on your resume

Your resume should include these key sections:

  • Contact information
  • Summary
  • Education
  • Work experience
  • Software projects
  • Skills

Contact information

At the top of your resume, you should include your name, phone, email address and location. If you are in the United States, just list your City and State. If you are based elsewhere, just list your city and country. There is no reason to include your full mailing address on your resume because that could lead to privacy or even discrimination issues.

You can also choose to list your GitHub profile or Linkedin profile under the contact section. If you have a website or portfolio, you can list that here as well.

Summary

Under your contact information, you can have a short 2-3 sentence summary. This is meant to be a section to explain why your experience and skills make you qualified for the job. Remember that recruiters and hiring managers will only spend a few seconds on your resume. Focus on making an impactful short summary that recruiters will want to read.

Education

If you have a degree, even if it is not in computer science, you should definitely list that on your resume. If you don't have a lot of work experience, it is ok to list your education at the top. But if you have some work experience, you will want to list that first.

When it comes to online courses, I would suggest being selective about what to list. If you have AWS or Oracle certifications, then list those. But if you have a whole bunch of Udemy courses, then I would personally avoid listing those. There is nothing with Udemy courses, but it is important to remember that recruiters and hiring managers will place more weight on college degrees and certifications from large tech companies.

Work experience

When it comes to your work experience you want to focus on the contributions you made to the team and the value you brought to the company. Be specific about what you contributed to the projects because potential employers want to see what you can bring to their teams.

Software Projects

In this section, you want to focus on substantial side projects you have built and been involved with. Avoid listing every single small class project you did in an hour or so. Only list projects where you have invested significant amount of time and effort into. Remember that this is a chance to show off your skills.

Skills

When it comes to listing your skills, focus on the core soft skills and technologies you have worked with the most. Remember that any technology you list on your resume is fair game during a technical interview. If you haven't worked with that technology enough to be comfortable discussing it in an interview, then avoid placing it on your resume.

Here are some free resumes templates you can look at to help you write your resume.

Mistakes to avoid in your resume

There are a few important mistakes you need to avoid doing in your resume to help ensure that it is not immediately rejected by potential employers.

Spelling errors

If your resume is filled with spelling errors, it sends the message that you produce sloppy work and don't care about the finished product. When you have finished a draft of your resume, make sure to read it out loud to catch obvious spelling and grammatical errors. Then share it with your friends, family and others in your network to look it over too. A fresh pair of eyes can help you catch errors that you might have missed the first time around. You can also use tools like Grammarly to help check your work.

Aside from common spelling and grammatical errors, it is really important that you properly capitalize technologies. For example, if you are applying for a web developer position, please do not list "javascript" or "Javascript". The correct capitalization is "JavaScript". Triple check to make sure you are properly capitalizing the names of the technologies you are working with.

Unprofessional email address

When you are applying for these software jobs, you need to come across as a professional in every way possible. This includes having a professional email address. If you are still using an email address from high school like "awesompants@hotmail.com" or "ilove2party@aol.com" ,then please change that.

It doesn't matter how good of a software engineer you are. If your email address is unprofessional, recruiters will throw your resume away. Take the time to set up a professional sounding email address so people will take you seriously. A good safe format would be your name followed by the email provider.

For example: johndoe@gmail.com

Head shots on a resume

In the United States, it is not encouraged to include an image on your resume. Some recruiters and hiring managers will view that as unprofessional while others unfortunately will discriminate against you for your photo. Also, a lot of applicant tracking systems don't work well with images.

It is best to leave it off your resume and just focus on your skills and experience. If recruiters or hiring managers really want to see an image, they can visit your Linkedin profile or other social media sites.

Listing to many technologies on your resume

If you are a software engineer with 15+ years of experience, it is expected that you will have worked with a variety of technologies. But if you are just starting out with very little work experience, avoid listing every single technology you have programmed "hello world" in. Listing dozens of technologies in a short time frame could come across as scattered and unfocused to a hiring manager. Make sure to just list the those you have built substantial projects with, or have worked with professionally.

For example, I took a couple of classes early on that involved C and Python. But I don't list them on my resume because I only spent a few weeks on them and never built anything substantial. So I chose to only list technologies that I have worked with and am comfortable talking about in interviews.

Summaries are to long

Writing a short clear, and concise resume summary takes a lot of time and effort. A big mistake would be to write a summary that is too long and not filled with any substance. Keep your summaries to three sentences, and talk about the value you bring to companies. If recruiters or hiring managers see a summary that has multiple paragraphs, they will just skip over it.

Avoid stuffing our resume with keywords just to pass the ATS software

Some people will stuff their resume with keywords in an effort to get pass the ATS programs. The issue with that is when a recruiter or hiring mangers sees that, it will be obvious that the applicant is just stuffing their application with keywords. Avoid doing this practice because it usually leads to automatic rejections by hiring managers.

Conclusion

No one enjoys having to work on their resume but it is important part of the hiring process. Take the time to draft a strong resume and get feedback from friends and family before submitting it to potential employers.

About the author

Jessica Wilkins

Jessica Wilkins

Software Engineer

Jessica Wilkins is a classical musician turned Software Engineer. Prior to joining the tech industry, she spent her time running her own sheet music company (JDW Sheet Music) as well as performing and teaching in Los Angeles, CA. She enjoys working with React and TypeScript. She is also a prolific technical writer for freeCodeCamp.

Keep reading

View all posts →

How to Avoid Common Pitfalls and Ace Your Take Home Assignment

During the interview process, you might be asked to complete a short take home assignment consisting of building out a small project with required tasks. But what is the best way to approach a take home assignment?...

Jessica Wilkins6 mins
Career

How to Optimize Your Profile and Build a Developer Network on LinkedIn

LinkedIn is a platform designed for professionals to connect with recruiters and potential employers. If you invest the time to build a strong developer profile it can lead to potential job opportunities....

Jessica Wilkins8 mins
Career

How to Build and Grow Your Career Through Networking

What does it really mean to network, and does it actually work? How can you build out a network, and how does it help to grow your career? ...

Jessica Wilkins5 mins
Career developmentCareer

My Career Roadmap

Every developer has their own unique roadmap. I love hearing these stories as they’re constant reminders that there is no right way. Anyone can become a successful developer as long as they have the passion for it. I’ll be sharing my roadmap in hopes that someone also realizes that there are multiple ways to be part of the programming world. My journey started when I attended a junior college in an effort to complete the prerequisites for a Biochemistry degree. I actually got far enough to start taking Organic Chemistry courses. However, my heart wasn’t in it. I found it boring and dreaded anything related to those science classes. I did find it cool that I could recognize some of the fancy ingredients in a shampoo. It just wasn’t what I connected with. I knew that something had to change. I was on track to transfer to a four year university in less than two years. I was always interested in computers and thought about programming. I still don’t know why I was drawn to that: maybe social media made it look cool? The dilemma was to either continue or take a risk by starting a whole new career. I didn’t want to spend more time at junior college, so I needed to make a hard decision: either continue with Biochemistry or drop it completely to pursue programming, but still transfer within the estimated year. I probably would have chosen to experiment with both at the same time if I had realized this a couple of years prior. However, I ended up changing majors within a week. It was one of the best decisions I have ever made. My first programming class felt a bit scary. The building was run down and cold. The room was cramped. There were only two females (including myself). The course wasn’t hard or discriminating against genders but it probably felt that way due to being completely new to the field and not knowing anyone. It didn’t discourage me from programming. In fact, I still remember typing up my first Hello World program. It was the feeling of writing code that made me realize that I was on the right track. Luckily, the junior college had opened up the new STEM building a year later. This really made the place more welcoming. It was actually pretty cool. There were outlets everywhere! A dream for programmers that we take for granted. One of the courses that I took was Internet Programming. This was a turning point for me. My professor recommended that I participate in the local hackathon that was coming up soon. He suggested forming a team with the two other females in class. I never once thought he was discriminating. I honestly believe that he saw potential in all of us but we were lacking confidence in a male dominated world. We participated in the hackathon as a female group. It was my first time working with a team and presenting our project to the public. We didn’t win any awards, but it provided some of the confidence that I was lacking. I finally understood that it didn’t matter what gender you are. I found a love of programming and wanted to be one of the best. I ended up getting recruited for a local internship through the hackathon. I was able to learn about realistic expectations when building a project for a client. The lead developer was also very open to teaching a complete newbie. This is where I learned the basics for web development. It was this type of support that helped shape my career. I graduated from junior college with an associates degree in Chemistry and transferred the next semester. The one regret that I do have in my career is the university that I chose. It didn’t have the best resources for the Computer Science students. The classes were boring and most of the professors didn't seem to care. If you weren’t on the game research cohort, you were just another student passing through. During this time, I got a chance to be part of a research team. However, I decided to accept an internship instead. It was another difficult decision as both had great opportunities. I still think that the internship was the best route as it helped me later on. The internship only lasted for the summer. I learned Polymer during this time. The project was my first deployment and it was used by the city. It was also another great confidence booster. I returned to school with the goal to find my first job before graduation. Truthfully, it was very discouraging, even with my internship experiences. Most companies wanted developers with years in programming. They really don’t make it easy for junior developers. I’m almost positive that I placed over 100 applications. When I did get a response, it was a decline. I also attended the career fair that the university organized. That’s where I found the company that gave me a job offer. I started working for them after graduation. This led to web development in the Drupal world for a little over 2 years. It was a small company but provided development growth. I learned the importance of quality assurance and time management. I also acquired the skill to advocate for higher priority tickets. The most important lesson was that a project can only thrive with a unified team and proper documentation. However, the company had a tremendous downsize due to the pandemic. I was once again on the job hunt. Fortunately, the connections I made during the summer internship helped me find a job at This Dot. There was still an interview process, which I passed due to all the career choices that were made. I’m very excited to be here. I’m working with LitElement projects and more structured work environments. It really is a big difference from a very small company. I’m now pursuing the path of being a mentor, a dream that I had since my first internship. I’m working on improving a mentorship program and making sure my mentee has all the support she needs. I barely have a bit over 3 years of work experience. The time went by very quickly and I’m still excited to be programming. I can’t wait to see where my roadmap will be in the next upcoming years. Tweet me your favorite moment in your roadmap!...

Maria Loza4 mins
CareerMentorship