Skip to content

Software engineer resume: a full example and how to write yours

A recruiter gives a software engineer resume a quick first read, and a hiring manager reads it again for three things: what you built, with which stack, and what changed because of it. Below is a full software engineer resume example, then how to write yours, from a new grad looking for a first role to a senior engineer who leads the technical direction.

Published
Updated
Reading time
14 min
Share

In short

  • Lead with a short summary: your level, your main languages and the kind of systems you build.
  • Under each job, write what you built, the tech you used and a result with a number: latency, users, cost, deploy frequency.
  • Group your technical skills by type and list only what you could discuss in an interview.
  • Add projects and a GitHub link when they show real work. One page, no photo, in a layout an ATS can read.
On this page
  1. Software engineer resume example
  2. What hiring managers look for in a software engineer resume
  3. How to write a software engineer resume: sections and order
  4. Software engineer resume summary examples
  5. Work experience on a software engineer resume: impact, not tasks
  6. Software engineer resume skills section
  7. Projects and GitHub on a software engineer resume
  8. Entry-level and new grad software engineer resume
  9. Senior software engineer resume: scope and leadership
  10. How to make your software engineer resume stand out
  11. Software engineer resume template and format
  12. After your resume: cover letter and interviews
  13. Questions

Software engineer resume example

Example resume

Example

Nadia Kowalczyk

Software Engineer | Backend, Python and AWS | github.com/nadiakowalczyk-example

nadia.kowalczyk@example.com · (614) 555-0165 · Columbus, OH

Summary

Software engineer with 5 years of experience building backend APIs and data pipelines in Python and Go on AWS. Cut p95 latency of a tracking API by 77% and moved a team from weekly to daily deploys. Comfortable owning a system end to end, from design docs to on-call, and mentoring junior engineers.

Experience

Software Engineer II, Platform

Jun 2023 - Present

Brightlane Logistics · Columbus, OH · Full-time, hybrid

  • Own 4 Python and Go APIs behind the shipment tracking platform, about 2,500 requests per second at peak, on AWS (ECS, RDS PostgreSQL, SQS).
  • Cut p95 latency of the tracking endpoint from 820 ms to 190 ms with a Redis cache and 3 rewritten SQL queries.
  • Replaced a nightly batch job with event-driven updates on Kafka: customers now see a status change in under 10 seconds.
  • Built the CI/CD pipeline in GitHub Actions; deploys went from twice a week to 8 to 10 times a day, with automated rollbacks.
  • Mentor 2 junior engineers and review about 15 pull requests a week.

Software Engineer

Jul 2021 - May 2023

Kettle & Pine Software · Columbus, OH · Full-time

  • Shipped 12 features in a React and TypeScript scheduling app used by 300+ clinics, in 2-week sprints with product and design.
  • Raised test coverage of the billing module from 41% to 85% with pytest and Jest; billing bugs reported by customers fell by half in 2 quarters.
  • Built a Django REST API with OpenAPI docs, used by the iOS and Android apps.

Open-source maintainer (side project)

Mar 2022 - Present

ridgequeue, a Python job queue library · Remote · Personal project

  • Wrote and maintain a Redis-backed job queue for Python: 1,100 GitHub stars, 40 contributors, tests and releases in CI.

Education

B.S. in Computer Science

Aug 2017 - May 2021

Scioto Valley University · Columbus, OH

AWS Certified Developer, Associate

Feb 2024

Amazon Web Services · Online

Skills

  • Python, Go, TypeScript, SQL
  • Django, FastAPI, React
  • AWS (ECS, Lambda, RDS, SQS)
  • PostgreSQL, Redis, Kafka
  • Docker, Kubernetes, Terraform
  • GitHub Actions, CI/CD
  • System design and code review
  • Mentoring and design docs

Languages

  • English native speaker
  • Tamil B2

Interests

Volunteer mentor at a local coding bootcamp · Trail running

Nadia has 5 years of experience: a first job on a product app, then a backend role on a logistics platform. Her resume fits on one page, and in a few seconds recruiters can see her level, her stack and the kind of problems she solves. Everything in this example is fictional, including the GitHub link and the numbers.

What this example does well, and you can copy:

  • the first line gives the role, the main stack and the GitHub link, so nobody misses it;
  • each bullet names what she built, the tech she used and the result, with a number;
  • the numbers are the ones engineering managers care about: latency, scale, deploy frequency, bugs, test coverage;
  • the skills section is grouped by type, so it reads like a tech stack, not a word cloud;
  • the side project is written like a job, with one line and real proof (stars, contributors, CI).

You can create yours from the same layout or pick another resume template among our resume templates, and switch at any time without retyping. In Kandiq, put your GitHub or portfolio in the Website field of the contact details: it prints in the header, next to LinkedIn.

What hiring managers look for in a software engineer resume

The Bureau of Labor Statistics (BLS) files software engineers with software developers. Developers analyze what users need, design each piece of an application and how the pieces work together, keep programs working through maintenance and testing, and document the system for future upgrades. Software engineers, the BLS adds, take a broad view of a project's system and software requirements, plan its scope and order of work, and may direct other developers and testers.

Behind those tasks, recruiters and hiring managers reading your resume look for answers to five questions:

  • What did you build? A product, an API, a data pipeline, a mobile app, an internal tool. Name it in plain words.
  • With which stack? Languages, frameworks, cloud and databases, written the way the job description writes them.
  • What changed because of it? Faster, cheaper, more reliable, more users, fewer bugs. One number per bullet when you have it.
  • How big was it? Requests per second, users, data volume, size of the codebase or the group you worked with.
  • How do you work with others? Code reviews, design docs, mentoring, on-call, working with product and design.

The demand is there. The BLS counted about 1.7 million software developers in 2025 and projects 10 percent growth from 2025 to 2035, much faster than the average, with about 106,100 openings a year for developers, QA analysts and testers. The median annual wage for software developers was $135,980 in May 2025. The largest employers are computer systems design firms (29%), finance and insurance (11%), software publishers (10%) and manufacturing (8%): a bank and a startup read the same resume, but they don't look for the same words.

How to write a software engineer resume: sections and order

Here is what to include in each section of your resume, in the right order for most engineers:

  1. Header: name, city and state, phone, email, LinkedIn and GitHub or portfolio. No photo, no full address.
  2. Professional summary: two or three lines with your level, your main languages and the kind of systems you work on.
  3. Work experience: newest role first, with job title, company, city and dates, then 3 to 5 bullets with results.
  4. Technical skills: grouped by type (languages, frameworks, cloud and DevOps, databases, tools).
  5. Projects: 1 to 3 projects with a link, when they add something your jobs don't show.
  6. Education: degree, school, graduation year. Add coursework, GPA or honors only if you are a new grad.
  7. Optional: certifications, open-source work, hackathons, publications or talks.

New grads put education and projects before work experience; everyone else puts experience first. Keep it to one page if you have less than about 10 years of experience. A senior engineer with a long career can use two pages, as long as page two is still relevant.

Many employers receive applications through an applicant tracking system (ATS). Standard section headings, a simple layout and the key words of the job description help the software read your resume correctly before a recruiter does. Our ATS checker shows what the software reads.

Software engineer resume summary examples

The summary is the first thing recruiters read. Make it specific: your years of experience, your stack, the kind of product, and one result. Skip “passionate developer” and “team player”: every resume has them. More examples by career stage are in our resume summary guide.

New grad software engineer

Computer science graduate with 2 software engineering internships, in Java at a payments company and in React at a health tech startup. Built a full-stack class scheduling app used by 1,200 students. Looking for a first backend or full-stack role.

Software engineer, 3 to 6 years of experience

Full-stack software engineer with 4 years of experience in TypeScript, React and Node.js, building customer-facing web apps for a SaaS company. Led the rewrite of the checkout flow that raised conversion by 9%. Comfortable with AWS, PostgreSQL and on-call.

Senior software engineer

Senior software engineer with 10 years of experience in distributed systems, Java and Go. Led the design of a payments platform that processes $2B a year at 99.99% availability. Mentor to 6 engineers and owner of the technical roadmap for a group of 3 squads.

Career changer

Former high school math teacher turned software engineer, with a 6-month apprenticeship in Python and Django and 3 deployed projects. Built an attendance app now used by 2 schools. Strong at explaining technical work to nontechnical users.

Work experience on a software engineer resume: impact, not tasks

“Worked on the backend” or “responsible for APIs” tells a hiring manager nothing. A good bullet follows a simple pattern: an action verb, what you built or changed, the tech you used, and the result. If you don't know the exact number, use a careful estimate you can explain in an interview, never a figure you made up.

What to measureExample bullet
PerformanceCut p95 API latency from 600 ms to 140 ms by adding a cache and an index on the orders table.
ReliabilityRaised availability of the login flow from 99.5% to 99.95% with retries, health checks and a staged rollout.
Delivery speedMoved the team from weekly releases to daily deploys with a GitHub Actions pipeline and feature flags.
CostSaved about $18,000 a year in AWS spend by right-sizing instances and moving cold data to S3.
Scale and usersBuilt the notifications API that sends 3 million push messages a day to iOS and Android users.
QualityRaised test coverage from 50% to 80%; production incidents fell from 6 to 2 per quarter.

Start each bullet with a strong verb: built, designed, shipped, migrated, automated, reduced, scaled, led, mentored. Then make sure the bullets cover your whole job, not only the code: design docs, code reviews, incident response, working with product managers and designers. More bullets you can adapt with your own numbers:

  • Migrated a monolith's user module to a separate API in Go, with zero downtime, over 3 months.
  • Designed the data model and REST endpoints for a new billing feature used by 40,000 customers.
  • Wrote the runbook for the on-call rotation and cut the average time to resolve incidents from 90 to 35 minutes.
  • Built an internal CLI that automated environment setup, saving new hires about a day of onboarding.
  • Added end-to-end tests with Playwright to the checkout flow, catching 3 regressions before release in the first month.

Software engineer resume skills section

Technical skills get the most attention on a software engineering resume, and the most abuse. A list of 40 technologies reads like keyword stuffing, and an interviewer can ask about any of them. Include what you have used in real work or projects, group it by type, and put the stack of the job description first.

A technical skills section

Languages: Python, Go, TypeScript, SQL

Frameworks: Django, FastAPI, React, Node.js

Cloud and DevOps: AWS (ECS, Lambda, S3), Docker, Kubernetes, Terraform, GitHub Actions

Databases: PostgreSQL, Redis, DynamoDB, Kafka

Practices: system design, testing (pytest, Jest), code review, observability (Datadog, Grafana)

In Kandiq, the editor has a separate “Software and tools” section for this list, next to your other skills. Soft skills belong in your bullets, not in a list. The BLS names the qualities that matter in this job: analytical skills, communication, creativity, attention to detail, interpersonal skills and problem solving. Show them with an example: a design doc you wrote, a junior engineer you mentored, an incident you led. Our guide to skills for a resume shows how to pick and prove them.

Projects and GitHub on a software engineer resume

Projects are most important when your jobs don't show the work you want to do next: a new grad, a career changer, or an engineer moving from frontend to backend. A project earns its place when it solves a real problem, has users or a live demo, and has code someone can read.

  • One line of context: what the project does and for whom.
  • The stack: the same words as the job description when they apply.
  • One proof: users, stars, a deploy, a test suite, a talk or a hackathon prize.
  • A link: to the repository or the live app. Check that the README explains how to run it.
A project entry

CampusSlots, class scheduling app (React, Node.js, PostgreSQL, deployed on AWS): about 1,200 students used it during fall registration; 200+ tests in CI. github.com/yourname/campusslots

Your GitHub link helps only if the profile helps. Pin your 3 to 6 best repositories, write a short README for each, and remove the half-finished tutorials. A link to an empty profile is worse than no link.

Entry-level and new grad software engineer resume

According to the BLS, software developers typically need a bachelor's degree in computer and information technology or a related field, such as engineering or mathematics, and some employers prefer a master's degree. Students often get their first experience through an internship while in college. A new grad resume is built around that: education, internships and projects first, because that is where your coding experience is.

  • Education at the top: degree, school, graduation date, and relevant coursework (data structures, algorithms, operating systems, databases).
  • Internships written like jobs: what you built, the stack and a result, even a small one.
  • 2 or 3 strong projects rather than 8 class assignments.
  • Hackathons, teaching assistant roles, open source: each shows you can ship and work with others.
  • No experience at all? Our resume with no work experience shows how to fill the page.
A new grad education section

B.S. in Computer Science, Scioto Valley University, Columbus, OH, May 2026. GPA 3.7

Relevant coursework: Data Structures and Algorithms, Operating Systems, Databases, Distributed Systems

Teaching assistant, Intro to Programming (Python), 2 semesters, about 60 students

Senior software engineer resume: scope and leadership

A senior software engineer resume is read for scope. A hiring manager wants to see the systems you designed, the decisions you made, and how you made other engineers better. Fewer bullets about tickets, more about direction:

  • Led the design and rollout of a multi-region setup for the payments API, now at 99.99% availability.
  • Wrote the design doc and migration plan that moved 40 microservices to Kubernetes over 2 quarters.
  • Set the code review and testing standards for a group of 3 squads, about 20 engineers.
  • Mentored 5 engineers, 2 of whom were promoted to senior.
  • Worked with product and finance to cut infrastructure costs by 22% without slowing the roadmap.

The BLS notes that software developers can move into positions that oversee the software development process, such as computer and information systems manager. If you want the staff engineer track rather than management, say so in your summary, and keep the bullets on technical leadership.

How to make your software engineer resume stand out

Recruiters at large tech companies can receive hundreds of applications for one opening, and many candidates list the same languages. What makes a resume stand out is rarely the design. It is how easy it is to find your achievements and the impact of your work. The most common mistakes, and what to do instead:

  • Listing duties instead of results: “wrote code for the payments team” becomes “built the refunds API that handles 20,000 requests a day”.
  • Listing every technology you have ever touched: keep the stack you would be happy to discuss in a coding interview.
  • One resume for every job: before applying, compare your bullet points with the job description and move the most relevant ones to the top.
  • Vague job titles: use your real title, and add the area in a few words (Software Engineer, Payments) so the reader knows what you did.
  • Old or irrelevant work: past jobs outside tech can stay as one line each, or go. Keep the space for software engineering.
  • Typos in technology names: write PostgreSQL, JavaScript, Kubernetes the way their own docs do. It is a small thing, and reviewers notice.

Think about who reads it: a recruiter first, who checks the title, the stack and the years of experience, then an engineer, who reads the bullets to decide what to ask you. Make sure each one gets what they need on the first page, and that every claim is something you have done and can explain.

Software engineer resume template and format

  • One page under about 10 years of experience, two at most after that.
  • A simple template: clear headings, no skill bars, no icons standing in for text. Our ATS friendly resume templates are built this way.
  • PDF by default, unless the posting asks for a Word file.
  • No photo, age or marital status: that is the practice in the United States.
  • Tailor each application: reorder skills and bullets to match the job description, don't send one version everywhere.
  • Check the links: GitHub, portfolio and LinkedIn must open and be up to date.

The example above uses our Azure template, designed for tech, product and marketing profiles: its tinted headings are a background color, so they stay readable text for an ATS. Kandiq exports your resume as a PDF or a Word file; the Word file uses a simple layout Word can edit without breaking, not a copy of the template. Before you apply, check your file with our AI resume checker: a score out of 100, the reason for each lost point, and the words of the job posting your resume is missing.

After your resume: cover letter and interviews

Many tech companies don't ask for a cover letter, but a short one helps when you change fields, apply to a small company or get a referral. Our cover letter generator writes one from your resume and the job posting, and you edit it word by word.

Every bullet on your resume can come up in the interview. Prepare a story for each one with the STAR method, review the most common behavioral interview questions, and practice out loud with our mock interview. Working with data more than with product code? See our data analyst resume example, and all other jobs in our resume examples.

Frequently asked questions.

A header with your GitHub or portfolio, a two-line summary, your work experience with results, a technical skills section grouped by type, 1 to 3 projects if they add something, and your education. Certifications and open-source work are optional.

Sources

  1. Software Developers, Quality Assurance Analysts, and Testers, Occupational Outlook Handbook (checked on November 14, 2026), U.S. Bureau of Labor Statistics

About the author

Diego Benitez

Founder of Kandiq, more than 100 hires led

Diego Benitez has hired more than a hundred people, in marketing, sport and sales, as a manager at Intersport and then as Head of Growth at Goodvest (2022 to 2026). He ran those hiring processes from start to finish: screening applications, interviews, the hiring decision, then managing the team. He also knows the candidate's side: internships, work-study, student jobs, a permanent contract, starting an agency, then freelancing. He built Kandiq to give candidates what he looked for in an application himself, and what screening software can read. His guides start from the questions candidates ask Google, rely on official public sources (government employment and careers services, employment law) and are updated when the rules change. The examples are fictional; the figures are sourced.

Your resume, ready to send.