DraftCareer

Think ChatGPT could build you a better resume?

Ask ChatGPT, then decide

Resume examples / Software Engineer

Software Engineer Resume Examples (2026): New Grad to Senior

Three software engineer resume examples for 2026, senior, junior and new graduate, written to match 10 live postings, with notes on each. Free PDFs.

Two-page software engineer resume example for Daniel Okonkwo, 8 years' experience, in the Opal template

Two pages, rendered in the Opal template. Scroll the image to see all of it.

Sample software engineer resume, section by section

Daniel Okonkwo

Senior Software Engineer

Austin, United States · daniel.okonkwo@example.com · +1 (415) 555-0163 · github.com/example-daniel · linkedin.com/in/example-daniel

Summary

Senior software engineer with 8 years building service-oriented backends in Java and Python. Owns features end to end, from problem framing through deployment and on-call, and has cut latency and infrastructure cost on systems serving millions of requests a day. Mentors two to three engineers at a time.

Experience

Senior Software Engineer, Northwind Payments

04.2022 – Present

  • Designed and developed service-oriented architecture for the payouts platform, replacing a monolith path that handled 4M requests a day; cut p95 latency from 840ms to 210ms.
  • Owned delivery of merchant refunds end to end - problem framing, design review, rollout behind a feature flag, and the on-call runbook that followed it.
  • Built the CI/CD pipeline in GitHub Actions that took the team from weekly releases to 12 deploys a day, with automated rollback on error-rate regression.
  • Reduced AWS spend 31% ($18K/month) by right-sizing Kubernetes workloads and moving batch reconciliation to spot instances.
  • Mentored three engineers through their first year; two were promoted to mid-level within 18 months.
  • Led the incident review process for the payments group, taking repeat incidents from 9 a quarter to 2.

Software Engineer, Cedarline Logistics

06.2019 – 03.2022

  • Built REST and gRPC services in Java (Spring Boot) for shipment tracking used by 40+ carrier integrations.
  • Led the migration of 1.2M records from MySQL to PostgreSQL with zero downtime and no data loss, two days ahead of schedule.
  • Added structured logging, metrics and tracing across six services, cutting median incident diagnosis from 45 minutes to 12.
  • Collaborated with the security team to close 23 findings from an external penetration test, including an authentication bypass in the partner API.

Junior Software Engineer, Bellrock Systems

01.2018 – 05.2019

  • Developed internal tooling in Python and React used daily by a 30-person operations team.
  • Wrote the unit and integration test suite for the billing module, lifting coverage from 38% to 84%.
  • Ran the fortnightly engineering brown-bag and onboarded two interns.

Education

  • B.S. Computer Science, University of Texas at Austin - 08.2014 – 12.2017

Skills

Java · Python · TypeScript · Spring Boot · React · PostgreSQL · REST & gRPC APIs · Microservices · AWS · Kubernetes · Terraform · CI/CD (GitHub Actions) · Observability & monitoring · Application security · Agile / Scrum · Docker · Git · Linux

Certifications

  • AWS Certified Solutions Architect – Associate, Amazon Web Services (05.2023)

Junior software engineer resume example

Two years in, one page. A junior resume can carry real results already, and the postings ask juniors for the same things as seniors, at a smaller scale: tests, ownership, and code that reached production.

One-page junior software engineer resume example for Sofia Alvarez, 2 years' experience, in the Diamond template

One page, rendered in the Diamond template.

Sofia Alvarez

Software Engineer

Denver, United States · sofia.alvarez@example.com · +1 (720) 555-0194

Summary

Software engineer with 2 years building backend services in Python and TypeScript at a B2B SaaS company. Ships features from ticket to production, writes the tests that keep them there, and takes a turn on the team's on-call rotation.

Experience

Software Engineer, Brightpath Health

07.2024 – Present

  • Built the appointment-reminder service in Python (FastAPI) and PostgreSQL that sends 60,000 SMS and email reminders a week; no-shows at the pilot clinics fell 18%.
  • Added caching and two missing indexes to the availability API, cutting p95 response time from 1.2s to 340ms.
  • Wrote integration tests for the booking flow, lifting coverage from 52% to 81% and catching two double-booking bugs before release.
  • Resolved 40+ production issues on the weekly on-call rotation and wrote three runbooks the team still uses.
  • Migrated the scheduling screens from JavaScript to TypeScript (React) one module at a time, with no feature freeze.

Software Engineering Intern, Brightpath Health

06.2023 – 08.2023

  • Built a React tool for support staff to reschedule appointments in bulk, which went to production and replaced a spreadsheet process.

Projects

  • Transit delay alerts (Go, Redis): polls the city transit feed and messages subscribers when their route is running late; 300 users.

Skills

Python, TypeScript, JavaScript, FastAPI, React, PostgreSQL, Redis, REST APIs, AWS (Lambda, S3, RDS), Docker, CI/CD (GitHub Actions), Pytest, Git, Linux

Education

B.S., Computer Science, Colorado State University

08.2020 – 05.2024

Certifications

  • AWS Certified Cloud Practitioner, Amazon Web Services (03.2025)

Links

GitHub: github.com/example-sofia

What changes from the senior software engineer version

Results, even at two years

18% fewer no-shows and a p95 cut from 1.2s to 340ms. A junior engineer rarely owns a whole system, but most have shipped something that moved a number; find it and put it first.

Tests and on-call are named

The postings we sampled ask for ownership from problem framing to deployment. At junior level, the honest version of that is tests you wrote and incidents you handled, so both are here with numbers.

The internship shrinks to one line

It is at the same company, so it shows the conversion to a full-time offer. Two years in, it no longer needs more space than that.

One project, chosen for what the job doesn't show

The day job is Python and TypeScript; the project is Go. A side project earns its line on a junior resume when it adds a skill, not when it repeats one.

New graduate software engineer resume example

No full-time experience yet, so education comes first, internships are written like jobs, and projects fill the space that experience will later take. The resume a final-year student or recent graduate sends to new-grad and entry-level roles.

One-page new grad software engineer resume example for Jamal Carter, a new graduate with 2 internships, in the Onyx template

One page, rendered in the Onyx template.

Jamal Carter

Software Engineer (New Graduate)

Atlanta, United States · jamal.carter@example.com · +1 (404) 555-0172

Summary

Computer science graduate (May 2026, GPA 3.7) with two software engineering internships and a capstone project used by 2,100 students. Strongest in Java and Python, with experience in REST APIs, SQL and AWS, and looking for a backend or full-stack new-grad role.

Education

B.S., Computer Science (GPA 3.7/4.0), Georgia Institute of Technology

08.2022 – 05.2026

Experience

Software Engineering Intern, Meridian Freight

05.2025 – 08.2025

  • Built a shipment-status REST endpoint in Java (Spring Boot) with unit and integration tests; it now serves the customer tracking page.
  • Cut a nightly reconciliation job from 50 minutes to 12 by replacing row-by-row queries with batched SQL.
  • Presented the work to 40 engineers at the intern demo day.

Software Engineering Intern, Peachtree Community Credit Union

05.2024 – 08.2024

  • Added input validation and audit logging to an internal loan-application form (Python, Django), closing three findings from a security review.
  • Automated a weekly operations report that was built by hand, saving the team about four hours a week.

Projects

  • Campus room booking, senior capstone (TypeScript, React, Node.js, PostgreSQL): used by 2,100 students in its first semester; built the booking API and the double-booking check in a team of four.
  • Distributed key-value store, course project (Go): Raft-based replication that passes all 30 of the course's fault-injection tests.

Skills

Java, Python, TypeScript, Go, Spring Boot, React, Node.js, SQL & PostgreSQL, REST APIs, AWS (EC2, S3), Docker, Git, Linux, Unit testing (JUnit, Jest)

Links

GitHub: github.com/example-jamal

What changes from the senior software engineer version

Education first, with the GPA

With no full-time role yet, the degree is the most recent and most relevant thing on the page. Show the GPA when it is 3.5 or above; below that, leave it off and let the projects speak.

Internships written like jobs

Same format as a full-time role: what you built, in which stack, and what changed. "Cut a nightly job from 50 minutes to 12" is a result a hiring manager can picture.

Projects with users or tests, not tutorials

2,100 students used the capstone; the key-value store passes 30 fault-injection tests. A to-do app from a tutorial says nothing a recruiter can weigh, so it would not make this page.

The skills list matches what the work shows

Every language in the skills list appears in an internship or a project above it. That is what lets you be interviewed on all of them, and it is how screening software and a recruiter both find them.

Junior vs senior software engineer resume: what changes

The three examples on this page follow the same rules: results over duties, the posting's wording where it is true, one clean column. What changes with seniority is where the evidence comes from and how much room it gets.

New gradJunior (1–3 years)Senior (6+ years)
LengthOne pageOne pageTwo pages is fine
After the summaryEducation, then internshipsExperienceExperience
ProjectsTwo or three, with users or testsOne, if it adds a skillOnly if it shows something the jobs don't
Bullets per role2–3 per internship4–5 for the current role5–6 for the current role, fewer for older ones
What the numbers measureUsers, test results, time savedLatency, test coverage, incidentsScale, cost, delivery speed, people promoted
GPAShown if 3.5 or aboveUsually droppedDropped

At every level, the postings we sampled asked most often for security, Java, cloud and performance. What changes is how much of each you can show you owned.

Other titles for the same job

This role is advertised under several names, and the resume barely changes between them. What should change is the job title you put at the top: use the wording the posting uses, because screening software and the recruiter reading afterwards both match on it.

  • Software Developer
  • Backend Engineer or Backend Developer - the same resume with the services work first
  • Full-Stack Developer - move the frontend and API work up and name both sides of the stack
  • SDE or Software Development Engineer - the usual title at Amazon and at many Indian employers
  • Application Developer - more common in banks and IT services firms
  • Junior Developer, Associate Software Engineer or Software Engineer I - see the junior version below
  • Entry-Level or New Grad Software Engineer - see the new graduate version below

Why the senior software engineer example works

The summary answers "what do you do" in one line

Eight years, the two languages, and the thing the postings keep asking for - owning something end to end. No adjectives about being passionate or hard-working, which say nothing a recruiter can check.

Every bullet ends somewhere, not in a duty

"Cut p95 latency from 840ms to 210ms" and "reduced AWS spend 31% ($18K/month)" are checkable. Compare "responsible for backend performance", which describes the job description rather than the person.

The wording mirrors the postings, truthfully

Service-oriented architecture, CI/CD, on-call, mentoring and security all appear because they recur in the postings we sampled - and because this person actually did them. Mirroring language you can't back up is how interviews go wrong.

Page two earns its place

Six bullets for the current role, four for the one before, three for the first: space follows recency. A second page is fine at this level as long as nothing on it is filler.

It's single-column and parses cleanly

Rendered in Opal, one of our ATS-friendly templates: one column, standard headings, contact details in the body rather than the page header, no icons standing in for words.

What software engineer postings actually ask for

We pulled 10 live postings (software engineer, United States) on 24 September 2026 and counted what they mention - counted across all 10 descriptions, so a posting that repeats a term counts each time. The example above uses these terms where they are genuinely true of the person, which is the only way to use them.

TermMentions across those postings
Security20
Java13
Cloud13
Performance13
Python10
JavaScript6
SQL5
Agile5
CI/CD4
REST / APIs4
Linux4
React3
AWS3
PostgreSQL3

How those postings describe the work, in their own words:

  • “design and develop scalable, service-oriented software architectures”
  • “own the software solutions that are deployed to customers”
  • “collaborate cross-functionally to deliver scalable and resilient applications”
  • “own delivery of a client-facing capability end to end - from problem framing through deployment”
  • “partner with end-users to turn needs into features”

Start from this example instead of a blank page.

Upload your current resume or answer a few questions, pick the same Opal template, and DraftCareer fills it in with your own experience. Free to start, no watermark on the PDF.

Mistakes to avoid on a software engineer resume

Listing every technology you've touched

A 40-item skills list reads as noise and invites questions you can't answer. Fifteen you can be interviewed on is stronger than forty you can't.

Describing the team's work, not yours

"We migrated the platform" tells a recruiter nothing about you. Say what you owned, and use "led" or "built" only where it's true.

Burying the stack in prose

If the posting screens for Java and Kubernetes, those words need to appear where they can be found: in the summary, in the bullet where you used them, and in the skills list.

GitHub links with nothing behind them

An empty profile is worse than no link. Either pin something you're happy to discuss, or leave it off.

Frequently asked questions

What does a good software engineer resume look like in 2026?

Like the sample above: a two-line summary naming your languages and what you own, bullets that end in a measurable result, a skills list of the technologies you can be interviewed on, and one clean column that a parser reads in order. In the 10 postings we sampled, security, Java, cloud and performance came up most, so those belong near the top if they are true of you.

Where can I download a software engineer resume sample?

Right here: each of the three samples, senior, junior and new graduate, has a free PDF download beside it. They are made-up engineers, so use them for structure and wording, then build your own from your real experience.

Is a software developer resume different from a software engineer resume?

Not in structure. Developer, engineer, SDE and application developer are different names for much the same job, and the same resume works for all of them. Change the job title at the top to the wording the posting uses, because both the screening software and the recruiter match on it.

How long should a software engineer resume be?

One page for the first five or six years, like the junior and new graduate examples here. The senior example runs to two pages because eight years of delivery, mentoring and incident work doesn't compress honestly into one, and shrinking the font to force it would be the wrong fix.

What should a junior software engineer resume include?

A short summary naming your languages, then your current role with four or five results: something you shipped, something you made faster, the tests you wrote, the incidents you handled. Add one project only if it shows a skill the job doesn't. The junior example above does exactly that on one page.

How do I write a software engineer resume with no experience?

Put education first, with your GPA if it is 3.5 or above, then internships written like jobs, then two or three projects that had real users or passed real tests. See the new graduate example above, and the fresher resume examples for more versions.

Should I include personal projects?

Early in your career, yes - they stand in for work experience. With eight years behind you, a project only earns space if it shows something your jobs don't.

Do I need a GitHub link?

It helps when there's something on it you'd happily walk through in an interview. A link to an empty or abandoned profile works against you.

Should I write a different resume for every application?

Not a different resume - a different version. Keep one master file and change the summary, the skills order and three to five bullets per posting.

Is it safe to use a two-column design?

For an online application at a large employer, no: a parser reads across the page and merges the columns. Where a person opens the file first, it's fine.

Related resume examples

Read next

About these examples: Daniel Okonkwo, Sofia Alvarez and Jamal Carter are not real people. We wrote each resume to illustrate the format, then rendered it through the same engine that builds a real DraftCareer PDF. The employers are invented; the skills and phrasing come from 10 live job postings we sampled on 24 September 2026.