Software Engineer CV Example
Updated 2 July 2026
A strong software engineer CV proves you can build things that work. Whether you're a graduate with standout projects or a senior engineer with production systems under your belt, your CV needs to show what you built, the tools you used, and the measurable impact. This guide walks you through writing a software engineer CV that passes ATS screening and gets you to the technical interview.
Software Engineer CV examples
Graduate Software Engineer
entryLeads with strong projects and quantified outcomes to compensate for limited commercial experience.
Software Engineer
midBalances commercial experience with a standout personal project, showing both delivery and initiative.
Senior Software Engineer
seniorDemonstrates leadership, architectural decisions, and business impact at scale with concrete metrics.
How to write a software engineer CV
CV structure and length
Keep your software engineer CV to two pages. Put your name and contact details at the top, followed by a short personal statement, then technical skills organised by category, work experience in reverse-chronological order, education, and finally any relevant projects or achievements.
Header and contact details
Include your GitHub and portfolio URLs in the header alongside your email, mobile and LinkedIn. For a software engineer these links are evidence of real coding ability, and hiring managers actively look for a public GitHub or portfolio presence.
Personal statement
Write a sharp professional summary that states what kind of engineer you are, what you build, and the value you deliver. Name the stack and the focus area, not just "passionate developer." Example: "Backend Software Engineer with 5+ years building Java/Spring microservices on AWS, focused on reliability, observability and performance."
Technical skills
Organise your technical skills by category: Programming Languages, Frameworks/Libraries, Databases, Cloud Platforms, DevOps Tools, Version Control. This lets recruiters and ATS systems match your stack to job requirements at a glance. Cap the list at 10-12 genuinely proficient technologies and order them by proficiency or relevance to the job. Don't keyword-dump every tool you've touched.
Work experience
For each role, write 3-4 achievement bullets using the formula: action verb + what you built + specific tools/skills + metric. Lead with strong engineering verbs like developed, built, shipped, designed, architected. Spell out your individual contribution and its measurable result.
Projects
Calibrate the Projects section by seniority: juniors should give projects substantial space to prove technical capability, while engineers with 2+ years should include only one standout project and let work experience carry the CV. Always link to the source-code repository as well as a live demo.
Education and certifications
List your degree, institution, dates and classification. Skip online certifications and self-rated skill scores from certification sites, for software engineers, demonstrated projects and shipped work carry far more weight than course-completion badges.
Personal statement examples
Full-stack Software Engineer with 3 years building scalable web applications in Python and JavaScript. Experienced in designing RESTful APIs, optimising database performance, and deploying microservices to AWS. Focused on writing maintainable code and delivering features that improve user experience and business metrics.
Passionate and hard-working software developer looking for a challenging role where I can use my skills and grow. I have experience with many programming languages and frameworks and am a quick learner who works well in a team.
Writing your experience
The result-plus-metric pattern
Every bullet should follow the formula: action verb + what you built + specific tools/skills + metric. This proves you shipped real code with real impact.
Useful engineering quantifiers: performance gains (latency, throughput), downtime/error reductions, revenue impact of shipped features, test/code-coverage improvements, and team velocity (release cadence) improvements.
Before and after examples
| Weak | Strong |
|---|---|
| Responsible for developing new features and fixing bugs in the codebase. | Built a customer feedback dashboard using React and Node.js, reducing manual report generation time by 12 hours per week for the support team. |
| Worked on improving application performance and database queries. | Optimised PostgreSQL queries and introduced Redis caching, reducing average API response time from 340ms to 98ms for 10,000+ daily requests. |
| Helped the team migrate to Kubernetes and set up CI/CD pipelines. | Led migration of three legacy monoliths to Docker containers deployed on AWS ECS, reducing deployment errors by 88% and accelerating release cycles by 4 days. |
Claim your contribution
A hiring manager's top complaint: engineers describe features as a team effort without claiming their share. "You helped build, test, and deploy that feature, so tell me how much of a good job YOU did." Spell out your individual contribution and its measurable result, whose time the software saved and how much.
Action verbs for engineers
Lead with verbs that show ownership of the build-test-deploy lifecycle: developed, built, created, delivered, shipped, designed, architected, oversaw, managed, led. They read as ownership rather than passive participation.
Mirror the job description
Mirror the exact languages and technologies named in the job description into your CV to pass ATS screening. If the posting says API development, surface a matching bullet like "Designed and implemented a RESTful API for a third-party payment gateway, cutting transaction processing time by 22%."
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
Education
List your degree, institution, dates and classification in reverse-chronological order. If you achieved a First or 2:1, include it. For a final-year project that demonstrates technical ability, add a one-line note describing what you built and the outcome.
Graduates with limited commercial experience should lean on education and projects to prove coding ability. Engineers with 2+ years of experience can keep the education section brief and let work experience carry the CV.
Certifications
Skip online certifications and self-rated skill scores from certification sites, a hiring manager calls them "meaningless." For software engineers, demonstrated projects and shipped work carry far more weight than course-completion badges.
The exception: vendor certifications like AWS Certified Solutions Architect or Google Cloud Professional can signal genuine platform expertise, especially for cloud-focused roles. List these in an Achievements section with the issuer and year.
Spelling out abbreviations
Spell out common tech abbreviations at least once, Amazon Web Services (AWS), Google Cloud Platform (GCP), Continuous Integration/Continuous Deployment (CI/CD), so ATS keyword matching catches both the acronym and the full term recruiters may search.
Common mistakes to avoid
Listing every technology you've ever touched in a flat, unstructured skills list.
Organise skills by category (Programming Languages, Frameworks, Databases, Cloud Platforms, DevOps Tools) and cap the list at 10-12 genuinely proficient technologies. Order them by proficiency or relevance to the job.
Describing team features without claiming your individual contribution.
Spell out what YOU built and the measurable result. Example: "Developed a customer onboarding portal in React and Node.js, reducing manual onboarding time by 18 hours per week for the operations team."
Writing vague bullets like "Responsible for developing new features and fixing bugs."
Use the formula: action verb + what you built + specific tools/skills + metric. Example: "Built a real-time fraud-detection microservice in Java and Spring Boot, processing 2.4 million transactions daily and reducing fraudulent payments by 34%."
Omitting GitHub and portfolio links from the CV header.
Put GitHub and portfolio URLs in the header alongside contact details. For a software engineer these links are evidence of real coding ability, and hiring managers actively look for them.
Padding the CV with online course certificates and self-rated skill scores.
Skip certification badges from online learning platforms. For software engineers, demonstrated projects and shipped work carry far more weight. The exception: vendor certifications like AWS Certified Solutions Architect.
Giving projects equal weight regardless of experience level.
Juniors should give projects substantial space to prove technical capability. Engineers with 2+ years should include only one standout project and let work experience carry the CV.
Junior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Leads with education, projects and eagerness to learn. Example: "Recent Computer Science graduate with hands-on experience building full-stack web applications." | Leads with years of experience, technical specialism and leadership. Example: "Senior Backend Software Engineer with 7 years building Java microservices on AWS, focused on reliability and performance." |
| Technical skills | Lists 8-10 core technologies learned through university and internships, ordered by proficiency. | Lists 10-12 production-proven technologies, organised by category and ordered by relevance to target role. May include architectural patterns and infrastructure tools. |
| Work experience bullets | Focuses on individual contributions and learning. Metrics are smaller scale (hours saved, test coverage increases). Example: "Wrote unit tests using Jest that increased code coverage from 54% to 82%." | Demonstrates leadership, architectural decisions and business impact at scale. Metrics include system uptime, revenue impact, team velocity. Example: "Architected a fraud-detection microservice processing 2.4 million transactions daily, saving £1.2 million annually." |
| Projects section | Includes 2-3 standout projects with links to GitHub and live demos, proving coding ability through personal work. | Includes one standout personal project or open-source contribution, or omits the section entirely if work experience is strong enough. |
| Achievements and leadership | May include hackathon participation, university awards or open-source contributions. | Includes vendor certifications (AWS, GCP), conference talks, mentoring experience, and open-source maintainership with measurable impact (GitHub stars, downloads). |