ClayCV

Software engineer resume examples

By Gaurav Sharma. Updated .

A software engineer resume should name the systems you worked on and give each one a scale, such as requests a day or users served. Be exact about which part was yours. New graduates are judged mostly on projects and fundamentals, and staff engineers on the technical direction they set across teams.

Ibrahim Diallo, Senior software engineer, eight years, distributed systems

Why Dispatch works for this software engineer resume

  1. Scale and role together. Tech lead and 40 million messages a day set both Ibrahim's seniority and the size of the system.
  2. Fewer pages. Pages falling from 45 to nine a month is a reliability figure every on-call engineer understands.
  3. Practices get a row. System design and mentoring beside the tools show the skills that separate senior from mid level.
Read Ibrahim's resume as text

Ibrahim Diallo, Senior Software Engineer

ibrahim.diallo@example.com | (202) 555-0131 | Washington, DC

Summary

Senior software engineer with eight years building distributed systems in Go and Java on Google Cloud. Tech lead for a messaging platform delivering 40 million messages a day, with a record of improving reliability and helping engineers around him grow.

Experience

Senior Software Engineer, Relecloud | Washington, DC, Apr 2021 – Present

  • Tech lead for a messaging platform delivering 40 million messages a day at 99.95% availability
  • Redesigned the delivery pipeline to absorb traffic spikes of 10 times normal volume without dropped messages
  • Reduced monthly pages to the on-call engineer from 45 to nine by fixing the top alert sources
  • Led a five-engineer project adding regional data storage, needed to enter two new markets
  • Wrote design documents for the team's three largest projects and reviewed about 30 others across the group
  • Mentored four engineers, two of whom were promoted

Software Engineer, Northwind Traders | Arlington, VA, Jun 2018 – Mar 2021

  • Built order and inventory services in Java handling 1 million orders a month
  • Reduced deployment time from two hours to 15 minutes with a new CI/CD pipeline
  • Introduced load testing that found two capacity limits before the holiday peak
  • Replaced a shared database with service-owned schemas across six services

Associate Software Engineer, Litware | Reston, VA, Jan 2017 – May 2018

  • Built API features in Java for an enterprise product used by 150 customers
  • Fixed about 50 defects and added regression tests for each
  • Automated a weekly data repair task that took half a day

Education

Virginia Tech | Blacksburg, VA, Aug 2012 – Dec 2016

  • Bachelor of Science, Computer Engineering

Skills

Languages

Go, Java, Python, SQL

Systems

Pub/Sub, Kafka, Kubernetes, PostgreSQL

Practices

System design, Load testing, Incident response, Mentoring

Everyone and every company in these examples is fictional, and the figures are there to show how a good bullet is built, not to set a standard.

How to write a software engineer resume summary

Two or three sentences: your languages, the system and its scale, and the level at which you work.

Software engineer (entry level)
Software engineer with 18 months of full-time experience and two internships. Builds Java services for a logistics product tracking 150,000 shipments a week.
Senior software engineer (mid level)
Senior software engineer with eight years in Go and Java. Tech lead for a messaging platform delivering 40 million messages a day.
Staff software engineer (senior)
Staff software engineer with 15 years across search and infrastructure. Leads technical direction across five teams and 45 engineers.
Instead ofWrite
Hardworking software engineer with strong problem-solving skills and a track record of delivering quality code.Senior software engineer leading a messaging platform that delivers 40 million messages a day at 99.95% availability.

Keep a figure like 99.95% only if you can explain how your team measured it, because an interviewer will ask.

Summary or objective?

Most engineers should use a summary. New graduates can skip both and open with education and projects.

An objective helps when changing direction: "Mechanical engineer moving into software; built two Python tools used daily by a 20-person test team."

Resume headline examples

Keep your real title, and add the area of work if it helps. Don't inflate your level.

  • Software Engineer | Java, Python, backend services (Entry)
  • Senior Software Engineer | Distributed systems, Go (Mid)
  • Software Engineer | Infrastructure, Kubernetes, reliability (Infrastructure)
  • Staff Software Engineer | Search, cross-team technical lead (Senior)

Experience bullets that show results

Start each bullet with the change you made, then give the result in numbers. The numbers should reflect your own contribution.

Instead ofWrite
Fixed bugs in production.Reduced a failing nightly job's error rate from 4% to under 0.2% by finding a race condition in shipment updates.
Worked on a messaging system.Redesigned the delivery pipeline to absorb traffic spikes of 10 times normal volume without dropped messages.
Helped with on-call.Reduced monthly pages to the on-call engineer from 45 to nine by fixing the top alert sources.
Improved CI/CD.Reduced deployment time from two hours to 15 minutes with a new CI/CD pipeline.
Mentored junior engineers.Mentored four engineers, two of whom were promoted.
Wrote design docs.Wrote the design for a new rate limiter, reviewed by three teams, now protecting 20 services from traffic bursts.
Improved tests.Raised test coverage on the billing service from 40% to 85% and cut escaped bugs per release by two thirds.

Missing a number? Write a bracket now, such as "cut the run from [X] to [Y] minutes", and check the figure in your team's dashboards or tickets before you send. A bracket you can't fill means the bullet needs rewriting.

Bullet ideas by area

Bullets for the work most often hired for. Swap in your figures where the brackets are and keep only the work you have done.

Building
  • Built [system] in [language] handling [X] [requests / events] a [period]
  • Designed [component] using [method], resulting in [outcome]
Reliability
  • Reduced [error or page count] from [X] to [Y] by [fix]
  • Led [X] engineers adding [capability] needed for [goal]
Team
  • Wrote design documents for [X] projects and reviewed [Y] others
  • Mentored [X] engineers, [Y] of whom were promoted
Technical direction
  • Set [standard or design] adopted by [X] teams
  • Led the migration of [system] from [old] to [new] with no downtime

Skills and keywords for a software engineer resume

Keep this section short. List languages first, then the systems and tools you've used in real work.

Languages

Python, Java, C++, Go, TypeScript, SQL

Systems

Linux, Kubernetes, Kafka, PostgreSQL, Redis

Cloud

AWS, Google Cloud, Azure, Docker

Tools

Git, CI/CD, Prometheus, Grafana

Practices

System design, Code review, Automated testing, Incident response

Matching the software engineer job description

At large companies, recruiters often skim for scope and level; at small ones, they look for hands-on range. Order your bullets to suit the company you're applying to.

If the ad names a domain, such as infrastructure or machine learning, move that work up, even if it wasn't your main project.

Use the ad's exact names for the languages and systems you really use, so applicant tracking software matches them.

Certifications and how to list them

No licence is needed, and few software engineering ads ask for a certificate. Hiring rests on your work and your interviews. A cloud certificate is worth listing when the job runs on that platform and your work history doesn't show it yet.

CredentialEarnedIn progress
AWS Certified Solutions Architect - AssociateAmazon Web ServicesAWS Certified Solutions Architect - Associate, AWS, [year]Exam scheduled for [month year]
AWS Certified Developer - AssociateAmazon Web ServicesAWS Certified Developer - Associate, AWS, [year]Exam scheduled for [month year]
  • AWS Certified Solutions Architect - Associate: AWS recommends at least a year of hands-on experience designing cloud solutions on its services. Valid for 3 years. AWS, Solutions Architect - Associate
  • AWS Certified Developer - Associate: A 130-minute exam of 65 questions. AWS recommends a year or more of hands-on experience building and maintaining applications on its services. Valid for 3 years. AWS, Developer - Associate

Master's, MBA or certificate: what helps a software engineer

According to the U.S. Bureau of Labor Statistics, software developers typically need a bachelor's degree in computer and information technology or a related field. Most engineers are hired and promoted on that degree plus their work, and a further degree is optional.

A master's in computer science helps most for specialist work such as machine learning, distributed systems or security, and some employers prefer developers who have one. Many engineers take it part-time, often with employer support, and list it as "MS Computer Science, [School], expected [year]" while they study.

An MBA, an Executive MBA or a master's in engineering or technology management fits a move toward management or product. Developers can advance to computer and information systems manager, and some organisations require or prefer a graduate degree for that job, in computer science, information technology or business administration.

A cloud certificate takes weeks instead of years. It helps most when it matches the platform named in the job ad.

List degrees under Education with the school and year. Short courses, such as a systems design course or an employer's tech lead programme, go under Professional development. Put a finished master's in the summary only when the job ad asks for one.

Software Engineer resume with no experience

Lead with education and projects, and write about each project the way you'd write about a job, ending with the result. An internship is the strongest entry here because it shows code that shipped on a real team.

  • Pick two or three projects with some depth rather than many small ones.
  • Add a test suite and a readme.
  • List internships first, with the team and what shipped.
  • List coursework only if it's relevant, such as operating systems or databases.
  • Include hackathons or open-source work with a link.
  • Be ready to explain every line you've listed.

Moving up: engineer, senior, staff

Engineer. Hiring managers check that you can ship working code without close supervision. Open with a service you built and one result you can measure. Keep projects and internships while your work history is short.

Senior engineer. The resume has to show ownership. Name a system you designed or run and give its size. An incident you resolved on it shows you're trusted with production. Mentoring belongs here too, ideally with an outcome such as a promotion.

Staff engineer and above. Your strongest bullets describe decisions that other teams followed, such as a standard, a migration or a shared service. Cost or time saved across the organisation counts for more than any single feature. Early jobs can shrink to a line each.

Software engineer resume format and length

Keep it to one page for under about 10 years of experience. Senior engineers can use two.

Use one column, plain section headings and standard dates, and keep contact details out of the page header, so applicant tracking software can read the file.

Put your GitHub or portfolio link next to your email only if it shows work you'd be glad to discuss. One pinned project with a readme says more than a profile full of course exercises.

Questions

Should a software engineer resume be one page?

Usually, yes, for anyone under about 10 years of experience. Beyond that, two pages can be fine if everything on the second page is relevant to the job. Cut older roles to a line each before you cut recent results, and keep your strongest system and its scale on the first half of page one.

Should I put my GPA?

Include it if you've recently graduated and it's strong, or if the employer asks for it. Remove it after your first job or two, when your work speaks for you. Relevant coursework, honours and a capstone project often say more than the number itself.

How do I describe team work?

Be exact about your part. "Led", "designed" and "contributed to" mean different things, and interviewers will ask. Name the team size and your role, then the piece you owned: "designed the retry logic for a five-person payments team" is stronger and more honest than claiming the whole system.

What if I can't share numbers?

Use rounded or relative figures you're allowed to discuss, such as "cut build time by about half" or "served several million requests a day". Avoid anything confidential, including customer names and unreleased products. If no figure is safe, describe the scale another way: number of services, teams using it or regions.

Should I include open-source work?

Yes, with a link, especially if others use the project or you've had changes merged into a well-known one. Say what you contributed and how it was received: "added streaming support to a parser with 2,000 stars; merged and released in v3". A single strong contribution beats a long list of forks.

Which certificate is most useful for a software engineer?

None is required. The useful one matches the platform in the job ad: AWS Developer Associate for AWS shops, or the equivalent from Google Cloud or Azure. Add the year you passed it so a reader can see it's current. If you already run production work on that platform, your bullets show it, and the certificate adds little.

Is a master's or MBA worth it for a software engineer?

An MBA pays off mainly if you plan to leave hands-on engineering for product or engineering management. Many engineers wait until they've led a team, then take an Executive MBA, which is built for people in senior jobs and runs outside working hours. If you want to stay technical, a master's in computer science or a stronger record of shipped systems will do more for you.

How do I show I'm ready for a higher level?

Show work you already do at the next level. For senior, that's a system you own end to end and the incidents you handled on it. For staff, it's a design or standard another team adopted. Put those bullets first under your current job, and keep your real title.