A software engineer resume has to survive two very different readers. The recruiter's pass is a keyword-and-shape scan: do the languages match, do the years add up, does the last title map to the level we're hiring for. The tech lead's pass is a credibility scan: do the bullets describe real engineering work, or do they read like someone listing every technology they've ever sat near. Most engineering resumes are optimized for one reader and fail the other. This guide shows you how to pass both, with a full annotated example and level-by-level bullet patterns.
How engineering resumes get read: recruiter pass vs tech-lead pass
The recruiter typically screens against the job description: required languages, cloud platform, years of experience, and sometimes degree or visa constraints. They are matching, not evaluating. This is where a clean skills section and a title history that parses correctly matter most — if your resume goes through an applicant tracking system first, the same rules apply as any ATS-focused resume: standard headings, no columns holding critical data, real text rather than graphics.
The tech lead reads differently. They skim your most recent role and look for three signals:
- Specificity. "Reduced p95 latency from 1.8s to 240ms" is engineering. "Improved performance" is marketing.
- Ownership scope. Did you build a feature, own a service, or design a system? Titles inflate; described scope doesn't.
- Judgment. Trade-offs mentioned, migrations survived, incidents handled. Anything suggesting you've operated software, not just written it.
Write every bullet so it satisfies the second reader without losing the keywords the first reader needs.
Example software engineer resume
Maya Chen Software Engineer — Backend & Distributed Systems Oakland, CA | maya.chen.dev@email.com | github.com/mayachen-dev | linkedin.com/in/mayachen
Summary Backend engineer with 5 years building and operating Go and Python services at logistics and fintech startups. Led the redesign of a shipment-tracking API serving ~50k daily requests and the zero-downtime migration of its Postgres cluster. Looking to own service architecture on a small team with real production responsibility.
Experience
Software Engineer — Harborview Logistics (remote) | Mar 2023 – present
- Rebuilt the shipment-tracking API in Go, cutting p95 response time from 1.8s to 240ms for ~50k daily requests across 3 client integrations
- Designed and executed a zero-downtime Postgres 13→16 migration for the primary orders database (~400GB), including a rollback plan exercised in staging
- Introduced structured logging and OpenTelemetry tracing across 6 services, reducing median incident diagnosis time from hours to under 30 minutes by the on-call team's own postmortem notes
- Mentor two junior engineers through weekly pairing and design-review feedback; both shipped their first independently owned features within a quarter
Software Engineer — Brightledger (fintech) | Jun 2021 – Mar 2023
- Built the reconciliation service (Python, Celery, Redis) matching ~120k daily transactions against bank feeds, with automated discrepancy flagging that cut manual review volume roughly 70%
- Migrated CI from Jenkins to GitHub Actions, reducing average build time by 12 minutes and flaky-test reruns by half
- Implemented rate limiting and idempotency keys on public payment endpoints after a duplicate-charge incident; zero recurrences in the following 18 months
Junior Developer — Corvid Web Studio | Jul 2019 – Jun 2021
- Delivered features across 8 client Django applications; owned the booking system rewrite for a regional clinic chain used by ~200 staff daily
Skills
- Languages: Go, Python, SQL, TypeScript (working)
- Infrastructure: PostgreSQL, Redis, Docker, Kubernetes (EKS), Terraform, AWS
- Practices: observability (OpenTelemetry, Grafana), CI/CD, incident response, design docs
Education B.S. Computer Science — Cal State East Bay, 2019
Why this resume works, section by section
Header. GitHub and LinkedIn links, city without full address, a headline that states specialization. "Backend & Distributed Systems" tells a recruiter which pile to put this in before reading a word of experience. More on link choices in our resume header guidance.
Summary. Three sentences: scope (5 years, Go/Python, two industries), proof (two specific achievements), direction (what she wants next). No adjectives doing unpaid work — no "passionate," no "results-driven."
Experience. Every bullet follows action-scope-result, the same formula our resume bullet points guide teaches, but with engineering-native evidence: latencies, data sizes, request volumes, incident outcomes. Note the honesty texture — "roughly 70%," "by the on-call team's own postmortem notes." Hedged numbers you can defend beat precise numbers you invented.
Skills. Grouped, short, and honest — TypeScript is marked "working" rather than silently padded into the expert pile. A tech lead trusts a resume more when it admits gradients. See technical skills for a resume for formatting alternatives.
Education. One line, at the bottom, because five years of experience outranks any coursework. A new grad would flip this ordering.
Project bullets that show impact, not just stack
The most common engineering-bullet failure is the stack list: "Built microservices using Go, Kafka, Kubernetes, and gRPC." That sentence contains four keywords and zero information. What did the service do? For whom? What changed because it existed?
The fix is to make the technology grammatically subordinate to the outcome:
- Weak: "Used Redis for caching."
- Strong: "Added a Redis cache layer for catalog queries, dropping database load ~40% during peak promotional traffic."
If you genuinely have no metric, describe the before/after state: "replaced a manual CSV export process that previously required a support engineer's afternoon each week."
GitHub, portfolio, and side projects: what to link and what to skip
Link a GitHub profile only if a visitor will find signal there: pinned repositories with READMEs, meaningful commit history, or a project someone actually uses. A profile with two forked tutorials hurts more than no link at all.
Side projects earn resume space under two conditions: they demonstrate a skill your paid work doesn't, or you're early-career and need the material. One or two, with the same bullet discipline as jobs — users, scale, or a technical challenge solved. Skip the abandoned hackathon list.
Bullet examples by seniority
Junior (0–2 years):
- Fixed 30+ bugs across the checkout flow in my first six months, including a race condition causing intermittent double-submits
- Wrote integration tests for the notifications service, raising coverage from 40% to 75% and catching two regressions before release
- Built an internal CLI tool for seeding test data, adopted by the full 8-person team
Mid-level (2–6 years):
- Owned the payments webhook service end to end: design doc, implementation in Go, deployment, and on-call runbook
- Led migration off a deprecated third-party auth provider for ~90k user accounts with no forced password resets
- Reduced cloud spend on the staging environment ~35% by right-sizing instances and scheduling non-production shutdowns
Senior (6+ years):
- Designed the event-driven architecture (Kafka, schema registry) adopted across 4 product teams, replacing point-to-point integrations that had caused three cross-team outages the prior year
- Ran the technical interview loop redesign; time-to-decision dropped from 3 weeks to 9 days while onsite pass-through quality held steady per hiring-manager review
- Drove the postmortem program: 100% of Sev-1 incidents reviewed within a week, with tracked action items closing at over 80%
Notice the progression: juniors prove they finish things, mid-levels prove they own things, seniors prove they change how other people work.
Skills and keywords for software engineering roles
Pull the exact spellings from each posting, then draw from this pool where true:
Languages and frameworks: Python, Go, Java, TypeScript, JavaScript, C#, Rust, Node.js, React, Django, Spring Boot Data and infrastructure: PostgreSQL, MySQL, Redis, Kafka, Elasticsearch, AWS, GCP, Azure, Docker, Kubernetes, Terraform Practices: REST API design, gRPC, microservices, CI/CD, test-driven development, observability, incident response, code review, agile AI-era additions (only if genuine): LLM API integration, retrieval-augmented generation, prompt evaluation, GitHub Copilot / AI-assisted development workflows
On that last group: listing AI tooling credibly means naming what you built or changed with it — "built an internal support-ticket classifier on the OpenAI API with an evaluation set of 500 labeled tickets" — not "AI enthusiast." Interviewers now probe these claims routinely.
Common mistakes on software engineer resumes
- The everything skills list. Fifteen languages signals depth in none. Cap it at what you'd accept an interview question about.
- Stack-only bullets. Technology named, outcome missing (fix above).
- Team achievements claimed solo. "Scaled the platform to 10M users" from a 200-engineer company invites the question you can't answer. Claim your slice: the service, the migration, the feature.
- Graphics-heavy templates. Skill bars and icon columns can lose data in parsing and read as junior to senior reviewers. Plain structure wins; see the broader patterns in our resume examples pillar.
- No production evidence. Resumes listing only builds, never operations — no incidents, no monitoring, no migrations — read as untested at mid-level and above.
- Buried recency. Leading with a 2016 role because it had a bigger brand. Recruiters read top-down; your most recent, most relevant work goes first.
Frequently asked questions
Should a software engineer resume be one page or two?
One page through roughly 8–10 years of experience is a safe default; two pages are fine when you have genuinely distinct senior roles to document. What kills engineering resumes isn't a second page — it's the first page wasting space on a 2014 internship.
Do I need a summary section?
It's optional. It earns its space when it resolves ambiguity — career changers, specialists whose titles undersell them, or engineers targeting a narrower role than their history suggests. A mid-level engineer applying to an obviously matching role can skip it and let the first three bullets do the work.
How do I list technologies I've used only briefly?
Either mark the gradient ("working knowledge") or leave them off. The interview cost of an overstated skill is far higher than the screening cost of a shorter list. If a posting demands something you've only touched, address it honestly in the bullet where you touched it.
Does a computer science degree still matter?
For most experienced roles, demonstrated work outweighs the degree, and the education section shrinks to one line. It matters most for new grads, some large enterprises, and visa-related requirements. Bootcamp grads and self-taught engineers should lead with projects and experience, exactly as a degree-holder with experience would.
Run your resume past a parser before a person
Workplacea shows its work: paste your engineering resume into the free resume checker and see exactly what a parser extracts — titles, dates, skills — plus the specific fixes, with reasoning you can verify. When you're ready to rewrite, the editor keeps every claim yours.