What should a software engineer resume summary say?

A software engineer summary should state your level, your main language or stack, the kind of systems you build and one result that shows impact. Keep it to two or three sentences and match it to the job you are applying for.

A useful structure:

• Level and focus: "Backend software engineer with five years in Java and Spring Boot."
• What you build: payment services, mobile apps, data pipelines, internal tools.
• One outcome: faster releases, fewer incidents, lower latency.

Example (fictional): "Backend software engineer with five years building Java and Spring Boot microservices for e-commerce. Designed an order service handling peak holiday traffic and cut average API response time from 800 ms to 250 ms. Comfortable with AWS, Docker and CI/CD pipelines."

Avoid vague openers such as "passionate coder who loves technology". A hiring manager wants to know quickly which stack you know and what problems you have solved with it.