Engineering resumes are read by an engineer, usually in under a minute, looking for one thing: evidence you have shipped something non-trivial and owned it in production.
Keywords an ATS holds for software engineer roles
These are the terms that recur across software engineer postings and appear in the search filters recruiters run. They are not a checklist to paste in — use the ones that describe work you have genuinely done, phrased the way the market phrases it.
- software engineer
- full stack
- backend
- frontend
- distributed systems
- microservices
- api design
- rest api
- graphql
- system design
- code review
- unit testing
- integration testing
- ci/cd
- continuous integration
- agile
- scrum
- cloud
- containerisation
- observability
- performance optimisation
- technical design
- on-call
- incident response
Core skills to list explicitly
Skills sections are parsed into structured fields and searched directly, so a skill only mentioned inside a bullet is weaker than one listed here as well. Split them the way hiring managers think about them.
- Hard skills — Python, Java, TypeScript, JavaScript, Go, C++, React, Node.js, SQL, REST APIs, GraphQL, System design, Data structures & algorithms, Test automation, Concurrency, Caching, Message queues
- Tools and platforms — Git, Docker, Kubernetes, AWS, GCP, Azure, Terraform, Jenkins, GitHub Actions, PostgreSQL, MongoDB, Redis, Kafka, Datadog, Jira, Postman
- Working skills — Code review, Technical writing, Mentoring, Cross-functional collaboration, Incident communication, Estimation
The numbers that move a software engineer hiring manager
Quantified bullets consistently outperform unquantified ones, but the useful numbers are role-specific. These are the ones that get read in this field. Use only figures you can defend in an interview — the builder will leave an [ADD METRIC] placeholder rather than invent one for you.
- Requests per second or daily active users the system served
- Latency reduction (p50/p95/p99) in milliseconds or percent
- Cost reduction in infrastructure spend
- Deployment frequency and lead time before and after
- Test coverage or defect-escape rate change
- Size of codebase, service count or team you supported
- Incidents reduced, or MTTR improvement
Example bullets (illustrative)
These are examples of shape and specificity, not text to copy. They belong to nobody, and the AI writers will never insert them into your resume — everything they produce comes from your own profile.
- Rebuilt the checkout service's payment retry logic in Go, cutting failed transactions from 4.1% to 0.7% across roughly 90,000 daily orders.
- Led the migration of 14 services from EC2 to EKS, reducing monthly infrastructure spend by 31% and deploy time from 22 minutes to under 4.
- Designed and shipped the public REST API used by 3 partner integrations, including versioning, rate limiting and OpenAPI documentation.
- Introduced contract testing across 6 services, which cut integration-related production incidents from 9 per quarter to 2.
- Mentored 3 junior engineers through their first on-call rotations and wrote the runbook set the team still uses.
Mistakes that recur on software engineer resumes
- Listing technologies instead of outcomes — A wall of 40 technologies tells a reviewer nothing about what you built. Group your stack in the skills section and spend your bullets on systems, scale and results.
- No scale anywhere on the page — 'Built a microservice' could mean an internal tool with 5 users or a service handling 40,000 requests per second. Without a number, reviewers assume the smaller one.
- Describing the team's work as your own — 'Developed a platform used by millions' invites an interview question you cannot answer. State your actual component and your actual role in it.
- Burying production ownership — On-call, incident response, migrations and deprecations are strong signals of seniority and are routinely left off. They belong on the page.
- Two-column templates through a corporate portal — Engineering resumes are keyword-dense, which makes column scrambling especially damaging. Use a single-column layout for portal submissions.
Section order and structure
Put technical skills above experience. Engineering recruiters search on stack before they read prose, and a skills block in the top third is found faster by both the parser and the person.
Recommended template: Circuit for stack-heavy engineers, Atlas or Northline for a general application.
- Contact
- Professional Summary
- Technical Skills
- Work Experience
- Projects
- Education
- Certifications
Writing the summary
Three lines: your specialism and years, the scale of the systems you have worked on, and your strongest single result. 'Backend engineer, 6 years, Go and Python, services handling ~40k rps; cut checkout failure rate from 4.1% to 0.7%.'
Certifications worth listing
Certifications are frequently used as hard filters, so list every relevant one you hold with the awarding body and year. Never list one you are 'planning to take' — in progress with an exam date is acceptable and honest.
- AWS Certified Solutions Architect
- AWS Certified Developer
- Google Cloud Professional Cloud Architect
- Certified Kubernetes Administrator (CKA)
- Microsoft Azure Developer Associate
- Oracle Certified Professional, Java
Frequently asked questions
- Should a software engineer resume be one page?
- One page under about eight years of experience, two beyond that. Staff and principal engineers regularly need two pages to describe architectural scope, and reviewers accept it at that level.
- Do I need a GitHub link?
- Include it if the profile has substantive work — real repositories with commits, documentation and history. An empty GitHub link is worse than none, because reviewers do click it.
- How do I list side projects?
- In a Projects section, with the same discipline as work: what it does, the stack, and a number — users, stars, downloads, or the problem it solved. Cut anything abandoned at the tutorial stage.
- Should I include LeetCode or competitive programming?
- Only if it is exceptional — a Codeforces rating or an ICPC placing. Ordinary practice counts is noise on a resume, though it does help you in the interview it gets you.
- How do I handle a career gap as an engineer?
- State it plainly with one line of context, and if you built or learned anything during it, list that. Engineering hiring managers are generally pragmatic about gaps; concealment is what raises questions.