Software engineer resume examples: projects, stack and impact

How to format a software engineer resume in 2026

Keep the resume to one page if you have fewer than ten years of experience, two pages if you have more. Use a single-column layout for ATS compatibility. Applicant tracking systems at companies like Google, Amazon and most mid-size tech firms parse left-to-right, so avoid tables and text boxes.

Use a standard font such as Calibri, Inter or Georgia at 10 to 11 points. Margins of 0.6 to 0.75 inches give you space without looking cramped. Save as a PDF unless the job posting explicitly asks for a Word file, which some Workday portals still do.

• Name and contact details at the top: city, LinkedIn URL, GitHub URL, professional email
• Section order for most engineers: Summary, Skills, Experience, Projects, Education
• Flip Projects above Experience if you are a new graduate or career changer
• No photo, no date of birth, no marital status (standard in the US, Canada, UK and Australia)

Writing your tech stack section

List technologies under clear sub-labels so a recruiter can scan in three seconds. Group by category rather than dumping every tool in one line. Honest depth matters more than length: if you used Redux once, do not list it alongside React, which you use daily.

A clean skills block might look like this: Languages: Python, TypeScript, Go | Frameworks: FastAPI, React, Next.js | Databases: PostgreSQL, Redis, DynamoDB | Infrastructure: AWS (EC2, Lambda, S3), Docker, Terraform | Tools: GitHub Actions, Datadog, Jira. Update this block for each application by mirroring the exact terms in the job posting, because ATS systems match on string literals.

Impact bullets for work experience

Every bullet should answer three questions: what did you do, how did you do it and what changed as a result. The formula is: action verb + technical detail + outcome with a number. Avoid vague verbs like 'worked on' or 'helped with'.

If you do not have an exact figure, use a defensible range or a relative improvement. 'Reduced median API latency from 420 ms to 95 ms by replacing synchronous database calls with a Redis cache' is better than 'improved performance'. If you genuinely cannot quantify, describe scope: 'Served 2 million monthly active users' or 'Owned the payments service processing roughly $4 million in transactions per month'.

• Migrated a monolithic Rails app to microservices on Kubernetes, cutting deployment time from 45 minutes to under 8 minutes
• Built a real-time fraud detection pipeline in Python and Apache Kafka that flagged 94% of fraudulent transactions before settlement
• Reduced AWS monthly spend by approximately $18,000 by right-sizing EC2 instances and moving cold data to S3 Glacier
• Led a team of four engineers to deliver a HIPAA-compliant patient portal on schedule, covering auth, audit logging and encryption at rest
• Wrote 340 unit and integration tests that raised code coverage from 41% to 87% and eliminated a class of regression bugs

How to write a projects section that gets attention

Projects are the most underused section on engineer resumes. They let you show skills your job history does not cover and demonstrate initiative. Include two to four projects: at least one personal or open-source project and, if you are a new graduate, one academic project that involved real engineering decisions.

For each project, give it a name, link to the GitHub repo or live URL, a one-line description of what it does and two to three bullets covering the stack, a technical challenge you solved and any usage or contribution numbers you can cite honestly.

1. Project name and link: 'Pricetrace | github.com/yourhandle/pricetrace'
2. What it does in one sentence: 'A serverless price-tracking tool that monitors e-commerce listings and sends alerts via SMS.'
3. Stack bullet: 'Built with AWS Lambda, DynamoDB and Twilio; deployed via Terraform and GitHub Actions CI/CD pipeline.'
4. Challenge bullet: 'Handled rate-limiting from five retailer APIs by implementing exponential back-off and per-domain request queuing.'
5. Impact bullet: 'Reached 300 active users within six weeks of launch with zero infrastructure cost under AWS free tier limits.'

Summary statement: what to write and what to skip

A two to three sentence summary at the top helps a recruiter place you in five seconds. State your level, your primary domain and one or two differentiators. Do not copy the job description back at the reader and do not use phrases like 'passionate developer' or 'results-driven engineer'.

Example for a mid-level backend engineer: 'Backend engineer with five years building distributed systems in Go and Python. Specialise in high-throughput data pipelines and cloud-native architecture on AWS. Contributed to open-source projects in the CNCF ecosystem with over 400 GitHub stars across personal repositories.' Tailor the domain and technologies to each role.

Tailoring your resume for each application

A generic resume performs worse than a tailored one because ATS systems score keyword density and hiring managers notice when a resume does not reflect the role. The minimum tailoring for each application is: adjust the summary, reorder your top three skills to match the posting and swap in one or two bullets that use the posting's exact language for the same work you already did.

Break-In Bad's resume enhancement conversation can help here. Omar reads your existing resume, asks up to 20 questions about your experience and projects, then rewrites each section with tailored bullets and stack details drawn only from what you confirm. She checks every line against your answers so nothing is invented. You can tap or speak your replies, which makes it faster than filling in a form. The result is a resume and cover letter pair matched to a specific job posting, built from facts you verified.