Technology · Resume guide

How to write a software engineer resume

A great engineering resume proves you ship things that matter, not that you know a long list of languages.

Recruiters skim for scope, impact, and a stack that matches the role. Give them numbers — latency, users, revenue, uptime — and a clean summary they can read in ten seconds. The rest is detail.

What recruiters look for

Systems you actually shipped, with the scale they ran at
A tech stack that overlaps with the job posting
Impact in numbers — latency, throughput, uptime, revenue, users
Signs of ownership: you led a project, not just closed tickets
A GitHub, portfolio, or link that backs up the claims

Skills worth highlighting

Hard skills

JavaScript / TypeScriptPythonReactNode.jsPostgreSQLAWSCI/CDSystem designTesting

Soft skills

Code reviewMentoringCross-team collaborationClear written communication

ATS keywords for a software engineer resume

Applicant tracking systems match your resume against the job posting. Weave these terms in where they are genuinely true — never pad with skills you don't have.

ReactNode.jsTypeScriptREST APIsmicroservicesCI/CDunit testingAgilecode reviewcloud (AWS/GCP)

Bullet points, before and after

The pattern is the same every time: start with an action, add the detail, land on a result. Here it is on real software engineer lines.

Before

Worked on the backend and fixed bugs.

After

Cut API p95 latency 38% by adding Redis caching and query indexes, across ~2M requests a day.

Before

Built new features for the web app.

After

Shipped a checkout redesign in React that lifted conversion 12% and cut support tickets 20%.

Common mistakes to avoid

  • Listing every language you have ever touched instead of the ones you are strong in
  • Describing responsibilities ("responsible for the API") with no outcome
  • Writing dense paragraphs where scannable bullets belong
  • No link to code, a portfolio, or anything that backs the claims

How to structure it

Header with a GitHub or portfolio link, a two-line summary, then a skills block grouped by languages / frameworks / tools so a recruiter can pattern-match fast. Experience comes next with impact bullets; if you are early-career, a Projects section carries real weight. Education goes last.

Frequently asked questions

More resume guides

Put it into practice

Build your software engineer resume in HubKit

Start from a clean, ATS-safe template and fill in the sections as you read. The preview matches your PDF export exactly, and it's free to start.