Should a software engineer resume be one page?

Yes, for almost everyone under about ten years of experience. Recruiters skim, and a second page usually holds older, less relevant work. Cut to your strongest 2–4 bullets per role.

Do I need a summary at the top?

Usually not. For engineers, a summary takes space that a bullet with real evidence would use better. The exception is a career change, where one or two lines can explain the switch.

Should I include GPA?

Include it if you're a student or recent grad and it's 3.5 or higher, or if the employer asks for it. Drop it after your first job or two.

How many bullets per job?

Two to four for most roles, up to five for your current or most relevant role. Each bullet should describe a distinct thing you built or changed.

What does a good software engineer resume look like?

One page, single column, with a header of links, a grouped skills section, experience and projects written as action, technology and result, and education. Jake's resume template is the most common example.

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

Lead with education and two or three projects written like jobs, each with a stack and a result. Add internships, hackathons, open-source work or tutoring. See the new grad and self-taught guides.

How to write a software engineer resume

By Mubeen Jawed, founder of ResumeForDev · Updated November 7, 2026

Short answer

A strong software engineer resume is one page, uses standard section headings (Education, Experience, Projects, Technical Skills), and fills each role with 2–4 bullets that name what you built, the stack you built it with, and a measurable result. Keep it in a single-column, text-based layout so applicant tracking systems can parse it, and only list skills you can talk about in an interview.

Key points

One page, single column, real text (not an image or a Canva export).
Bullet formula: action verb, what you built, the tech, the scale, the outcome.
Put a number in most bullets: latency, users, requests, cost, time saved.
Group skills (Languages, Frameworks, Tools) and make sure the bullets back them up.
Tailor the keywords to each job post, but never claim something you didn't do.

What recruiters look for in the first pass

A recruiter screening engineering applications is checking a few things quickly: does your recent title and stack match the role, have you shipped real things, and is there evidence of scale or impact. They read the top third of the page closely and skim the rest. That is why order and density matter more than design.

Hiring managers read more slowly, and they are looking for something else: specifics they can ask you about. A bullet like “worked on backend services” gives them nothing. A bullet that names the service, the database and the latency you cut gives them an interview question.

The section order that works

Recommended section order by experience level
Section	Students and new grads	Experienced engineers
Header	Name, email, phone, LinkedIn, GitHub	Name, email, phone, LinkedIn, GitHub, site
First section	Education	Experience
Second section	Experience (internships, TA, research)	Projects (optional, if they add something)
Third section	Projects	Technical Skills
Last section	Technical Skills	Education
Summary or objective	Skip it	Skip it, unless you're changing careers

Use the conventional heading names. ATS software and recruiters both look for “Experience”, “Education”, “Projects” and “Skills”. Creative names like “Where I've Been” make parsing less reliable and save no space.

How to write each bullet

The bullet is the unit of a developer resume. A good one follows the same shape almost every time: verb → what you built → the tech → the scale → the outcome. You don't need every part in every bullet, but the verb, the thing and one number carry most of the weight.

Before and after

Before:Worked on the reporting dashboard and made it faster.

After:Rebuilt the reporting query layer behind the customer dashboard in Node.js and PostgreSQL, cutting p95 load time from 4.2s to 900ms for 12,000 monthly active users.

Same work. The second version names the system, the stack, the scale and the before/after.

If you don't remember an exact number, estimate honestly and be ready to explain it (“~40% less DB CPU”). Don't invent one. Interviewers ask about the numbers on your resume more than anything else on it. Our bullet point guide has more before/after rewrites.

Projects: when they help and when they don't

Include them if you're a student, switching stacks, or your best work is outside your job.
Include them if they have users, stars, a live URL, or a technical problem worth asking about.
Cut them if they're tutorial clones (a to-do app, a weather app) and you have real work experience.
Give each project a one-line tech stack and 1–3 bullets, the same as a job.

The skills section

Group skills by type instead of one long comma list, and keep only what you'd be comfortable being quizzed on. A skill that appears in the list and in a bullet is far more convincing than one that only appears in the list. See how to write the skills section.

Format and length

One page unless you have 10+ years of directly relevant experience.
Single column. Multi-column layouts can be read out of order by some parsers.
Standard fonts, no text inside images, no icons standing in for words.
Export a real text PDF, not a scan or a screenshot.
Dates right-aligned, consistent format (“Jun 2023 – Present”).

The widely shared Jake's Resume template follows all of these rules, which is why it's so popular in engineering circles.

Guides by role

Frontend engineer resume: performance, accessibility and UI outcomes.
Backend engineer resume: scale, latency and reliability.
DevOps or SRE resume: deploys, incidents, uptime and cloud cost.
Data engineer resume: volume, freshness and pipeline reliability.
Machine learning engineer resume: evaluation metrics and production results.

How ResumeForDev does this for you

ResumeForDev asks one question per screen (role, stack, experience, projects, education, achievements), then asks 4–7 follow-up questions about the gaps it finds, like “how many users did this serve?”. It writes bullets in the shape above, removes any number or skill you never gave it, and lays the result out in a faithful port of Jake's template, auto-fitted to one Letter page. Your first resume is free.

Frequently asked questions

Should a software engineer resume be one page?: Yes, for almost everyone under about ten years of experience. Recruiters skim, and a second page usually holds older, less relevant work. Cut to your strongest 2–4 bullets per role.
Do I need a summary at the top?: Usually not. For engineers, a summary takes space that a bullet with real evidence would use better. The exception is a career change, where one or two lines can explain the switch.
Should I include GPA?: Include it if you're a student or recent grad and it's 3.5 or higher, or if the employer asks for it. Drop it after your first job or two.
How many bullets per job?: Two to four for most roles, up to five for your current or most relevant role. Each bullet should describe a distinct thing you built or changed.
What does a good software engineer resume look like?: One page, single column, with a header of links, a grouped skills section, experience and projects written as action, technology and result, and education. Jake's resume template is the most common example.
How do I write a software developer resume with no experience?: Lead with education and two or three projects written like jobs, each with a stack and a result. Add internships, hackathons, open-source work or tutoring. See the new grad and self-taught guides.