How to write a Software CV

The conventions below are the ones this field actually uses. They are what the builder applies when you pick Software / IT, and what the rating checks a finished CV against.

What it must contain

Leave any of these out and the CV reads as incomplete to someone who hires in this field:

Technical Skills
Work experience — Lead with what changed: latency, error rate, build time, cost, users served.

The order to put them in

Order is not cosmetic. What sits at the top is what gets read before someone decides whether to keep reading.

Professional summary
Technical Skills
Work experience
Projects
Education
Certifications
Achievements
Languages

Section by section

Professional summary — Name the stack and the kind of systems you build. Skip adjectives.
Projects — Recruiters do open these links. Only list what you would be happy to have read.

What to put numbers on

The single most common reason a CV in this field reads as weak is that nothing in it is measured. These are the figures that mean something here:

latency · p95 · uptime · throughput · build time · error rate · test coverage · requests per second · users

Verbs that carry weight

Openers like “responsible for” and “worked on” describe a job description rather than a person. In this field these do the work instead:

Built · Shipped · Migrated · Reduced · Automated · Designed · Scaled · Refactored · Instrumented · Debugged

What gets one rejected

A GitHub or portfolio link is close to mandatory for engineering roles.

Length

1 to 2 pages is normal for this field.

Build a Software CV See a worked example

Free, no account, and nothing is uploaded — the builder runs in your browser and the CV never leaves it.