The ultimate software engineer
resume builder & guide

Contact information section

As you might have guessed, the first software engineering resume section is all about your contact details and personal information.

While it is easier than the other resume template sections, many software engineer candidates actually mess this part up. Turns out, there’s way more to consider than what you might have thought.

First, take a look at a bad example SWE resume contact section:

And here’s a good example:

Now, what makes the good example good and the bad example bad?

Hint: it’s not the formatting.

Here are the important details to consider when preparing your contact information section:

Name - First name and last name is fine, but a middle name or initial could help when there are many others with similar names on Google and LinkedIn.

Job title or branding statement - An optional subtitle below your name listing your current professional title or short personal description is a common and accepted practice. You could put "Entry Level Software Engineer, User Interfaces" if you want to be specific. With that said, you want to avoid convoluted titles like "Full-Stack Dev Ninja," as this title may not work well with ATS.

Email address - Don’t turn IT recruiters off with your old high school handle (e.g., smartymcfartypants420@aol.com). Use a basic, professional email address with just your first and last name. You can also create an alias or a brand new email address if necessary.

Phone number - Give your cell phone number rather than your home phone number, and include your country code. As recruiters may leave a voicemail, make sure you have ample space. Also, re-record your voicemail greeting if it’s unprofessional.

Physical address - In most cases, don’t include your home address or mailing address, as it’s usually unnecessary. Add it only if the company you’re applying to requires local candidates for onsite positions.

Website - A personal portfolio website is a great supplement to your resume for software engineer jobs. Use it to document your past professional, freelance, and personal projects in detail.

LinkedIn profile - Around 72% of recruiters use LinkedIn to make hiring decisions. Before sending your software developer resume, complete your profile and update it with current information. To showcase your software engineer skills, complete LinkedIn skills assessments to earn badges and impress IT recruiters with your expertise.

GitHub URL - If you’re active on GitHub, add a link to your profile to show off your projects, repositories, and other development activities. Many hiring managers give you bonus points if you’ve contributed to open-source projects.

Other social media profiles - In most cases, leave your other social profiles off, as they’re likely irrelevant (and easily found on Google anyway). However, add these profiles to round out your resume if you are a software engineering thought leader on Reddit or Twitter.

Sensitive information - Don’t include your social security number, date of birth, political affiliations, religion, or other super-personal details. It's not safe and could lead to bias, which may result in you being excluded from consideration.

Formatting - Feel free to be a bit creative here and consider customization options, but don’t go overboard. Make sure your name stands out (larger font size, bold, etc.), and align as you please. Keep the header the same on both your software engineer cover letter and resume template for consistency.

Hyperlinks - Make it as easy as possible for recruiters and CTOs by hyperlinking any URLs in your software engineering resume.

Finally, before we move on to the actual resume content, a warning — make sure to clean up your online presence!

Whether you list your social media profile links or not, an interested hiring manager or head of IT will Google your name to see what comes up. You want it all (e.g., Facebook, Twitter, LinkedIn) to be professional, so thoroughly comb them beforehand for lewd photos, political rants, and other potentially offensive material. Hide them, or better yet, remove them completely!

Introduction paragraph

Hiring managers and IT recruiters spend an average of six seconds scanning through every single resume the first time around, which is really no time at all.

If they notice something they like during that quick glance, your software engineer resume will be reviewed more thoroughly. If not, it’s game over at this particular company, unfortunately.

So, write an irresistible introduction paragraph to capture their attention.

This opening statement is a sales pitch that tells them, "Here's why you should continue reading my resume and keep me in the running as a software engineer job candidate." Let’s start off by looking at two examples of this opening paragraph.

First, here’s a bad software engineer resume example:

And here’s a good resume summary example:

The second resume sample provides enough information, like education, years of experience, and quantifiable measurements of success. With these information in hand, the HR hiring manager or tech recruiter is much more likely to pass your developer cv on to the head of IT for further review.

Let’s dive deeper to understand the characteristics of a compelling opening statement on software engineer resumes:

Concise & complete - A perfect resume summary statement is only about 3-5 sentences long, yet it touches on everything.

Important keywords - It’ll allude to, or directly mention, key skills, education, professional experience, certification, and other items meant to keep your candidacy alive.

Numbers as proof - Don’t simply write that you have certain technical skills or knowledge of software applications. Give the recruiter hard numbers to back up your claims. For example: “I increased speed and accuracy” is vague and requires clarification, but “I increased speed and accuracy by 12% in 6 months” shows hiring managers just how capable you are.

Tailored - The introductory paragraph should be tailored to each software engineer job you apply for. Start by mentioning the role and company you are applying to. Look at the job posting to find hints about the type of person they want.

There are two main kinds of resume introductions:

Resume summary - When you have previous experience in software development jobs or as an SWE, this is the one you’ll use. As the name suggests, it summarizes your relevant skills, experience, and education while showcasing key accomplishments. All in a way that is tailored to this particular job, of course.

Resume objective - Also known as a "career objective," use a resume objective when you have little or no experience in software development or engineering (like if you’re fresh out of university or changing careers). Here, give quantifiable achievements from college or other professional areas that are transferable to software engineering. Then, mention your goals for a career in software engineering to wrap it up.

And, a quick pro tip —

Write your career objective or resume summary paragraph last. Though it's positioned at the top of the page, completing the rest of your software engineering resume first allows you to flesh out the important numbers and critical details. Once you’re done, you can circle back and fill in this opening paragraph, and it’ll be a heck of a lot easier!

Work experience section

Next comes the work experience section, where you’ll compile your previous job history.

As in the last section, let’s look at a good example and a bad example of a software engineering resume job experience section before discussing the best way to go about it.

Here’s a not-so-great professional experience example:

Now take a look at this good example work experience section:

Here’s what makes the second software engineer resume example the better choice:

Order - In your work experience section, the first line should be your job title, as it’s the most relevant information. Below each job title, include the company name, your working location (not their HQ city), and the dates you were employed. Start with the most recent software engineering position and work backward (reverse-chronological order).

Active voice - Use active voice rather than passive voice. It’s way more powerful and effective to say “I formed and mentored a team” than to say “the team was formed and mentored by me.”

Quantifiable achievements - Just as a checksum verifies the integrity of an associated file, achievement numbers verify how well you carried out past responsibilities. You can say you oversaw the redesign of a website, but you can prove you did a great job if you add something like “... leading to a 35% sales increase.”

Power verbs - Things like “worked on,” “responsible for,” and “helped” are weak resume words and phrases. Add some oomph to your writing with powerful, software development-related words (e.g., “tested,” “engineered,” “transitioned”).

Formatting - Group work experience achievements into bullet points. Around 3-5 bullet points per entry is ideal. Also, let it breathe - rather than cramming it all in there. Make use of negative space to help each point stand out. A solid text block is hard for recruiters to parse in that initial 6-second scan!

Be consistent - You can choose to spell the full month name or abbreviate the state in which you worked. Just be sure to follow that same styling everywhere else in the work experience section and other resume areas.

Please note that we recommend a great mid-level or senior software engineer resume to have the work experience section immediately follow the introductory statement. However, if you’re writing a resume with little or no experience (perhaps for a software development internship or junior software engineer position), move more relevant sections higher, particularly skills and education. Always put the most impactful items highest.

Education section

Depending on where you’re applying, your academic history may play an important role in software engineering. Even if you are a self-taught developer or learned through a coding bootcamp, many job descriptions for software engineer roles still require some university education. While your degree may be completely unrelated to information technology, it’s still important to display your scholastic credentials in the best way possible.

Before we dive into how to write a resume education section, let’s again take a look at some resume examples.

A bad software developer resume example:

And a good SWE resume sample:

Note that there are many ways to organize the education section of your senior or junior software developer resume.

A general rule of thumb: the less professional experience a job seeker has (say on a junior software engineer resume), the more info ought to be included to compensate.

Here are the must-have elements:

Degree - If you've earned a degree, the first line of each entry should be the degree name and your major. Follow the naming convention the job description uses when deciding to choose between “bachelor’s degree,” “BS,” or “B.S.” If you’re working on a degree, write instead “Majoring in Computer Science,” for example.

School Details - On the following line, simply write the name of the university and the city and state (or city and country).

Dates - Follow the same dating format you used above in the work experience section.

Format - In the bad example, the date is a second column within the education entry, which itself is in the resume’s second column. This very likely would make it difficult to parse if scanned into HR’s ATS (applicant tracking system) software. The fewer columns, the better, but a single column is best!

And some optional items to consider:

GPA - Adding your grade point average is often problematic, as anything much less than a perfect GPA will turn them off.

Relevant coursework - Include college classes you took that are relevant to the job you’re applying for. And not just specifically connected to software engineering. For example, if you’re applying to become the lead software engineer, adding that course you took on business leadership is a great way to increase your chances!

Minor - Listing a minor (or double major) on your resume shows you can balance a heavy workload and are eager to soak up knowledge.

Honors - If you graduated with honors or earned any academic awards, show them off.

Projects - Similarly, highlight any relevant software engineering projects, academic publications, or research papers.

Finally, while most job descriptions may specifically seek someone with a degree in computer science or software engineering, don’t pass up the chance just because your university history doesn’t match. As one of the more modern employment sectors, they may still consider you - especially if you have enviable software engineering skills and experience.

For those of you applying for software engineer jobs with non-traditional learning pathways in your past, we’ve got you covered! Use the resume education section to list traditional education, and we’ll talk more about where to add the others in just a moment.

Skills section

The software engineering resume skills area should be well thought out. Managers are looking for abilities you have that are relevant to the position, and anything that doesn't just get in the way.

Reread the job description. Find the software engineer skills they’re looking for, and, if applicable, include these in your resume skills list.

Here’s a bad resume skills example:

And this is a better example:

Let’s look at the characteristics of a great SWE resume skills section:

Quantity - Include only relevant skills that will help you land the software engineering position. These will usually be listed in the job description. As a software engineer, there's probably no point listing your proficiency with Microsoft Office, but more relevant software applications should certainly be included.

Go “Hard” - Hard skills are those that can be developed through learning, such as technical skills, while soft skills are acquired as life goes by, such as people skills. Go heavier on the hard skills.

Grouping - IT managers often prefer you to include skill levels to identify just how proficient you are at each one. Follow our convention above or choose your own, but omit any skills with which you have only a rudimentary understanding.

Format - Remember that ATS we mentioned earlier? To make sure hiring software will read your resume correctly, opt for a text-based format (see the good software engineer resume example) over bar charts or fancy graphics.

An important thing to remember - your entire resume shows off your software engineering skills and abilities, not just this skills section. And, other places often show these skills off in a better way, particularly when accompanied with numbers.

You can save crucial resume real estate by thoughtfully cherry-picking, especially for soft skills. For example, rather than (or on top of) adding “communication skills” or “leadership skills” here, imply you are a great communicator or leader using the career summary statement, education section, or work experience bullet points.

Certifications & awards

If you’re looking to apply Pareto’s principle (the “80/20 rule”) to writing a resume for software engineering jobs, the certification and awards section will surely give you the most bang for your buck.

If you can include this section, the few words you list here may just be the most impactful items found on your resume. Why? Certifications and awards, including online qualifications, automatically prove a certain level of technical skills and knowledge, especially when delivered from an industry-renowned organization.

However, though just a few words long, there’s a right way and a wrong way to list them.

Here’s a bad software engineer resume sample:

And here’s a good example:

First and foremost, the bad example is hard to notice as it’s crammed there into a corner. The good example makes use of white space all around to ensure the contents stand out to hiring managers.

Also, always remember to stay consistent. The bad example uses the full name of one certification as the first entry but the abbreviation for the second. Our recommendation is to write out the full name and include the abbreviation in parentheses to maximize resume keywords.

Finally, if you have several certifications and awards each, consider splitting them up into their own sections. Otherwise, one section combining both is just fine.

Personal projects section

Software developers are a passionate, dedicated, enterprising bunch, and you likely have some (or many) personal projects, open-source contributions, or freelance work to show off. And that’s great! These software side projects are very useful in getting the hiring manager on your side.

However —

Let’s just figure out how to highlight your software projects in the best possible way.

A personal projects section *on* a resume is a good idea for lower-level software engineering positions with little professional experience. If you’re writing an entry-level software development resume or a resume for a software engineering internship position, add a few of your proudest projects. Having these projects shows you’re not just in it for the paycheck, but rather you are wholly passionate about software development and engineering.

But, for mid-level and senior software engineering resumes, link out to an online portfolio of your projects in the resume contact information section instead. As a software engineer with experience, you’re going to need all the room on the resume you can get, which is why the online projects portfolio is better. However, if you find yourself with room to spare, by all means, include them!

Anyway, if you’ve decided to add projects directly onto your resume, here’s what to do:

Grouping - When listing more than a couple of projects, group them into subheadings like “Technical Projects,” “Business Projects,” and “Other Projects.”

Title - On the first line, identify the type of project. It could be something like “iOS Mobile Application” or “eCommerce Chatbot.” If you have a website with expanded details on the project, hyperlink the title there.

Description - Give a short description of the project, no more than 3 sentences. Perhaps include the problem it solved, why you created it, and the client (if applicable).

Skills - To end each entry, identify the skills you used (e.g., API access, JavaScript Interop) or tech stacks required to complete the project (e.g., LAMP, MEAN).

An entry-level software engineer resume should be about a *single page* in length, and an experienced candidate should have a two-page resume at most. If your side projects resume section is causing your document to become too long, opt for linking to an online portfolio of projects, instead.

Other important parts of a resume

Above are some of the most common and important sections to include on a resume for software engineer positions, but other areas may help your chances as well. The important thing is to tailor each resume for one particular software engineer job description, rather than sending one generic resume everywhere.

Here are a few additional sections to consider for a good software engineer resume:

Languages - I don’t mean Java, Go, or Python here, but human languages. Adding languages you’re fluent in, along with your proficiency level in each, could be a great addition — especially if you’re joining an international team!

Volunteer work - Volunteering speaks to your character, commitment, and values. Any job seeker with a volunteer work experience section will definitely earn some extra points.

Publications - Are you an IT thought leader? Let the recruiter know with a few choice links to articles you've published on software design, containerization, or big data!

Memberships & affiliations - Highlight your dedication to computer science, information technology, and software engineering in particular by listing professional organizations where you have an active membership.

Hobbies and interests - This may seem irrelevant at first, but, like volunteering experience, they help to portray you as a human rather than just as a candidate. If you have some extra space left over on your resume template, consider adding hobbies and interests you’re proud of.

Coding Bootcamps - If you attended or graduated from a coding bootcamp, don’t be shy! Adding this type of non-traditional coding school and education to your resume is more and more common these days. Plus, it looks great to recruiters, especially for software developer resumes with little experience.

Courses - If you took courses related to software development but unrelated to a specific college degree (for example, the University of New South Wales’ “Introduction to Systems Engineering” on Coursera), add these in a section separate from your other education. Do the same for courses you took for other skills you want to show, such as leadership, communication, or business, for instance.

Additional activities - Have other life experiences or activities which may benefit your chances of landing that tech interview but nowhere to put them? Create a section called “Additional Activities” on your developer CV template. Here you can put things like conferences you attended (or better yet, spoke at), side projects you have, and other projects and pursuits.

And finally —

A software engineer cover letter.

A cover letter may not exactly be part of a resume, but you definitely ought to include one *with* your resume.

Just be sure to use it wisely.

Tailor your software engineering cover letter to the job description. Don’t repeat your resume on the cover letter, but use it instead to expand upon or add value to your resume. Explain why you’re applying and why you believe you’re the most eligible candidate for the software engineering position. Highlight key skills, experience, qualifications, and other items which support your claim.

“Every job is essentially a problem looking for a solution. So every job posting has within it a problem that the company is trying to solve by hiring a human to do that,” as Lisa Smith, Engineering Manager at Zapier, told Arc. If you can use your resume and cover letter to convey how hiring you helps them solve their problems, you’ll be well on your way to that software engineer interview.

And just before you send off your application, do a quick resume review to ensure everything is in order, from your resume format to your relevant skills section. Reread the software engineer job description to see if you missed anything. If possible, get a friend, family member, or roommate to proofread your documents or resume builder draft. Now, send your perfect resume to the hiring manager or IT recruiter, and keep your fingers crossed for a smooth job search experience.