Software Engineer CV Example & Template (2026)

A well‑written CV is the first conversation you have with a hiring manager. For software engineers, recruiters look for a clear picture of technical ability, problem‑solving track record and collaborative style. This guide walks you through the layout they expect in 2026, explains what belongs in each part, offers a short annotated example, and highlights the most common mistakes to sidestep. All advice is grounded in honesty – you should never claim experience you don’t have.

1. The overall layout

Most tech recruiters scan dozens of CVs in a few minutes, so a clean, skimmable structure is essential. Stick to a single‑page format unless you have ten or more years of experience; then a two‑page CV is acceptable. Use a standard font (e.g., Calibri, Arial, or Helvetica) at 10–11 pt, and keep margins at 1 cm. Save the file as PDF with a clear name such as john-doe-software-engineer.pdf.

Typical order

1. Contact details
2. Professional summary (optional but useful)
3. Core technical skills
4. Professional experience
5. Education
6. Projects (if not covered in experience)
7. Certifications / awards (optional)

Each section should be separated by a horizontal line or a bold heading to aid visual scanning.

2. What belongs where

2.1 Contact details

Place your name, phone number, professional email address, and a link to your GitHub or personal portfolio at the top. A LinkedIn URL is also welcome. Avoid personal details such as marital status, date of birth, or a photograph – they are unnecessary and can lead to bias.

John Doe
+44 7700 123456 | john.doe@email.com
github.com/johndoe | linkedin.com/in/johndoe

2.2 Professional summary (2–3 lines)

A concise sentence or two that tells the recruiter your current role, years of experience, and the type of engineering you specialise in. Focus on the value you bring rather than a generic “hard‑working professional”.

Example: “Software Engineer with 4 years of experience building scalable backend services in Python and Go, specialising in micro‑service architecture and CI/CD pipelines.”

2.3 Core technical skills

List languages, frameworks, tools and platforms you are comfortable with. Group them by category and order them by relevance to the role you are applying for. Do not list every language you have ever touched; instead, include those you can use confidently in a production environment.

Languages: Python, Go, JavaScript (Node.js, TypeScript)  
Frameworks: Django, FastAPI, React, Express  
Cloud: AWS (ECS, RDS, S3), Terraform  
DevOps: Docker, GitHub Actions, Kubernetes  
Databases: PostgreSQL, Redis, MongoDB

2.4 Professional experience

This is the heart of your CV. For each role, include:

• Job title – be precise (e.g., “Backend Engineer”, “Full‑Stack Engineer”).
• Company name and location – include the city and country.
• Dates – month and year (e.g., Apr 2022 – Present).
• Key achievements – use bullet points; start each with an action verb and quantify impact where possible (e.g., “Reduced API latency by 30 %”).
• Technologies used – add a short bracketed list at the end of each bullet, e.g., “(Python, Docker, AWS)”.

Avoid long paragraphs; recruiters skim for outcomes, not responsibilities.

2.5 Education

List your highest qualifications first. Include degree, institution, location, and graduation year. If you have a strong GPA (≥ 3.5/4.0) you may note it, but it is not required for most software roles.

2.6 Projects (optional)

If you have notable side‑projects, open‑source contributions or university work that demonstrates relevant skills, include them here. Keep each entry to one or two lines, focusing on the problem solved, the technology stack, and any measurable result (e.g., “Open‑source library with 1 k+ weekly downloads”).

2.7 Certifications / awards

Only list certifications that are current and recognised (e.g., AWS Certified Solutions Architect). Awards such as “Hackathon winner – 2023” belong here if they add credibility.

3. Annotated example (≈ 150 words)

Below is a stripped‑down CV excerpt for a mid‑level engineer. Brackets indicate the purpose of each element.

John Doe
+44 7700 123456 | john.doe@email.com
github.com/johndoe | linkedin.com/in/johndoe

Software Engineer with 4 years of experience delivering high‑throughput backend services for e‑commerce platforms.

Languages: Python, Go, TypeScript
Frameworks: FastAPI, React, NestJS
Cloud: AWS (ECS, RDS), Terraform
DevOps: Docker, GitHub Actions, Kubernetes

Backend Engineer, ShopStream Ltd., London, UK
Apr 2022 – Present
• Designed and implemented a payment micro‑service handling £10 M+ monthly volume, cutting transaction latency from 250 ms to 170 ms (Python, FastAPI, AWS RDS).  
• Migrated legacy monolith to Kubernetes, reducing server costs by 22 % and enabling zero‑downtime deployments (Docker, Helm).  
• Introduced automated contract testing with Pact, decreasing integration bugs by 35 % (GitHub Actions).

BSc Computer Science, University of Manchester, Manchester, UK
Graduated 2021

Why it works: The summary tells the recruiter the candidate’s focus. Skills are grouped for rapid scanning. Each bullet ties an achievement to a tangible outcome and lists the relevant tools, allowing applicant‑tracking systems to pick up keywords.

4. Common mistakes and how to avoid them

Mistake	Why it hurts	Remedy
Including every language ever used	Dilutes the impact of core competencies; ATS may miss the most relevant keywords.	List only languages you can use confidently in production.
Writing responsibilities instead of achievements	Recruiters cannot gauge your contribution; “worked on X” is vague.	Convert duties into results (e.g., “Improved page load time by 20 %”).
Using a generic objective statement	Adds no value and occupies precious space.	Replace with a concise professional summary that highlights your niche.
Over‑loading the CV with jargon	Can obscure meaning and appear pretentious.	Stick to widely recognised terms; explain niche tools only if they are central to the role.
Leaving gaps in employment without explanation	May raise questions about continuity.	Briefly note a gap if you were studying, freelancing, or on a career break; otherwise, keep the timeline continuous.
Including unrelated hobbies or personal details	Distracts from core qualifications.	Remove anything that does not support the engineering narrative.
Formatting inconsistencies	Makes the document look unprofessional and hampers readability.	Use a single style for headings, dates, and bullet points; proofread carefully.
Submitting a PDF with a non‑standard filename	Recruiters may struggle to locate the file on a shared drive.	Name the file clearly, e.g., john-doe-software-engineer.pdf.

5. Tailoring for each application

Even a strong CV benefits from a small amount of customisation. Scan the job description for the top three technical requirements and ensure those keywords appear in your skills or experience sections. If the role emphasises “team leadership”, highlight any mentoring or code‑review responsibilities you have undertaken. This targeted approach signals that you have read the posting carefully and understand the role’s priorities.

6. Using Ryser to polish your CV

Ryser’s free AI‑driven tool can help you fine‑tune language, check for missing keywords, and keep the tone consistent across sections. By uploading your draft, you can see a side‑by‑side comparison of the original and the AI‑suggested version, making it easy to adopt improvements without losing your authentic voice. Give it a try to tailor your CV free and ensure every line works for you.

7. Final checklist

• One‑page PDF (two pages only if > 10 years experience)
• Clear contact details with professional links
• Concise summary that states role, experience level and specialisation
• Skills grouped and ordered by relevance
• Experience bullets focused on outcomes, quantified where possible, and tagged with technologies used
• No fabricated responsibilities or exaggerated dates
• Consistent formatting and a clean visual hierarchy
• File name follows the “firstname-lastname-role.pdf” convention

A disciplined, honest presentation of your software engineering journey will stand out in a crowded market. By following the structure outlined above, you give recruiters the information they need to move you to the interview stage – and you keep your integrity intact. Good luck!