Software Engineer Resume Example (+ Template)

A full mid-level sample you can copy, an entry-level variant, and the bullet formula that turns vague duties into measurable engineering work.

By Daniel Ortiz · Published · Updated · 18 min read

Featured image for "Software Engineer Resume Example (+ Template)"

This guide gives you a complete mid-level software engineer resume you can model line for line, a shorter entry-level version, and a section-by-section method for writing your own: header, summary, experience bullets, skills, education and certifications.

It also shows weak bullets rewritten with scope and numbers, a table of skills worth listing and how to evidence each one, and where to check current pay and outlook data instead of trusting a number you read on a forum.

Sample resume

The sample below uses placeholder employer and school names in brackets — swap in your own. Everything else (dates, titles, tools, numbers) is internally consistent, which is what a hiring manager scans for first.

Mid-level sample: software engineer, six years' experience

JORDAN RIVERA

Denver, CO · (555) 010-4477 · jordan.rivera@email.com · github.com/jrivera-dev · linkedin.com/in/jordanrivera

SOFTWARE ENGINEER — BACKEND / DISTRIBUTED SYSTEMS Backend engineer with 6 years building Go and Python services on AWS for logistics and healthcare products. Took a shipment-tracking service from 820 ms to 210 ms at p95 under 3M requests a day, and led a 7-month migration of 14 endpoints off a Rails monolith with no customer-facing downtime. Comfortable owning a service end to end: design doc, implementation, tests, dashboards and on-call.

EXPERIENCE

Software Engineer II — [B2B logistics SaaS, ~200 employees], Denver, CO — Mar 2022 – Present - Rebuilt the shipment-tracking service in Go, cutting p95 response time from 820 ms to 210 ms across roughly 3M requests a day. - Led migration of 14 REST endpoints from a Rails monolith into 4 containerised services over 7 months, with zero customer-facing downtime during cutover. - Raised backend test coverage from 56% to 83% across 9 repositories by adding contract tests to the GitLab CI pipeline; release rollbacks fell from about 2 a month to 1 a quarter. - Mentored 3 junior engineers, reviewed ~25 pull requests a week, and wrote the code review guide now used by all 18 engineers in the group. - Cut non-production infrastructure spend by scheduling 40 idle ECS tasks to scale to zero outside business hours.

Software Engineer — [Healthcare data company, ~80 employees], Denver, CO — Jul 2019 – Mar 2022 - Built and maintained 20+ Python/Django API endpoints serving patient-record search for 350 clinic users across 6 customer sites. - Automated a nightly ETL of ~1.2M rows from 6 partner feeds using Airflow, reducing manual reconciliation from 6 hours a week to about 20 minutes. - Instrumented 12 services with Datadog dashboards and alerts, cutting mean time to detect production incidents from 45 minutes to 8. - Shipped a React reporting dashboard that replaced 4 manually produced spreadsheets, delivered in 3 two-week sprints.

Associate Software Engineer — [Digital product agency], Boulder, CO — Jun 2018 – Jul 2019 - Delivered features for 5 client web applications in JavaScript and PHP on 2-week sprint cycles. - Wrote 120+ unit and integration tests for a booking module processing ~4,000 reservations a month. - Remediated 60 accessibility defects to meet WCAG 2.1 AA ahead of a client audit.

SKILLS Languages: Go, Python, TypeScript, Java, SQL Frameworks: Spring Boot, Django, Node.js, React Data: PostgreSQL, Redis, Kafka, Airflow Cloud & infrastructure: AWS (ECS, Lambda, S3, RDS), Docker, Kubernetes, Terraform Tooling: Git, GitLab CI, Atlassian Bitbucket, Jira, Datadog, pytest, JUnit Practices: REST and gRPC API design, code review, incident response and on-call, 2-week sprints

EDUCATION B.S. Computer Science — [State university], Colorado — May 2018

CERTIFICATIONS AWS Certified Developer – Associate — 2023 Certified ScrumMaster (CSM), Scrum Alliance — 2022

Notice what the dates do: the degree finishes in May 2018 and the first job starts in June 2018, titles move Associate → Engineer → Engineer II, and every tool in the skills block appears in at least one bullet. If a reviewer can't trace a skill back to a job, bullet or project, cut it.

Entry-level variant: new graduate or career changer

PRIYA NATARAJAN

Austin, TX · (555) 010-8812 · priya.natarajan@email.com · github.com/pnatarajan · linkedin.com/in/priyanatarajan

SOFTWARE ENGINEER — NEW GRADUATE Computer science graduate with a summer internship building Java services and a capstone project deployed to AWS for 300 campus users. Strongest in backend work: Java, Python, PostgreSQL and REST APIs, with unit testing and Git workflow habits from a 5-person team project.

EXPERIENCE

Software Engineering Intern — [Fintech platform, ~500 employees], Austin, TX — Jun 2024 – Aug 2024 - Built 6 Spring Boot endpoints for an internal account-reconciliation tool used daily by 12 operations staff. - Added 85 unit tests with JUnit, taking the module from no automated coverage to 74%. - Fixed 11 bugs from the team backlog and shipped each through code review and the Bitbucket CI pipeline.

Projects - Campus event API (capstone, Jan – May 2025): Led a 5-person team building a Python/FastAPI service and React front end used by 300 students; deployed to AWS with Docker and GitHub Actions. - Transit delay tracker (personal, 2024): Wrote a Go service polling a public transit feed every 60 seconds and storing 2 years of history in PostgreSQL; published to GitHub with a README and 40 tests.

SKILLS Languages: Java, Python, JavaScript, SQL Frameworks and tools: Spring Boot, FastAPI, React, Docker, Git, GitHub Actions, Bitbucket, JUnit, pytest Databases: PostgreSQL, SQLite Coursework: Data Structures, Algorithms, Operating Systems, Databases, Distributed Systems

EDUCATION B.S. Computer Science — [State university], Texas — May 2025

CERTIFICATIONS AWS Certified Cloud Practitioner — 2024

How to write each section

Work top to bottom. Reverse-chronological order, one page while you have under 10 years of experience, two pages only if you have 10+ years or a genuine publication or patent list.

  1. Header. Name, city and state, phone, email, GitHub, LinkedIn. One line, or name on its own line at 20–24 pt with contact details underneath at 10–11 pt. Skip your street address — city and state is enough, and say "Remote (based Denver, CO)" if that's what you're looking for. If your GitHub is empty, leave it off and link a portfolio or nothing at all. Use a professional email address and a file name like `Jordan-Rivera-Software-Engineer.pdf`.
  1. Summary. Three or four lines, no heading beyond your target title. Use this formula:

[Level and specialism] with [X years] building [what] in [languages/stack]. [One concrete achievement with a number]. [Second achievement or the scope you own].

Example — mid-level backend

Backend engineer with 6 years building Go and Python services on AWS for logistics and healthcare products. Took a shipment-tracking service from 820 ms to 210 ms at p95 under 3M requests a day, and led a 7-month migration of 14 endpoints off a monolith with no customer-facing downtime.

Example — front-end, career changer

Front-end engineer with 3 years in React and TypeScript, previously 6 years in product support. Rebuilt a checkout flow used by 40,000 monthly customers, cutting abandoned-cart errors by half, and now own the design-system component library used by 4 product teams.

Leave out adjectives about your personality. The bullets below have to carry that.

  1. Experience. Company descriptor, your title, location, month and year range. Three to five bullets for the last two roles, two or three for anything older than about six years. Bullet formula:

Action verb + what you built or changed + the stack + scope or result in engineering units.

Engineering units are requests per second or per day, latency in ms, users, services, repositories, endpoints, build and deploy minutes, test coverage percentage, incidents, rollbacks, data volume, team size, sprint length, cost. Example bullets:

  • Rewrote the pricing engine in Go, cutting p99 latency from 1.4 s to 320 ms for 180 requests per second at peak.
  • Designed and shipped a Kafka consumer processing 9M events a day, replacing a nightly batch job and cutting data freshness from 24 hours to under 2 minutes.
  • Reduced CI pipeline time from 32 minutes to 9 by parallelising test suites across 6 runners in GitLab CI.
  • Migrated 23 services from EC2 to Kubernetes over 5 months, writing the Terraform modules the other 3 squads now reuse.
  • Cut flaky-test failures from 18 a week to 2 by quarantining and rewriting 40 integration tests in pytest.
  • Led incident response for 2 Sev-1 outages as on-call, restoring service in under 25 minutes and writing both postmortems.
  • Built a TypeScript component library of 34 components adopted by 4 product teams, cutting duplicate UI code across 11 repositories.
  • Paired with 2 new hires through their first 90 days; both shipped to production within 3 weeks of joining.
  • Added OpenTelemetry tracing to 12 services, reducing mean time to resolution from 70 minutes to 22.
  • Negotiated an API contract with 3 partner teams and shipped v2 of a public endpoint used by 600 external developers, with a 6-month deprecation plan for v1.

If a number is genuinely unavailable, give scope instead: team size, number of services, users, release cadence. Never pad with invented metrics — interviewers ask "how did you measure that?"

  1. Skills. Group them into 4–6 labelled lines: languages, frameworks, data, cloud and infrastructure, tooling, practices. Put the stack you actually want to be hired for first. Don't rate yourself out of 10 or draw progress bars; they say nothing and waste space. Mirror the job posting's vocabulary where it's true for you — if the posting says Kubernetes and you wrote Helm charts, say Kubernetes.
  1. Education. Degree, subject, institution, state, month and year. Drop your GPA once you're two or three years in; keep it while you're a new graduate if it helps you. Relevant coursework belongs on an entry-level resume only. BLS notes that students often gain experience through an internship while in college, and that some employers prefer a master's degree (U.S. Bureau of Labor Statistics, 2025) — so an internship line is worth as much space as the degree itself early on. BLS lists the typical entry-level education for this occupation in the Occupational Outlook Handbook Quick Facts table, which is worth reading before you decide how much weight to give this section (U.S. Bureau of Labor Statistics, 2025). Bootcamp and self-taught routes vary a lot by employer; list the programme by name, the hours or months, and what you built in it.
  1. Licences and certifications. Software engineering in the United States generally has no occupational licence, so this section is about voluntary certifications and, for some defence and government work, clearances — which vary by employer and by contract. List the certification name, the issuing body and the year, newest first. Worth naming if you hold them: the AWS developer-level certification, which Amazon Web Services describes in terms of a target candidate with hands-on development experience using AWS services, and Certified ScrumMaster, where Scrum Alliance sets its own requirement for sitting the exam — check both bodies' current pages before you claim eligibility. Equivalent cloud certifications from Microsoft Azure and Google Cloud, plus security certifications, fit the same pattern. Put expired certifications in the past tense or remove them.

Formatting specifics. Body text 10–11 pt, section headings 12–13 pt, margins 0.5–0.75 inches, a single sans-serif or serif family, bullets one or two lines each and never more than three. Export to PDF unless a posting asks for .docx. No photo, no columns that break when text is extracted, no tables wrapped around your job history.

Weak vs strong bullets

The difference is almost always a unit of measurement and a verb that names what you did, not what you were assigned.

Weak

Responsible for backend development on the payments team.

Strong

Shipped 9 payment-service endpoints in Go handling ~250,000 transactions a day, holding p95 latency under 300 ms through two Black Friday peaks.

The weak version tells a reviewer your team name. The strong one tells them the language, the surface area, the traffic and the reliability bar you held.

Weak

Worked on improving test coverage and code quality.

Strong

Raised backend test coverage from 56% to 83% across 9 repositories by adding contract tests to the CI pipeline; release rollbacks fell from about 2 a month to 1 a quarter.

Coverage percentages are cheap to state and easy to verify in conversation. The second clause shows you knew why coverage mattered — fewer rollbacks, not a prettier dashboard.

Weak

Used AWS, Docker and Kubernetes in a microservices environment.

Strong

Containerised 14 services and moved them to ECS with Terraform modules, cutting deploy time from 35 minutes to 6 and letting the team release daily instead of weekly.

Tool names on their own belong in the skills block. In the experience section, every tool should be attached to something you changed.

Weak

Collaborated with cross-functional teams in an agile environment.

Strong

Ran sprint planning and refinement for a 7-person squad (4 engineers, 1 designer, 1 PM, 1 QA) on 2-week cycles, cutting mid-sprint scope changes from about 5 to 1 per sprint.

BLS lists communication, interpersonal skills and problem-solving among the important qualities for these workers (U.S. Bureau of Labor Statistics, 2025), and ONET's essential-skills list for the occupation includes Critical Thinking, Active Learning, Reading Comprehension, Active Listening, Writing, Speaking and Monitoring (ONET OnLine, U.S. Department of Labor). None of those belong on your resume as adjectives — show them through design docs you wrote, reviews you ran, incidents you handled and people you onboarded.

Skills to include

Pick the 8–12 that match the postings you're targeting and that you can defend in a technical interview. Everything in the right-hand column should appear somewhere above the skills block too.

SkillHard or softHow to show it on the resume
Primary language (Go, Python, Java, TypeScript, C#)HardName it in the summary and in at least two bullets, attached to a system and its traffic or user count
SQL and data modellingHardA bullet on schema design, query optimisation, or the row volume and database you worked with
Cloud platform (AWS, Azure, GCP)HardList the specific services you used, not just the vendor; back it with a migration or deployment bullet
Containers and orchestration (Docker, Kubernetes)HardNumber of services containerised, deploy-time change, or the Terraform or Helm work you owned
CI/CD pipelines (GitLab, Bitbucket Pipelines, Jenkins, GitHub Actions)HardPipeline minutes before and after, or release frequency moving from weekly to daily — GitLab and Atlassian Bitbucket both appear among the tools ONET associates with this occupation (ONET OnLine, U.S. Department of Labor)
Automated testing (pytest, JUnit, Jest)HardCoverage percentage change, number of tests written, or a drop in flaky failures or escaped defects
API design (REST, gRPC, GraphQL)HardEndpoints shipped, consumers served, versioning or deprecation you managed
Application frameworks (Spring Boot, Django, React, Node.js)HardPair the framework with what you built in it; Spring Boot is among the development platforms ONET lists for this occupation (ONET OnLine, U.S. Department of Labor)
Observability and incident response (Datadog, Prometheus, Grafana, on-call)HardMean time to detect or resolve, number of services instrumented, postmortems written
Version control and code review (Git)HardReview volume per week, a review guide you wrote, or a branching strategy you introduced
Communication and technical writingSoftDesign docs, RFCs, runbooks and postmortems you authored, with who read them
Mentoring and collaborationSoftNumber of engineers onboarded or mentored and how quickly they shipped; cross-team work with named functions
Problem-solving and analytical judgementSoftA bullet where you diagnosed something — a root cause found, an outage shortened, a bottleneck removed
Active learningSoftA language or platform you picked up on the job and shipped with inside a stated timeframe

BLS names analytical skills, communication skills, creativity, detail orientation, interpersonal skills and problem-solving skills among the important qualities for workers in this group (U.S. Bureau of Labor Statistics, 2025). Those are the qualities a reviewer infers from your bullets — they are not lines to type into the skills block.

Pay and outlook

Pay for software engineers is set by a handful of things you can partly influence and some you cannot. Level comes first: the gap between an associate and a senior doing design work and on-call ownership is usually the largest single step. After that, specialism and stack, the industry you sit in, and company size and funding stage all move the number. Total compensation structure matters as much as base salary — many employers in this field pay a base plus an annual bonus, and public companies and venture-backed startups often add equity in the form of RSUs or options, which vest over several years and are worth very different amounts depending on the company. Contract and staffing-agency roles are usually hourly with no equity. Ask for the full structure, not just the base, when an offer comes.

Geography still matters even in remote hiring, because many employers band pay by location. The Bureau of Labor Statistics notes that the pay data in its Occupational Outlook Handbook comes from the Occupational Employment and Wage Statistics survey, and that wages vary by experience, responsibility, performance, tenure and geographic area (U.S. Bureau of Labor Statistics, 2025). That is the right mental model when you compare two offers in different states.

For current figures, go to the source rather than to aggregated salary sites: the BLS Occupational Outlook Handbook publishes a 2025 median pay figure for this occupational group in its Quick Facts table and a median annual wage for software developers specifically in the Pay tab (U.S. Bureau of Labor Statistics, 2025). The OEWS survey behind it also publishes wages by state and metropolitan area, which is the comparison you want if you are weighing a move.

On outlook, the Handbook publishes a projected employment growth rate for this group covering 2025–35 and an average number of projected job openings per year (U.S. Bureau of Labor Statistics, 2025). Check both before you make career decisions on the basis of headlines. BLS also notes where these workers tend to be employed — computer systems design and related services, manufacturing, and software publishers, usually working on teams (U.S. Bureau of Labor Statistics, 2025) — which tells you where to aim your applications if you're not fixed on one industry.

For progression, the Handbook describes an advancement path for software developers moving into roles with greater responsibility (U.S. Bureau of Labor Statistics, 2025). In practice that usually splits into a technical track (senior, staff, principal) and a management track (team lead, engineering manager), and the resume evidence differs: the technical track wants design and scale bullets, the management track wants team size, hiring and delivery bullets. Decide which one your next resume is arguing for before you write it.

  • Software Engineer Cover Letter Example (+ Template)
  • Software Engineer Interview Questions and Answers
  • How to Prepare for a Technical Coding Interview
  • Junior Software Developer Resume Example
  • Backend Developer Resume Example
  • Front-End Developer Resume Example
  • Full-Stack Developer Resume Example
  • Software Engineering Manager Resume Example
  • DevOps Engineer Resume Example
  • Data Engineer Resume Example
  • QA Engineer Resume Example
  • How to Build a Developer Portfolio That Gets Read
  • Writing Resume Bullets With Metrics: A Practical Guide

Frequently asked questions

What goes on a software engineer resume if you have no professional experience?

Replace the experience section with projects, and treat each project exactly like a job: what you built, the stack, who used it and how much. Two or three projects with real users, tests and a deployed URL or repository beat a dozen tutorial clones. Add internships, co-ops, research assistantships, teaching assistant work, open-source contributions with merged pull requests, and hackathon builds. BLS notes that students may gain software development experience by completing an internship while in college (U.S. Bureau of Labor Statistics, 2025), so if you have one, it sits above projects on the page. Keep education near the top while you're within a year or two of graduating, including relevant coursework. Quantify what you can: 300 users, 40 tests, 2 years of data, a 5-person team, a 10-week internship. If you came through a bootcamp or taught yourself, name the programme and the hours, then let the projects do the arguing. Entry requirements vary by employer, and some ask for a degree while others weigh a portfolio and a technical screen more heavily — read the posting rather than assuming.

What format and file type should a software engineer resume use?

Reverse-chronological, single column, exported as PDF unless a posting specifically asks for .docx. Use 10–11 pt body text, 12–13 pt section headings, your name at 20–24 pt, and margins between 0.5 and 0.75 inches. Avoid two-column layouts, text boxes, headers and footers containing your contact details, images, icons and skill rating bars — they can scramble when an applicant tracking system extracts the text, and they cost space you need for bullets. Name the file with your name and the role, for example Jordan-Rivera-Software-Engineer.pdf. Keep section headings conventional: Summary, Experience, Skills, Education, Certifications. A reviewer spends their first pass looking for title, dates, stack and scope, and unusual layouts slow that down without adding anything.

How long should a software engineer resume be?

One page while you have fewer than about 10 years of experience, which covers most engineers through senior level. Two pages are reasonable at 10+ years, or if you're in research-heavy work with publications or patents worth listing. Beyond two pages, you're asking a reviewer to do editing you should have done. To get to one page, cut the oldest roles down to two bullets or a single line, remove jobs older than about 12 years unless they're directly relevant, delete the skills you don't want to be interviewed on, and drop your GPA and coursework once you're a few years in. Keep three to five bullets on your two most recent roles — that's where the reading attention actually goes.

Should I include GitHub, side projects and open-source work?

Include a GitHub or portfolio link only if the first thing a reviewer sees there is worth seeing: pinned repositories with README files, commits in the last year or so, and code you'd defend in a review. An empty or abandoned profile is worse than no link. Side projects earn space on an entry-level or career-change resume, and on an experienced resume only when they show something your jobs don't — a language you want to move into, or a system at a scale your day job doesn't reach. Merged open-source contributions are worth a line with the project, what you changed and the scale of the project. Write it the same way as a work bullet: what you did, in what stack, with scope attached.

Sources

  1. U.S. Bureau of Labor Statistics — Software Developers, Quality Assurance Analysts, and Testers : Occupational Outlook Handbook (2025)
  2. O*NET OnLine (U.S. Department of Labor) — 15-1252.00 - Software Developers

More in Resume & CV Guidance

Featured image for "Resume for a Teenager's First Job"
Resume & CV

Resume for a Teenager's First Job

You can write a strong resume with no paid work history. A first-job resume is one page built from school, clubs, sports, volunteering, babysitting and any informal work you have done, with each line written as an action, a task and a number — and with your availability and any certification (food handler card, CPR and First Aid, lifeguarding) easy to find near the top.

Nadia Hassan · 13 min read

Featured image for "How to Write a Resume Education Section (+ Examples)"
Resume & CV

How to Write a Resume Education Section (+ Examples)

List each credential in one consistent pattern — degree or certificate, school, city and state, date — then decide how much to add underneath based on how much the job leans on your schooling. New graduates put education near the top and expand it; experienced hires put it at the bottom and cut it to one or two lines.

Priya Shah · 18 min read

Featured image for "20 Technical Skills to Put on a Resume by Field"
Resume & CV

20 Technical Skills to Put on a Resume by Field

A technical skill earns its place on your resume when it appears in the job ad and you can back it up with a bullet showing what you did with it, at what scale. Listing a tool you have only read about is the fastest way to lose a phone screen.

Wei Chen · 12 min read

Featured image for "How to List Multiple Short-Term Jobs on a Resume"
Resume & CV

How to List Multiple Short-Term Jobs on a Resume

List every short-term job, but stop presenting them as separate careers. Group related stints under one header — a staffing agency, a client list, your own contracting banner — label each one with its arrangement (contract, temp, seasonal, project), and keep month-and-year dates throughout so nothing looks hidden.

James O'Connor · 13 min read