Examples & writing guide
Computer Science CV Example for 2026
Updated 24 July 2026
A strong computer science CV connects technical knowledge with evidence that your work solved a problem or improved a result. This guide shows how to shape that evidence, whether you are applying after university, moving from another field or bringing several years of experience.
Examples by experience level
Graduate Computer Science CV
TemplateTeal Signal2 / 5
Why this works
This example turns limited commercial experience into credible evidence through focused technical skills, a placement, relevant projects and specific outcomes.
Continue writing your CVMid-level Software Developer
TemplateNavy Atlas4 / 5
Why this works
This computer science CV sample pairs a focused technical profile with measurable delivery results, relevant projects and a clear record of growing responsibility.
Continue writing your CVSenior Software Engineering Lead
TemplateAshford1 / 5
Why this works
This example shows technical depth, leadership across several teams and defensible measures of delivery, reliability and performance.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Lead with the target discipline, recent education and one or two relevant projects. Make the direction specific, such as software development, data analysis or cyber security. | Lead with technical scope, leadership and outcomes delivered across products, systems or teams. Name the specialism without turning the computer science personal statement into a long tool list. |
| Experience and projects | Give academic, personal or placement projects enough detail to prove your contribution. Separate your work from the team's work and include only figures that you can defend. | Prioritise recent roles that show ownership, scale and sustained results. Compress older or less relevant work so major technical and organisational decisions remain visible. |
| Technical skills | List the programming languages, tools and operating systems used in completed work, then use project bullets to show how you applied them. | Group skills around the advertised role and established expertise. Emphasise technologies used to design, develop, test, maintain or improve substantial systems. |
| Results | Use modest, verifiable measures such as tests written, faults resolved, data records analysed or project delivery dates met. | Use measures that show broader effect, such as performance changes, reliability, delivery time, service volume or team output. Give enough context for the reader to understand each figure. |
| Communication and professional practice | Show how you explained technical work through presentations, documentation, group projects or support interactions. | Show communication through technical direction, stakeholder advice, written standards or decisions that connected user needs with implementation. |
| CV emphasis | Education and relevant projects can appear before limited employment, particularly on a graduate computer science CV. | Recent experience normally deserves more space than education. Keep qualifications concise unless they directly support the post. |
How to write a computer science CV
Use a clear, reverse-chronological layout with familiar section headings and simple formatting. One or two pages will suit most candidates: use one page when you are early in your career and have enough space to show relevant evidence; use two when substantial employment, research or project detail earns the extra room. Avoid columns, text boxes and decorative graphics that may make the document harder to read or process.
| Section | What to include |
|---|---|
| Contact details | Name, UK location, mobile, email and a relevant portfolio or repository link |
| Personal statement | Target role, strongest evidence and the kind of problem you can help solve |
| Technical skills | Relevant programming languages, frameworks and tools, grouped so they are easy to scan |
| Experience and projects | Recent work first, with your contribution, technical approach and measurable outcome |
| Education | Qualification, institution, dates and selected modules or project detail when relevant |
| Extras | Relevant certifications, publications, volunteering or technical interests only |
Tailor the document to the vacancy rather than relying on a generic computer science CV template. Mirror accurate wording from the job description where it matches your experience, but keep the prose natural. Your computer science personal statement should be brief and specific; it is an introduction, not a condensed cover letter.
Give experience the most space once you have relevant employment. For a graduate computer science CV, education and projects can appear before limited work history. Describe coursework as evidence only when it shows something useful, such as a substantial build, investigation or team contribution. List technical skills you could discuss confidently in an interview, and remove unrelated tools that dilute the match.
Projects deserve proper context. State what you built, the problem it addressed, your individual contribution and the result. Add a link only when the work is accessible, presentable and safe to share. Education entries should stay concise once professional experience carries more weight. Extras can help when they add fresh evidence, but they should never crowd out stronger technical work.
Personal statement examples
Computer science graduate targeting junior software development roles, with project experience designing, testing and improving web applications. Built a final-year service that reduced average query time from 1.8 seconds to 0.7 seconds in controlled tests, and documented the design choices for both technical and non-technical readers. Brings practical Linux experience, careful problem solving and a habit of measuring changes before claiming improvement.
Hard-working computer science graduate looking for an exciting role at a good company. I know lots of technology, work well alone or in a team and am passionate about computers. I am a fast learner who can do any task required.
Writing your experience
Computer science CV examples are most useful when their bullets show a chain of cause and effect. Start with the action you took, add enough technical scope to make the work understandable, then finish with a result. The result might concern response time, fault volume, test coverage, processing time, user completion or delivery speed. Use only figures you recorded and can defend; if no reliable metric exists, describe a specific, observable outcome without inventing one.
A useful pattern is: action + technical scope + measured result. Keep the action yours. If a team delivered the result, say which component, investigation or decision you owned.
| Before | After |
|---|---|
| Worked on a web application | Built and tested three server-side endpoints for a booking application, cutting median response time from 620 ms to 390 ms in load tests |
| Helped fix support issues | Diagnosed 27 recurring account faults from ticket records and wrote a troubleshooting guide that reduced repeat escalations by 18% over eight weeks |
| Completed a data project | Cleaned and analysed 48,000 anonymised records, identifying four recurring error patterns used to revise the validation rules |
The improved versions work because they state the scope, method and outcome. They also avoid vague claims such as "improved performance" when the candidate can name the test or comparison behind that claim.
Choose verbs that describe the work precisely: built, designed, developed, tested, debugged, analysed, automated, refactored, configured, documented, deployed, investigated and resolved. "Led" belongs only where you genuinely directed people or decisions. "Collaborated" is useful when followed by the parties involved and the concrete output; on its own, it says little.
For software work, show how you designed, developed or tested an application around user needs. A full stack example can distinguish front-end interface work from server-side logic. For data work, explain what you interpreted and how the finding informed a decision. For support work, include the request volume, tracking method, diagnosis or routing outcome where those details are relevant. If your evidence centres on broader engineering work, the engineering CV guide may be a closer fit.
Projects can follow the same method as employment. Name the problem, your contribution, the technical choices and the evidence produced by testing. A repository link can support the bullet, but it does not replace a clear explanation in the CV. Keep each bullet to one or two lines where possible and place the strongest, most relevant result first.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
Education carries more weight on a computer science CV when you have limited professional experience. Give the qualification title, institution and dates, then add selected modules, a dissertation or a substantial project only when they support the target role. A graduate can include two or three concise project bullets with technical scope and measured results. An experienced candidate can usually shorten the entry because recent work provides stronger evidence.
Do not imply that one degree, school qualification or certification is universally required for computer science employment. The supplied qualification evidence concerns entry to one undergraduate programme, not the wider profession. For standard entry to the University of Edinburgh Computer Science undergraduate programme, GCSE English at C or 4 is required. Within that programme's English-language entry requirements, SQA National 5 English at C or higher, GCSE English at C or 4 or higher, Level 2 Certificate English at C or higher, and International Baccalaureate (IB) Standard Level English at 5 or higher are accepted routes. International Baccalaureate (IB) English ab initio is not accepted for entry to that programme. These details belong on a CV only when relevant to the candidate's education and application.
Certifications should be listed when they are relevant and genuine. Give the exact credential name, issuing body and completion date; include an expiry date only when the credential has one. No named professional certification is supported by the supplied evidence, so this guide does not recommend one. Instead, compare each vacancy with your own verified training and include only the credentials that strengthen that application.
Keep short courses separate from formal education if that makes the hierarchy clearer. Avoid turning the section into a catalogue of every online lesson completed. A well-described project, including what you built and how you tested it, often gives the reader more useful evidence than a long list of course titles.
Common mistakes to avoid
AvoidUsing a generic computer science CV template that gives equal space to every module, part-time job and technical interest.
InsteadAdapt the structure to the vacancy. Bring the most relevant technical skills, projects and results near the top, and cut material that does not help the reader assess you for that particular computer science role.
AvoidListing programming languages, frameworks and tools without showing where they were used.
InsteadConnect each important technology to a project or role. State what you built, tested or improved, then give the outcome where you have a figure you can defend.
AvoidDescribing project activity without a measurable result, such as "worked on an application" or "helped with testing".
InsteadWrite bullets around your contribution and its effect. Suitable evidence might include test coverage, response time, fault volume, users supported or delivery time, but include only measurements drawn from your own records.
AvoidLeaving relevant academic, personal or collaborative projects off a graduate computer science CV because they were not paid work.
InsteadUse a clearly labelled projects section when it supplies stronger technical evidence than unrelated employment. Explain the problem, your contribution, the technology and the verified outcome.
AvoidAdding every skill ever encountered, including irrelevant software and unsupported proficiency claims.
InsteadKeep the skills section selective. Match it to the role and back the strongest entries with evidence elsewhere in the CV.
AvoidUsing columns, graphics or decorative rating bars that make the document difficult to parse or scan.
InsteadChoose a simple ATS-friendly layout with conventional headings, readable text and a clear reverse-chronological history. Describe proficiency through evidence rather than a visual score.
Frequently asked questions
For most applicants, one or two pages is sensible. A graduate computer science CV can often fit on one page, while an experienced candidate may need two to show relevant scope and results without crowding the layout.
Use relevant coursework, academic projects, personal builds, volunteering and transferable employment. For each project, explain the problem, your contribution, the technology used and any result you can verify. A repository or portfolio link can give the reader direct access to your work.
No. Under British CV conventions, leave out the photo and date of birth. Use the space for technical evidence, project outcomes and concise contact details instead.
No. Include languages that relate to the vacancy and that you can discuss confidently. Evidence from a completed project or role is more useful than a long, unqualified inventory.
A certifications section is optional. If you use one, record only accurate details that are relevant to the vacancy, and keep the section shorter than your work and project evidence.
Translate previous work into evidence that matters to the target role, such as problem solving, data analysis, fault diagnosis, documentation or explaining technical issues. Pair that evidence with recent, relevant projects so your computer science CV sample shows practical direction rather than relying on a career-change claim alone.
From example to application
Turn this computer science 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.