A skills list with no evidence
Twenty logos tell a reviewer nothing about depth. Keep the list to the tools you can discuss, and make sure each important one appears inside a bullet that shows what you built with it.
Engineering resumes get filtered twice: once by an applicant tracking system looking for language overlap with the job description, and once by an engineer who has thirty seconds and a bias toward evidence. The fastest way to lose either reader is a skills cloud with no context and bullets that describe tickets instead of systems.
Templates
Pick a layout, then make the content specific. Every option below keeps a single parseable column.
Software engineer with 5 years building customer-facing web applications in TypeScript and React. Focused on performance, reliable delivery, and systems that other teams can operate without escalation.
University of Washington
Modern
Built for engineering resumes: a project and stack section that stays readable without turning into a two-column grid.
SOFTWARE ENGINEER
Software engineer with 5 years building customer-facing web applications in TypeScript and React. Focused on performance, reliable delivery, and systems that other teams can operate without escalation.
Modern
A modern tech layout that still keeps headings and dates in a single parseable order.
Professional
The conservative option for large company portals. Plain text, standard sections, no parsing surprises.
What gets screened
These are the details that survive the first scan. If one is missing, the resume is read as a weaker match before anyone reaches the bullets.
Languages and frameworks tied to something you built, not a logo wall with no context.
Scope and scale: users, requests per second, data volume, latency, uptime, and team size.
Ownership beyond tickets: design, migration, on-call, code review, and mentoring.
Reproducible proof such as a GitHub profile, portfolio, or published package that is actually current.
Example bullets
Replace the brackets with your own numbers. Keep the structure, and drop any bullet that does not match your experience.
Avoid these
Twenty logos tell a reviewer nothing about depth. Keep the list to the tools you can discuss, and make sure each important one appears inside a bullet that shows what you built with it.
"Responsible for the payments service" is a job description. State what shipped, the scale it ran at, and the measurable change. If you do not have a metric, use scope instead.
Icon rows and rating bars are invisible to many parsers and unreadable to a skim. Write the technology names as text in the skills section and in the bullets.
FAQ
One page is enough under about ten years of experience. Senior and staff engineers can use two pages when the second page carries distinct systems, migrations, or leadership work rather than repeated responsibilities.
Yes, if the profile is active and relevant. Pin three or four repositories with a clear README instead of linking an empty account. A stale profile is worse than no link.
They help early-career engineers and career changers. Include one or two projects that show the stack, the problem, and an outcome. Once you have shipped production work, projects should support the experience rather than replace it.
Use scope: the number of teams or users affected, the systems touched, the frequency of the work, and the before and after state. Scope is evidence even when a clean percentage is not available.
Keep going
One tailored resume, every free template, 10 AI rewrites,
and 3 PDF exports. No credit card.

