Software engineer CV example and writing guide

Use a clean, reverse-chronological layout with clear headings and an ordinary, readable typeface. Two pages will suit many candidates. An entry level software engineer CV may fit on one page if the content is selective, while an experienced candidate will usually need more room for recent work. Start with contact details, then add a personal statement, technical skills, experience, education and relevant extras.

Keep the personal statement to one compact paragraph. Say what sort of software you work on, where your strongest experience lies and what you have achieved. Claims such as "excellent coder" waste space unless the CV proves them.

For each job, show the title, employer, location and dates before the achievement bullets. Software engineers can contribute to requirements, analysis, design, coding, build, testing, implementation and support. Choose the parts of that lifecycle that match the vacancy instead of squeezing every responsibility into every role.

Group technical skills by type so the reader can find them quickly. Include only tools you have genuinely used and can discuss. Use the experience section to show how you worked with product managers, UX designers and engineering colleagues, since software delivery commonly involves a collaborative team.

Recent graduates can place education and selected projects above limited employment. Move education below experience once your professional work provides stronger evidence. Extras should earn their space: include a project when it shows relevant engineering judgement, not simply because you completed it.

Tailor each software engineer CV to the application. Borrow relevant language from the advert when it accurately describes your experience, particularly where CV-scanning software may be used, but keep the wording natural.

Treat each bullet as a small piece of evidence. Start with a precise action, name the technical scope, then give the result and a measure you can defend. Useful measures include response time, failed deployments, support tickets, test duration, release frequency, defect count and engineering time saved. The result does not need to be financial.

A reliable pattern is: action + technical change + scale or constraint + outcome. For instance: "Reworked database queries for the order-history service, cutting median response time from 1.8 seconds to 1.1 seconds across 40,000 weekly requests." The reader can see what changed, where it changed and why the work mattered.

Choose verbs that match your contribution: built, designed, implemented, refactored, tested, reviewed, diagnosed, automated, migrated, integrated or mentored. Use "led" only when you set direction or coordinated other people's work. When several engineers shared an outcome, state your part without taking credit for the whole team's output.

A junior software engineer CV can use placements, coursework and personal projects. Explain the problem, your own contribution and the result. A more experienced software engineer CV should put greater weight on production scope, design decisions, maintenance, support and teamwork. If you supervised junior developers or colleagues working on part of a solution, say who you supported, what you reviewed and what improved.

Do not write a catalogue of technologies. "Used Python, SQL and Git" says little on its own. If your work centres on machine learning models rather than general software delivery, the machine learning CV guide may be a closer fit. Place those tools inside achievement bullets, then keep a short skills section for scanning. Focus on accomplishments and project impact instead of copying responsibilities from the job description.

List education in reverse-chronological order. Give the qualification, subject, institution and completion year. Add the grade when it supports the application or the employer requests it. Recent graduates may include a short selection of relevant modules or a final project, but the description should identify the problem, the candidate's contribution and a result they can verify.

For larger UK employers recruiting undergraduates into software engineer roles, an Undergraduate degree at 2:1 or above is preferred by many employers, but it is not essential. State the qualification and grade accurately if you hold them; do not present this preference as a rule for every vacancy.

A Relevant level 2 qualification is an optional route that may support entry to an entry-level software engineer position or apprenticeship in the UK. Candidates using this route should reproduce the exact qualification title on their CV, with the institution and completion date, then add relevant project or practical evidence.

The grounding available for this guide does not establish a named professional certification for software engineer roles. Include certifications only when they are genuine and relevant to the vacancy, using the exact official title. State the status clearly where necessary. An unfinished or unrelated course rarely deserves space unless it explains a useful skill or current training route.