Independent data publication. Not affiliated with UCAS, SLC, HESA, or GOV.UK. How we source figures

CV & Careers · CourseToJob

Software Developer CV example

What to include in a software developer cv: relevant evidence, skills, sample achievement structures and template suggestions.

A useful starting point

Lead with the stack you actually shipped, then two systems with scale. Two pages. Skip icon skill clouds. Skip this example if you are a new graduate with only course work — use the student or graduate page and one page.

These examples illustrate structure, not a real applicant’s history. Replace every sample detail with your own evidence. Follow the employer’s instructions on qualifications, registration, document length and file format.

Evidence to consider

  • Languages and frameworks you used in production
  • One system with traffic or users
  • Testing and CI you touched
  • Links to a real repo or product if public

Illustrative achievement bullets

  • Shipped a Go payments worker handling 2M requests/day with p99 under 120ms
  • Cut CI time 35% by splitting a monolith test suite on GitHub Actions
  • Owned on-call for a service for two quarters; MTTR 40 minutes on Sev-2s
  • Mentored 2 juniors through a RFC process for a schema change

Relevant skills to substantiate

Go · TypeScript · PostgreSQL · GitHub Actions · Kubernetes · On-call

What to leave out

  • Twenty languages you tried once
  • Photos
  • Two-column rails on an ATS form

Choose a layout

Explore the modern template or use it in the CV builder. This is a suggested layout; follow the vacancy’s requirements.

Related roles

Frequently asked questions

Should I list every language?

List production ones. A zoo of unused names is a smell.

Is a GitHub link required?

Useful if the work is public. Do not link an empty profile.

One page or two?

Two once you have more than a couple of roles. New grads can stay on one.