CV example

Software Engineer CV Example

A software engineer's CV should show what you have built, the technologies you used to build it and the difference it made to users or the business. Recruiters scan for your main languages and frameworks first, so make them easy to find, then use your bullet points to show engineering judgement: design decisions, reliability, performance, testing and collaboration.

This example follows UK conventions: two pages at most, British spelling and a personal statement at the top.

Example software engineer personal statement

Software engineer with five years' experience building web applications and APIs in TypeScript, Node.js and React for a subscription software business. Comfortable across the stack, from database design to front-end performance, with a strong interest in testing and developer tooling. Mentors junior engineers and takes part in the on-call rota. Seeking a senior engineer role in a product-led team.

Key skills for a software engineer CV

  • Languages such as TypeScript, JavaScript, Python, Java or C#
  • Front-end and back-end frameworks such as React, Node.js, Django or .NET
  • REST and GraphQL API design
  • Relational and NoSQL databases, including SQL query tuning
  • Cloud platforms such as AWS, Azure or Google Cloud
  • Automated testing, CI/CD pipelines and version control with Git
  • Containers and infrastructure as code
  • Code review, agile delivery and mentoring

Example work experience bullet points

  • Designed and built a billing API in Node.js and PostgreSQL that replaced a manual invoicing process used by the finance team.
  • Reduced the median page load time of the customer dashboard by around 40 per cent by introducing code splitting and caching of API responses.
  • Raised automated test coverage on the core service from a low base to a level where releases moved from fortnightly to several times a week.
  • Led the migration of a monolithic application's authentication module to a separate service, with no downtime during cut-over.
  • Took part in the on-call rota, leading the investigation of two production incidents and writing the follow-up reviews.
  • Mentored two junior engineers through pairing and code review, both of whom now own features independently.

How to write your software engineer CV

  • Group technical skills by type, such as languages, frameworks, databases and cloud, and lead with those in the job advert.
  • Say what the software did and who used it, not only which technologies it involved.
  • Include measurable effects where you have them, such as performance, reliability, release frequency or time saved, and only figures you can explain.
  • Link to a code repository or portfolio if it shows work you are proud of; it matters most early in your career.
  • Leave out technologies you have only touched briefly. You may be asked detailed questions on anything you list.

UK CV or US resume?

The title is the same in both countries, with 'software developer' also common in the UK. For a US application, call the document a resume, keep it to one page if you have under ten years or so of experience, use American spelling such as 'optimized', and replace the personal statement with a short summary. US candidates who need visa sponsorship, or who already have work authorization, usually say so.

Frequently asked questions

What should a software engineer CV include?

A short personal statement, a grouped technical skills section, work experience bullets that describe what you built and its effect, education, and links to a repository or portfolio where relevant.

Should I include personal projects and open source work?

Yes, particularly if you are early in your career or moving into a new technology. Describe them like work: the problem, the stack and the result. Experienced engineers can keep this section short.

How long should a software engineer CV be?

Two pages at most in the UK. In the US, one page for early-career engineers and two for experienced ones. Summarise older roles and outdated technologies briefly.