Software Engineer resume
What the hiring manager reads first
All roles Software engineering Reading notes, not rules
Summary
An engineering manager usually looks first for what the candidate built or worked on, the system around it and the stack it ran on.
Also posted as: software developer, swe, programmer, application developer, software development engineer, sde, java developer, python developer, net developer, c# developer, golang developer, go developer, php developer, ruby on rails developer, game developer.
Read first
- Systems or features you owned end to end
- Scale: users, requests, data, latency
- Measured impact on speed, reliability, cost or revenue
- Languages and frameworks named where you used them
One line, before and after
Original: Worked on the checkout service in Go. Moved pricing to a cached service, which cut p95 latency from 900 ms to 320 ms.Suggested: Cut p95 checkout latency from 900 ms to 320 ms by moving pricing to a cached service in Go.
Section order
- Summary
- Experience
- Projects
- Skills grouped by type
- Education
Where your resume has these sections. A section your resume does not have is not added.
Mistakes that cost interviews
- A wall of technologies with no context
- Team achievements written as yours
- Seniority buzzwords
- Team achievements written as personal ones
- Seniority words the resume does not support
Evidence that counts in software engineering
- Systems or features worked on, and the candidate's part in them
- Scale: users, requests, data volume, latency, cost
- Measured effect on reliability, performance or cost
- Stack named where it was used, not only in a skills list
- Code review, mentoring and design work for senior roles
- Shipped side projects or open source for early careers
Use what your resume already shows. A line without a number can still be strong when it says clearly what you did and where.
These are common reading conventions drawn from hiring guides and career services, not rules every employer follows.