Resume examples · Software engineer
A software engineer resume gets about ten seconds with a recruiter before the first yes or no. The engineers who pass that screen are not always the best engineers. They are the ones whose resumes state what they built, for how many users, and what changed because of it.
The screen
How many users, requests, or dollars did your systems touch? "Payments service handling 2M transactions a day" beats a paragraph about microservices.
A skills list alone reads as a keyword dump. Name the stack inside the work: "Rebuilt the search API in Go" proves Go better than a bullet that says "Go."
Recruiters look for verbs that show you led the work: designed, built, shipped, migrated. "Contributed to" and "assisted with" read as bystander verbs.
Promotions and growing scope matter more than any single project. If you were promoted, make it its own line so it cannot be missed.
Example
Every bullet names a technology, a number, or both. None of them says "responsible for."
Mistakes
Many applicant tracking systems read columns out of order. Use a single column with skills as a short section in the main flow.
Twenty-five skills reads as five. List the ten you would be comfortable interviewing on tomorrow.
"We built" hides you. State what you personally designed, wrote, or led, and let the scale of the system show the team context.
Latency, error rates, users, revenue, team size, uptime. If a number is confidential, use a ratio: "cut costs 40%" reveals nothing absolute.
Questions
One page under ten years of experience. Two pages at most after that. Recruiters spend seconds per page, so a tight single page usually outperforms a loose two.
Yes if they shipped and you can name users or downloads, or if you are early in your career. A GitHub link belongs in the header only when the pinned repos are ones you want discussed in an interview.
Only if it says something the title line cannot. "Backend engineer, 8 years, payments and fraud systems at two fintechs" is worth four lines of adjectives.