Examples & writing guide
Software engineer CV example and writing guide
Updated 2 July 2026
A strong software engineer CV connects technical work to useful results instead of reading like an inventory of tools. This guide explains how to organise your evidence, write a focused software engineer personal statement and turn development work into credible achievements.
Examples by experience level
Junior Software Engineer
TemplateBlue Horizon3 / 5
Why this works
This example turns a degree, internship and early-career role into credible evidence through specific delivery, testing and teamwork outcomes.
Continue writing your CVMid-level Software Engineer
TemplateNavy Atlas4 / 5
Why this works
This example connects hands-on delivery with measurable improvements to reliability, performance and team output.
Continue writing your CVSenior Software Engineer
TemplateTeal Signal2 / 5
Why this works
Shows technical leadership, delivery at scale and measurable improvements without losing sight of hands-on engineering.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Lead with recent education, placements, personal projects and the strongest transferable evidence. Be precise about the software you have built. | Lead with delivery scale, technical direction, leadership and measurable outcomes across applications, websites or systems. |
| Experience evidence | Use internships, university work, apprenticeships and personal projects where paid experience is limited. Explain your own contribution clearly. | Prioritise recent roles and show ownership across design, build, testing, implementation, maintenance and support. |
| Technical skills | Choose a focused set of languages, testing methods, databases and version-control skills that you can discuss confidently. | Show depth as well as range. Connect architecture and delivery choices to reliability, maintainability, team throughput or customer outcomes. |
| Collaboration | Give examples of contributing to code reviews, responding to feedback and working with classmates or delivery colleagues. | Show how you worked with product and UX colleagues, resolved competing requirements and guided engineers through delivery decisions. |
| Leadership | Evidence ownership of a feature, project task or technical problem without overstating authority. | Describe mentoring or supervision only where it formed part of the role, including the scope of the team or solution element and the result. |
How to write a software engineer CV
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.
| Section | What to include |
|---|---|
| Personal statement | Your level, technical focus and one or two results that fit the vacancy |
| Technical skills | Languages, databases, tools and methods you have used in practice |
| Experience | Recent roles first, supported by scope, actions and outcomes |
| Education | Qualification, institution, dates and selected relevant detail |
| Extras | Projects, open-source contributions or publications that add fresh evidence |
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.
Personal statement examples
Software engineer with four years' experience building and maintaining customer-facing web applications in collaborative product teams. Delivered a checkout redesign that cut median response time by 32%, while contributing tested TypeScript services, REST APIs and SQL changes from design through support. Colleagues rely on my careful code reviews and practical communication with product and UX teams.
Hard-working software engineer looking for an exciting new challenge. I am passionate about technology, work well alone or in a team and can learn any programming language quickly. I have excellent coding and problem-solving skills and would be an asset to your company.
Writing your experience
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.
| Before | After |
|---|---|
| Responsible for testing new features. | Added 86 unit tests around payment validation, raising module coverage from 61% to 84% and catching four regressions before release. |
| Worked on APIs for the mobile application. | Built three REST endpoints for account settings, reducing duplicate client requests by 28% in internal performance tests. |
| Helped fix production issues. | Diagnosed recurring authentication failures and shipped a retry fix that cut related support tickets from 34 to 9 per month. |
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.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
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.
Common mistakes to avoid
AvoidSending the same software engineer CV for every vacancy, with no change to the personal statement, skills order or project evidence.
InsteadTailor each version to the application. Bring the most relevant languages, methods and achievements forward, and mirror accurate wording from the advert where it describes experience you genuinely have.
AvoidWriting experience bullets as a list of routine duties, such as "wrote code" or "fixed bugs".
InsteadFocus on accomplishments. State what you changed, the scope of the work and the result, using only figures you can defend.
AvoidListing technologies without showing where or how they were used.
InsteadConnect important skills to evidence in employment, placements or projects. Name the application, feature or system and explain your contribution.
AvoidConcentrating entirely on technical tools and giving no evidence of teamwork.
InsteadInclude concise examples of work with engineers, product managers or UX designers. Show how your contribution helped the team deliver a solution.
AvoidPacking the CV with every technical term you know in the hope of passing screening software.
InsteadUse relevant terms from the job advert only when they match your real experience. Keep them readable and support the strongest terms with evidence elsewhere in the CV.
Frequently asked questions
Usually one or two pages is enough. An entry-level candidate can often use one page, while an experienced engineer may need two to show recent work without squeezing the text or listing every old technology.
Use placements, coursework, personal projects, apprenticeships and volunteering as evidence. For each project, explain what you built, the tools you used, your individual contribution and a result you can verify.
No. A British-style CV does not normally include a photo or date of birth; use the space for relevant technical evidence and achievements.
Yes. Adjust the personal statement, skills order and selected evidence for each application, using terms from the advert only where they accurately describe your experience.
Put relevant projects and technical training near the top, then translate earlier work into useful evidence such as problem solving, delivery ownership and collaboration. Do not hide the career change; make the link between your previous experience and the software work clear.
From example to application
Turn this software engineer example into a CV that sounds like you.
Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.