Software Engineer CV Guide 2026: ATS-Friendly Examples

Here is a sobering fact: research by Jobscan found that over 70% of CVs are rejected by an applicant tracking system (ATS) before a single human reads them. In tech hiring, where competition is fierce and job boards receive hundreds of applications per role, even the most capable engineers get screened out, not because of their skills, but because of how their CV is formatted or written.

A strong software engineer CV is not just a list of technologies. It is a carefully structured document that speaks to both an ATS and a hiring manager. Get the format wrong, and your application never makes it to a recruiter's inbox. Get the content wrong, and it ends up in the bin.

This guide walks you through every section of a software engineer CV, from your personal statement to your projects. You will find concrete examples, before/after rewrites, and practical tips that apply whether you are writing a graduate software engineer CV with no work history or updating an existing CV as an experienced developer. Let's get into it.

---

What should a software engineer CV include?

A well-structured software engineer CV covers these core sections:

1. Contact details, Full name, phone number, professional email address, LinkedIn URL, and optionally a GitHub link.
2. Personal statement, A 3-4 line summary of who you are, what you build, and what kind of role you are targeting.
3. Technical skills, Organised by category: languages, frameworks, databases, cloud and DevOps tools.
4. Work experience, Roles listed in reverse-chronological order, with bullet points showing what you built and the measurable results.
5. Projects, Personal builds, university coursework, hackathons, or open-source contributions that demonstrate practical ability.
6. Education, Degree, university, graduation year, and classification. Include relevant modules if you are a graduate.
7. Certifications (optional), AWS, Azure, Google Cloud, or other relevant professional certifications, listed either under education or in a separate section.

This structure works for the vast majority of software engineering roles. Keep it in this order, use standard section headings, and you will avoid most of the pitfalls that trip up otherwise strong candidates.

---

Software engineer CV format: what works in 2026

Reverse-chronological vs. hybrid

For developers with three or more years of experience, a reverse-chronological format is the standard. Your most recent and relevant roles appear first, which is exactly what recruiters and hiring managers expect to see.

If you are a graduate or career changer with limited formal work history, a hybrid format works better. This places a skills or projects section near the top, before a shorter work experience section. It lets you lead with your technical ability rather than a thin employment history.

One page vs. two

Under three years of experience: one page. No exceptions. If you find yourself squeezing the font down to 9pt to fit everything in, you are including too much. Cut it.

For senior roles or those with more than five years of experience, two pages is fine. Three pages is almost never necessary. Recruiters spend an average of seven seconds on a first pass, so every line needs to earn its place.

File format

Always export your CV as a PDF. PDFs preserve your formatting across different operating systems and devices. Word documents can render differently depending on the version of Word the recipient is using. AlignCV lets you export as PDF or DOCX in one click, so you always have both options ready.

ATS-safe design rules

This is where a lot of CVs silently fail. Modern ATS software parses the text of your document. Anything that interferes with that parsing can cause your CV to be misread or rejected entirely. Follow these rules:

• No tables, columns, or text boxes
• No graphics, icons, or images (including headshots)
• Standard fonts only: Arial, Calibri, or Georgia
• No headers or footers for key information (some ATS ignore these entirely)
• Standard section headings: "Work Experience" not "Where I've Worked"

AlignCV's free CV templates are built to pass ATS scanners by design. Every template uses clean, single-column layouts with standard formatting so you never have to guess whether your CV will parse correctly.

---

How to write your software engineer personal statement

Your personal statement sits at the top of your CV, directly below your contact details. It is the first thing a recruiter reads. Most personal statements are either too vague ("passionate developer with a love of technology") or too long (six lines of dense prose). Neither works.

The 3-sentence formula

A strong personal statement answers three questions:

1. Who are you? (Your role, level, and primary area of expertise)
2. What do you do? (Your key technical strengths or the type of work you do best)
3. What are you looking for? (The type of role or environment you are targeting)

Keep it to 3-4 lines. Use the first person implicitly (start with "Software engineer with..." rather than "I am a software engineer who..."). No clichés.

Mini-story: Jamie's before and after

Jamie just graduated with a 2:1 in Computer Science from the University of Manchester. Their first draft personal statement read:

I am a hard-working team player with a passion for coding. I have experience in many programming languages and enjoy solving problems. I am looking for an opportunity to grow.

This says nothing useful. It could apply to any graduate in any field. Here is the rewritten version:

Computer Science graduate (2:1, University of Manchester) specialising in backend development with Python and Django. Built three full-stack projects during my degree, including a real-time collaborative task manager with 200+ active users. Seeking a junior backend engineering role where I can contribute to production systems from day one.

Same person. Completely different impression. The second version is specific, confident, and immediately tells the recruiter what Jamie can do.

For more examples and a full framework, see the guide on how to write a CV personal statement.

---

Technical skills section: what to include (and what to leave out)

The technical skills section is one of the most important parts of a software engineer CV. Recruiters scan it to confirm you have the technologies the role requires. ATS software scans it for keyword matches. Both audiences need to find what they are looking for quickly.

Organise by category

A flat list of 25 technologies in no particular order is hard to read. Group your skills instead:

• Languages: Python, TypeScript, Go
• Frameworks: Django, React, FastAPI
• Databases: PostgreSQL, Redis, MongoDB
• Cloud and DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, GitHub Actions
• Tools: VS Code, Jira, Figma, GitHub Copilot, Cursor

The 2026 angle: AI coding tools

AI tools are increasingly expected in software engineering roles. Listing GitHub Copilot or Cursor under your Tools section is a small signal that you are working the way modern engineering teams work. According to the GitHub Octoverse report, the majority of developers now use AI coding assistants regularly. If you use them, include them.

The golden rule

Only list skills you can talk about confidently in an interview. If you put "Kubernetes" on your CV and cannot explain the difference between a pod and a deployment, a technical interviewer will find out. Stick to what you actually know.

Matching to the job description

Before you send your CV anywhere, read the job description carefully. Note every technology and tool mentioned. If you have experience with it, make sure it appears in your skills section. This is not padding. It is how ATS keyword matching works, and it is how recruiters confirm you are a fit.

---

Work experience: writing bullet points that actually get read

Most work experience bullet points on software engineer CVs are passive, vague, and interchangeable. "Worked on the backend." "Helped with deployments." "Involved in the development of..." These tell a recruiter almost nothing.

The formula

Every bullet point should follow this structure:

Action verb + what you built or did + measurable result

"Reduced average API response time from 850ms to 120ms by refactoring database queries and introducing Redis caching, improving user retention by 12%."

That is one sentence. It tells you what was done, how it was done, and what happened because of it.

How to quantify your work

Numbers are not always obvious in software engineering, but they are almost always findable. Consider:

• Latency or load time improvements (before and after)
• Number of users or requests served
• Test coverage percentage (before and after your work)
• Deployment frequency improvements
• Bug reduction rates
• Time saved through automation

If you genuinely cannot quantify something, describe the scope: "Built a REST API consumed by three internal services" is better than "Built a REST API."

Mini-story: Priya's bullet point rewrite

Priya had a placement year at a fintech startup. Her original CV listed this under her experience:

Responsible for building a login page using React.

She was not getting callbacks. After working through her bullet points properly, it became:

Built a secure OAuth 2.0 authentication flow in React and Node.js, reducing login errors by 40% and supporting integration with three third-party identity providers.

Within two weeks of updating her CV with rewritten bullet points like this, she had four interview invitations. The experience was the same. The presentation was completely different.

What if you have no formal experience?

Writing a software engineer CV with no experience is more achievable than most graduates think. If you have no professional work history, your projects section does the same job as work experience. Write your project bullet points using exactly the same formula: action verb, what you built, measurable outcome. See the next section for how to do this well. You might also find the guide on writing a CV with no experience useful.

---

Projects section: how to make your work count

For many graduates and junior developers, the projects section is the most important part of the CV. It is where you prove you can actually build things, independent of a formal job.

What belongs here

Include:

• Personal side projects (especially if deployed and in use)
• University coursework projects (final year projects in particular)
• Hackathon submissions
• Open-source contributions (even small ones, if meaningful)

Do not include projects you barely started, or projects where your contribution was minimal and you cannot explain the technical decisions made.

Describing a project in three bullet points

For each project, aim for three bullet points that answer:

1. What problem did it solve, or what was the goal?
2. What did you build, and with what technologies?
3. What was the outcome?

Weak version:

TaskFlow, a task management app

• Used React and Node.js
• Added features like task creation and user login

Strong version:

TaskFlow, real-time collaborative task manager

• Built to address the lack of simple, free team task tools for student project groups
• Developed with React, Node.js, Socket.io, and PostgreSQL; deployed on Heroku with CI via GitHub Actions
• Reached 200+ active users within six weeks of launch; maintained 99.4% uptime over three months

The second version tells a story. It shows technical range, initiative, and results.

Should you link to GitHub?

Yes, if your GitHub profile is active and reasonably tidy. A profile with pinned repositories, readable README files, and recent commit activity signals that you are a practising developer. Keep the URL short. Link to the specific repository where it is relevant, not just your profile.

If your GitHub is sparse or full of incomplete tutorials, either tidy it up before applying or leave the link off. A bad GitHub link can actively hurt your application.

---

Education section: keeping it relevant

The education section is straightforward, but there are a few things worth knowing.

What to include

• Degree title and subject
• University name
• Graduation year (or expected graduation year)
• Degree classification (e.g., First Class, 2:1, 2:2)

For example: BSc Computer Science, University of Leeds, 2024, 2:1

Relevant modules

If you are a recent graduate with limited work experience, listing relevant modules adds substance to your education section. Good examples: Data Structures and Algorithms, Distributed Systems, Machine Learning, Software Engineering Principles, Databases. Skip modules that are not relevant to the role you are applying for.

Certifications

If you have AWS, Azure, Google Cloud, or similar certifications, you have two options: list them under education (if you have no other section for them) or create a short standalone "Certifications" section below education. Either is fine. What matters is that they are visible and dated.

Bootcamp graduates

If you completed a coding bootcamp, list it with the same confidence as a degree. Include the name of the bootcamp, the programme (e.g., "Full Stack Web Development"), and the year you completed it. Bootcamp graduates are hired into engineering roles every day. Do not undersell it. You can also check out Prospects.ac.uk for guidance on how UK employers view alternative qualifications.

---

Making your software engineer CV ATS-friendly

ATS (Applicant Tracking System) software is used by the majority of UK employers to filter applications before a recruiter sees them. Understanding what ATS actually checks helps you make better decisions about how to write and format your CV.

What ATS checks

• Keywords: Does your CV contain the terms from the job description?
• Section headings: Are they standard and recognisable?
• File format: Is it a PDF or DOCX? (Both are usually fine, but check the job posting.)
• Readable structure: Can the parser extract text cleanly, without hitting tables or images?

Extracting keywords from a job description

Read the job description carefully and note the specific technologies, tools, and phrases used. If the job says "experience with containerisation" and you have Docker experience, your CV should mention Docker explicitly, not just "containerisation." ATS matches on exact and near-exact terms.

Copy the most important terms into your skills section and work experience bullet points. Do not stuff keywords unnaturally. Just make sure the terms appear where they are genuinely relevant.

Common ATS killers

Avoid these on your software engineer CV:

• Tables, ATS parsers often misread or skip table content entirely
• Columns, A two-column layout can be parsed left-to-right across both columns, making your CV read as nonsense
• Text boxes, Content inside text boxes is frequently invisible to parsers
• Images, ATS cannot read text inside images
• Non-standard fonts, Stick to Arial, Calibri, or Georgia
• Headers and footers, Key contact details in headers or footers may be ignored

AlignCV's ATS Score Checker (Pro plan) scans your CV against a specific job description and flags keyword gaps, formatting issues, and anything that could cause an ATS to misread your application. It is worth running before you send anything out.

For a deeper dive into this topic, the ATS CV guide covers the full range of optimisation steps you can take.

For students and recent graduates who are applying to their first engineering roles, the complete student CV guide also covers ATS basics alongside everything else you need to know.

---

Frequently asked questions

How do I write a software engineer CV with no experience?

Focus on your projects, university coursework, and any open-source contributions. Use the same action verb plus outcome formula you would use for work experience. A strong projects section can carry an entire CV for a junior role. See the full CV with no work history guide for a step-by-step walkthrough.

How long should a software engineer CV be?

If you have fewer than three years of professional experience, keep it to one page. For senior roles or those with five or more years of experience, two pages is appropriate. Three pages is rarely justified and signals poor editing. Every line should earn its place.

Should I include a GitHub link on my CV?

Yes, if your profile shows active and polished work. Pin your best repositories, write clear README files, and make sure recent activity is visible. If your profile is sparse or messy, tidy it up before linking to it. A weak GitHub link can do more harm than good.

What programming languages should I list on my CV?

Only list languages you can discuss confidently in a technical interview. Tailor the list to match the technologies mentioned in the job description. Putting every language you have ever touched in a tutorial wastes space and risks embarrassment in an interview.

How do I make my software engineer CV ATS-friendly?

Use clean, single-column formatting with no tables, columns, or images. Stick to standard section headings. Extract keywords from the job description and use them naturally throughout your CV. Export as PDF. The ATS-friendly CV guide covers every step in detail.

---

Conclusion

A strong software engineer CV is not about listing every technology you have touched. It is about showing, clearly and concisely, what you have built, what it did, and that you can do it again in a new role.

Here are the five things to take away from this guide:

• Use a clean, ATS-safe format: single column, standard fonts, standard headings, no tables or images
• Write bullet points with the action verb plus result formula: every bullet should show what you did and what happened because of it
• Tailor your technical skills section to each job description, match the keywords the employer uses
• Lead with your projects if you are a graduate or career changer, they are proof of ability, even without formal experience
• Run your CV through an ATS checker before you apply so you know the issues before a recruiter does

Your projects, your coursework, your side builds: these are real evidence that you can engineer software. They just need the right presentation to be seen.

Ready to put it all together? Build your software engineer CV with AlignCV, it is free, every template is ATS-ready, and you can export your finished CV as a PDF in minutes. Browse professionally designed templates and get started today.