Software Engineer Resume: Examples, Skills, and Writing Guide

A strong software engineer resume answers three questions in under a minute: what did you build, what was it built with, and what changed because you built it. Most resumes answer the second question in detail and skip the third. That is why so many capable engineers send out dozens of applications and hear nothing back.

This guide fixes that. You'll get a section order for every level from intern to staff, a way to present your tech stack without a wall of logos, a metrics table showing what to quantify, bullet examples by seniority, and a full sample resume you can adapt.

It also covers current pay and job outlook data from the U.S. Bureau of Labor Statistics, so you know what the market looks like before you start applying.

What hiring teams look for in a software engineer resume#

Your resume usually has two readers. A recruiter screens first, checking for title, years of experience, required technologies and work authorization. Then an engineer or engineering manager reads it to judge depth: the systems you owned, the decisions you made and the outcomes you drove.

Write for both. The recruiter needs keywords in obvious places. The engineer needs specifics that would survive a follow-up question in an interview.

The three questions every reviewer asks#

Every bullet on your resume should help answer at least one of these:

• Scope: How big was the system, team or problem? A service handling 2,000 requests per second is a different job from an internal admin page.
• Stack: What did you use, and did you choose it or inherit it? Tools named in context ("migrated billing jobs from cron to Airflow") prove more than a skills list.
• Result: What got faster, cheaper, more reliable, or more used? Results are what separate engineers at the same title.

What gets a resume rejected quickly#

Reviewers see the same mistakes again and again:

• Bullets that describe duties ("Responsible for backend development") instead of outcomes
• A skills section with 40 technologies and no evidence of any of them
• Dense two-column templates that scramble in applicant tracking systems
• Generic summaries that could describe any engineer anywhere
• Projects with no link, no stack and no explanation of what they do
• Two pages of content for a candidate with two years of experience

Software engineer job outlook and pay#

Before you tailor your resume, it helps to know the market. The U.S. Bureau of Labor Statistics reports that software developers earned a median annual wage of $135,980 in May 2025. The lowest 10 percent earned less than $82,460, and the highest 10 percent earned more than $214,670. Software quality assurance analysts and testers had a median of $104,300.

BLS projects employment of software developers to grow 10 percent from 2025 to 2035, much faster than the average for all occupations, with about 106,100 openings per year across developers, QA analysts and testers. There were about 1,717,800 software developer jobs in 2025.

Pay varies by industry#

Industry matters as much as title. The same BLS data shows a spread of more than $30,000 in median pay between the top-paying and lower-paying industries for developers.

If you are targeting a software publisher or a large tech company, expect more competition for each opening and a higher bar for quantified impact. Agencies and consultancies often weigh breadth across client stacks more heavily.

What the outlook means for your resume#

Strong long-term demand does not mean every application is easy. Entry-level roles in particular attract large applicant pools, so a resume that reads like everyone else's gets filtered fast. The practical response is specificity: a named system, a named stack and a measured result in every bullet.

At the other end, experienced engineers are often competing on judgment rather than raw skills. That is why senior resumes should show decisions (what you chose, what you rejected and why it worked), not just a longer list of technologies.

What the role involves#

O*NET's profile for software developers lists tasks such as analyzing user needs and requirements to judge design feasibility, conferring with other engineers on system design and interfaces, and modifying existing software to fix errors or improve performance. Use those tasks as a checklist: if your resume never mentions requirements, design, testing or performance work, you are leaving common screening criteria uncovered.

The best format and section order#

Use a reverse-chronological format with a single column. It is what recruiters expect, and it parses cleanly in applicant tracking systems. Functional formats that hide dates make engineering reviewers suspicious.

What changes by level is the section order. Put your strongest evidence first.

Length, layout and file type#

Keep the resume to one page if you have under about ten years of experience. Cornell's career development team, in an entry-level guide republished from Mentra, also recommends one page tailored to each posting with keywords applicant tracking systems can find. Senior engineers can use two pages if the second page carries real weight.

Layout rules that work for almost every engineering application:

• Single column, standard headings (Experience, Projects, Skills, Education)
• A readable font at 10 to 11 points, with consistent date alignment
• Bold job titles or company names, not both
• PDF unless the posting asks for Word
• No photos, skill bars, ratings or icons in place of words

For the general case for brevity, see our guide to the one-page resume.

Header and links: GitHub, portfolio and LinkedIn#

Your header should fit on two lines: name, then city and state, email, phone and two or three links. Engineering reviewers do click links, so choose them carefully.

Which links to include

• GitHub: Include it if your pinned repositories show readable code, a clear README and recent activity. An empty or abandoned profile hurts more than it helps.
• Portfolio or personal site: Best for frontend, mobile and full-stack engineers whose work is visual or interactive.
• LinkedIn: Include it for recruiters, and make sure titles and dates match your resume.
• Specific project links: A live demo or a merged pull request in a well-known open-source project can be stronger than a general profile link.

Skip your full street address, photo and date of birth. City and state (or "Remote, US") is enough.

Writing a summary that isn't generic#

A summary is optional for software engineers. Use it when you need to frame your profile: a specialty switch, a senior profile, a relocation, or a return after a gap. Skip it if you are a new grad whose projects make the case better.

A useful summary names your focus area, your years of experience and one or two results. It does not claim you are "passionate," "detail-oriented" or a "team player," which every resume already claims.

The "after" version gives a recruiter three keywords (backend, Go, PostgreSQL) and gives an engineer a story worth asking about. For more patterns, see our resume summary examples.

Summary examples by situation#

Adjust the summary to the story you need to tell. These three cover the most common situations where a summary earns its space.

Each one is two lines, names a stack and offers a concrete result or recent proof of currency.

How to present your tech stack#

Your skills section is the recruiter's keyword checklist. It should be easy to scan, grouped by category, and honest. A good rule: if you could not answer a detailed interview question on a tool, leave it off.

Group skills by category#

Use four to six labeled lines rather than one long comma-separated list. Typical groups:

• Languages: Go, Python, TypeScript, Java, SQL
• Frameworks and libraries: React, Node.js, Spring Boot, Django
• Data: PostgreSQL, Redis, Kafka, DynamoDB
• Cloud and infrastructure: AWS (ECS, Lambda, S3), Terraform, Docker, Kubernetes
• Practices and tools: Git, CI/CD (GitHub Actions), observability (Datadog), testing (Jest, pytest)

Order each line by relevance to the target job, not alphabetically.

Skills, tools and certifications for software engineers#

The table below maps the main skill areas to example tools and the certifications that are recognized in each. Certifications are rarely required for general software roles, but cloud certifications can help for infrastructure-heavy positions.

O*NET flags tools such as Git, TypeScript, React, Spring Boot, Kafka, PostgreSQL and Jira as in-demand for software developers. If the job post lists them and you have used them, make sure they appear in both your skills section and a bullet.

Which languages are most widely used#

If you are deciding which languages to feature, usage data helps. In Stack Overflow's 2025 Developer Survey, JavaScript, HTML/CSS, SQL and Python were the most commonly used languages among professional developers.

Popularity is not a reason to list a language you barely know. It is a reason to make sure SQL, for example, appears if you use it daily, since many engineers forget to list it.

Listing AI coding tools#

Many teams now use AI coding assistants, and some postings mention them. Listing a tool name alone says little, because almost anyone can install one. If AI-assisted development is relevant to the role, show it as an outcome in a bullet: for example, building an internal code-review bot, setting team guidelines for safe use of generated code, or integrating a model API into a product feature. That reads as engineering judgment rather than tool familiarity.

What to leave out#

• Proficiency bars or star ratings, which mean nothing to a reviewer
• Basic office software and operating systems you use like everyone else
• Technologies you used once in a tutorial
• Outdated tools unless the job asks for them (legacy stacks can be an asset in some roles)

A technical skills generator can help you build a grouped list from a job title, and our guide to technical skills for a resume covers how to prove each one.

Writing impact bullets that engineers respect#

Most software engineer bullets fail in one of two ways. They list duties, or they list technologies with no outcome. A strong bullet combines an action, the technical approach and a result.

A bullet formula that works#

Use this structure as a starting point: action verb + what you built or changed + how (stack or technique) + measurable result.

Each rewrite names the system, the technique and a number a reviewer can ask about. Our guide to resume bullet points covers the general method, and a resume bullet point generator can produce a first draft from a plain description.

What to quantify as a software engineer#

You almost always have more numbers available than you think. The table below lists the metrics that fit software work and where to find them.

When you don't have exact numbers#

Many engineers work under confidentiality rules or never had access to the dashboard. You still have options:

• Use approximations you can defend: "about 40%," "roughly 2M users."
• Use relative change: "halved," "tripled," "from weekly to daily."
• Use scope instead of results: team size, number of services, request volume.
• Use before-and-after states: "replaced manual weekly reconciliation with an automated nightly job."

Never invent a number. If an interviewer asks how you measured it, you need a real answer. For more methods, read our guide on how to quantify achievements on a resume.

Software engineer resume bullets by seniority level#

What counts as impressive changes with level. A new grad who shipped a feature end to end is doing well. A senior engineer who only shipped features is underselling. Match the scope of your bullets to the level you are applying for.

Entry-level and new grad bullets#

For more on starting out, see our entry-level resume guide.

Mid-level bullets#

Senior and staff bullets#

Handling promotions, contracts, gaps and layoffs#

Engineering careers are rarely tidy. Promotions, contract work, layoffs and short stints are common, and you can present each one cleanly.

Promotions at the same company#

List the company once, then stack the titles with their own dates. This shows growth at a glance and avoids repeating the employer. Put most of your bullets under the most recent title, and keep one or two under the earlier one to show the step up in scope. Our guide to multiple positions at the same company shows the layout.

Contract, freelance and agency work#

Group short contracts under one entry, such as "Independent Software Engineer (Contract)," with the overall dates. Then list two or three client engagements as bullets, each naming the type of client, the stack and the result. That turns six short stints into one coherent story instead of six lines that look like job hopping.

Layoffs and short tenures#

A layoff is not something you need to explain on the resume itself. List the role with accurate dates and strong bullets. If a tenure was very short because the company shut down or cut the team, a brief note in parentheses ("team eliminated in restructuring") can stop a reviewer from guessing. Save the fuller explanation for the interview, and see our guide to explaining an employment gap if you have one.

Projects, open source and side work#

Projects matter most early in your career and for career changers, but they can help at any level when they show something your job does not. The Cornell guide calls projects the most important section for entry-level candidates, especially those without work experience.

How to choose projects#

Pick two to four projects that look like real engineering, not tutorial output. Strong signals:

• Real users, even a small number
• A deployed app or a package someone installed
• Non-trivial technical choices you can explain (caching, concurrency, data modeling)
• Tests, CI and a README that tells someone how to run it
• Collaboration, such as a hackathon team or open-source pull requests

Weak signals include to-do apps, cloned UIs from courses and repositories with a single commit.

How to format a project entry#

Give each project a name, a one-line description, the stack and one or two result bullets. Link to the repository or live demo.

Our guide to projects on a resume covers how to place them for different levels.

Education, bootcamps and certifications#

For most engineers, education sits at the bottom of the page. New grads and students put it at the top. Either way, keep it short.

What to include#

• Degree, school, graduation month and year
• GPA only if it is 3.5 or higher and you graduated in the last few years
• Relevant coursework only if it fills a gap (distributed systems, databases, compilers)
• Honors, teaching assistant roles or research, briefly

BLS notes that software developers typically need a bachelor's degree in computer and information technology or a related field such as engineering or mathematics. Plenty of engineers come from bootcamps or self-teaching, and in those cases your projects and experience carry the education section.

Bootcamps and self-taught paths#

List a bootcamp like any other education entry, with dates and the main stack. Then let your projects do the heavy lifting. If you are moving from another field, our career change resume guide shows how to frame transferable experience.

Certifications#

Cloud certifications (AWS, Azure, Google Cloud) and the Certified Kubernetes Application Developer credential can help for platform, DevOps and backend roles. Put them in a short Certifications section with the issuer and year. For general product engineering roles, a certification rarely substitutes for shipped work.

Full sample software engineer resume#

Here is a complete one-page resume for a mid-level backend-leaning engineer. Names and companies are fictional. Adapt the structure, not the details.

Notice what the sample does: every bullet has a system, a technique and a result; the skills match the bullets; and the page has no filler sections.

Tailoring by specialty#

"Software engineer" covers very different jobs. Shift your keywords and emphasis to match the specialty in the posting.

If the posting is closer to web or infrastructure work, see our web developer resume and DevOps engineer resume guides. If it leans toward modeling and experimentation, the data scientist resume guide fits better.

How to tailor in 20 minutes#

1. Copy the job description and highlight every technology, practice and domain term.
2. Mark which ones you have real experience with.
3. Reorder your skills lines so the matching tools come first.
4. Swap one or two bullets per role for ones that show the highlighted skills in context.
5. Adjust your summary's first line to the specialty in the title.
6. Run the result through a resume keyword scanner to catch gaps you missed.

For the full method, read our guide on how to tailor your resume.

ATS formatting and common mistakes#

Most companies that hire engineers at volume use an applicant tracking system. These systems are better at parsing than their reputation suggests, but they still struggle with complex layouts.

ATS-safe formatting#

• Use standard section headings: Experience, Projects, Skills, Education.
• Keep one column. Put dates on the right of the job line, in a consistent format.
• Write technologies as text. Logos and icons are invisible to a parser.
• Spell out a term once if the posting uses the long form (for example, "continuous integration (CI)").
• Save as PDF unless the system asks for .docx.

Resume Maker's four templates (Classic, Modern, Compact and Minimal) are all one-page, ATS-friendly layouts, and the Compact template suits engineers who need room for a projects section. Whatever you use, check the output with an ATS resume checker before you send it.

A final review checklist#

• Every bullet has an action, a technical approach and a result or scope
• The top third of the page shows your strongest, most relevant work
• Skills are grouped, honest and repeated in context in bullets
• GitHub and project links work from the PDF
• Dates, titles and company names match LinkedIn
• One page, unless you have 10+ years of relevant experience
• No confidential numbers, client names or code you are not allowed to share

Your next steps#

Start by rewriting your three most recent bullets with the action, approach and result formula, then rebuild your skills section into grouped lines that match your target postings. Those two changes alone usually make the biggest difference.

Next, choose your strongest project or open-source contribution and make sure its README and link are presentable. Then tailor one version of your resume for each specialty you are targeting.

When interviews start coming in, shift your preparation to the technical rounds. Our technical interview prep guide covers coding, system design and behavioral questions, and the resume action verbs list can help you vary the wording of your bullets before you send the next application.