Examples & writing guide
Developer CV examples
Updated 18 November 2026
Build your developer CV around a specific engineering contribution: UK software engineers integrate products and platforms, create technical specifications and write operational documentation with technical authors. Their work also includes testing hardware and software systems to diagnose and resolve faults; depending on the company and project, daily activities may include evaluating and testing new programs. These developer CV examples show Software Engineer applicants how to select evidence for a first role or a senior application, then explain how to adapt that evidence to their own history.
Examples by experience level
First Software Engineer role - Internship and volunteer project
TemplateAshford1 / 5
Why this works
Riley shows bounded contributions, a testing decision and a useful project handover; this profile, its employers, history and achievement figures are fictional and illustrative.
Continue writing your CVSenior Software Engineer - Integration and service ownership
TemplateTeal Signal2 / 5
Why this works
Jordan connects sustained engineering work with release decisions, stakeholder responsibility and team support; this profile, its employers, history and achievement figures are fictional and illustrative.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Opening evidence | Riley leads with an internship and volunteer booking project while seeking a first Software Engineer role. | Jordan leads with nine years of engineering experience and responsibility for integrations used by four operational teams. |
| Ownership | Riley builds a bounded import check and submits the internship fix for a supervising engineer's review. | Jordan agrees acceptance criteria, changes the migration approach after a trial and supports three engineers. |
| Results | Riley uses test findings and an observed coordinator handover to explain whether the work was useful. | Jordan connects a migration to a measured reduction in failed transfers and a recovery exercise completed by support. |
| Suggested emphasis | Bring Riley's volunteer project and relevant education forward, then use the internship to show supervised delivery. | Bring Jordan's recent employment forward and keep education shorter so release decisions and sustained contributions have space. |
| Documentation | Riley drafts a field-mapping specification and revises a small operating guide after observing users. | Jordan works with a technical author on recovery instructions and tests the handover with support colleagues. |
How to write a developer CV
Choose evidence against the target advert before choosing a developer CV format. Check the application's instructions and use the shortest readable length that covers your relevant contributions; give a useful explanation space rather than shrinking the text to meet an arbitrary page target.
Use clear headings and consistent dates and spacing. Keep experience and education in reverse-chronological order. For these examples, Riley could bring the volunteer project forward, while Jordan could lead with recent employment. Start with your name and contact details, then arrange the remaining sections around your strongest evidence.
| Section | What to put first |
|---|---|
| Personal statement | Your relevant background and one concrete contribution, when useful |
| Experience or projects | Work that best demonstrates your contribution and its result |
| Skills | Capabilities connected to examples elsewhere in the CV |
| Education | Accurate study details and relevant project learning |
| Extras | Material that adds evidence rather than repeats it |
For UK CVs prepared for ATS screening, Careers Wales recommends a simple format with standard headings and advises avoiding tables because software might not understand them. It also recommends advert keywords in skills, experience and the personal statement only where you can demonstrate the corresponding capabilities. These are presentation recommendations, not guarantees about every system; the table above is a planning aid for this guide.
Personal statement examples
A personal statement is optional on a UK CV; University of Edinburgh Careers Service recommends leaving it out when it adds nothing. If you include one, use a short account of relevant experience, a concrete contribution and the work you seek. Entry example, Riley Sample: Computer science graduate seeking a first Software Engineer role, with a development internship and a volunteer booking project. Built an import check that caught duplicate bookings before upload and documented the process so two volunteer coordinators could run it independently. Senior example, Jordan Sample: Senior Software Engineer with nine years of software engineering experience, including responsibility for integrations used by four operational teams. Led a staged platform migration that reduced failed transfers from 36 to 8 per month, while agreeing release decisions with operations and supporting three engineers. Each developer personal statement draws on its fictional CV. Riley names a bounded contribution; Jordan adds sustained experience and wider responsibility.
Hard-working and passionate developer with excellent technical skills. A reliable team player who enjoys challenges and wants an exciting opportunity to make a difference. This could describe either candidate without explaining what either has done. Replace the adjectives with a contribution you can discuss, and keep the scope consistent with your experience.
Writing your experience
Give each entry a title, organisation or project name, and dates. Then describe enough of the problem for your action to make sense. A reader should be able to separate what you personally changed from what colleagues approved, delivered or supported.
The following before-and-after pairs reuse the fictional CVs. They illustrate writing choices, not figures to copy into your own application.
- Before: "Worked on an integration." After: "Mapped conflicting customer identifiers between scheduling and billing applications and added a reconciliation report so finance staff could resolve exceptions before invoicing." The revised version identifies the incompatibility, Jordan's method and the practical outcome.
- Before: "Helped with testing." After: "Created 18 booking-import test cases, found an error in cancellation handling and corrected it before volunteer coordinators used the check." Riley's contribution has a clear boundary. The count explains coverage, while the corrected behaviour supplies the result.
- Before: "Updated documentation." After: "Worked with a technical author to rewrite recovery instructions around observed failure cases; the support team completed the next recovery exercise without engineering intervention." This preserves the collaboration and explains how the team checked whether the instructions worked.
Use verbs that describe your actual action: integrated, mapped, reproduced, diagnosed, tested, corrected, specified, documented or reviewed. Choose "supported" or "drafted" when that better reflects your ownership. A project contribution can be substantial without implying that you led the whole delivery.
For measurements, explain the comparison. Jordan's transfer result uses equal three-month periods before and after migration. If your records cannot support that precision, describe a defensible qualitative outcome, such as a successful handover or a fault reproduced and corrected. Keep testing examples tied to the systems and projects you actually worked on.
Key skills & ATS keywords
Hard skills
ATS keywords
Education & certifications
The Complete University Guide describes a bachelor's degree in software engineering or computer science as the usual minimum qualification for a UK software engineering career. It also recognises apprenticeships and self-teaching as alternative routes without a degree. This is a description of entry routes, not a universal degree requirement.
List relevant qualifications with their exact titles, providers and dates. Make clear which courses you have completed and which are still in progress, and only list awards you have received. For a first application, give a relevant project a little space: explain what you built or tested and what you learned. If you have several years of experience, keep older study brief so your recent contributions have room.
When applying for UK software engineering work, you can use project programming experience as evidence of continuing professional development. Prospects says this experience demonstrates technical ability and effective problem-solving skills. Describe a decision you made or an error you corrected, rather than just listing lessons completed. Riley's fictional booking project shows how to explain that work.
If you hold a relevant certification or have completed useful training, give its exact title, provider and completion date. Keep planned learning separate from completed achievements. Include the details that help explain your suitability for this application.
Common mistakes to avoid
AvoidDescribing integration work without explaining the incompatibility.
InsteadName the conflicting behaviour or data, explain your change and describe how you checked the result.
AvoidListing technical skills that the experience section never demonstrates.
InsteadConnect each prominent capability to a specific contribution. Check that your personal statement, skills and experience describe the same level of ownership.
AvoidPresenting a team migration as an individual achievement.
InsteadSeparate your implementation, review or release decision from the team's overall result. Keep approvals and supervision visible where they matter.
AvoidKeeping every old task in an updated developer CV.
InsteadFor UK CVs, select the information most relevant to the job. Give space to useful engineering evidence and remove detail that adds little to this application.
AvoidUsing dates or results that conflict across sections.
InsteadCheck project and employment dates together, and confirm that repeated figures use the same comparison period and describe the same outcome.
AvoidLeaving spelling errors or unclear technical shorthand in the final draft.
InsteadFor a UK CV, read the text aloud, correct spelling and grammar, and ask another person to check it. Spell out wording that a reader outside your project could misunderstand.
Frequently asked questions
Use relevant projects, internships, volunteering or supporting work, as Riley does. Give each contribution a clear context and date, and explain what you personally built, tested or corrected.
Use the shortest readable version that explains your relevant evidence. Check the target application's instructions, then remove repetition before cutting useful explanations or shrinking the text.
Use Jordan's example to plan space for sustained contributions, decisions and wider responsibility that you actually held. Explain how your work affected a service or team, while keeping your personal contribution clear.
Use the developer CV sample as a structure, then replace its fictional history and achievements with your own. Check that the finished document tells one consistent story across dates, skills and results.
Check the target application's instructions before deciding what to include or upload. Choose a readable presentation and inspect the final file for missing text or awkward page breaks.
From example to application
Turn this developer 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.