Software Engineer CV Example and Guide
A software engineer CV gets read twice. First an applicant tracking system matches your stack against the job ad. Then an engineer reads it to find out what you actually built. That second reader skims for languages, frameworks, scale and ownership. If they can't tell within a few lines whether you've shipped production code in the stack they use, they move on to the next CV.
The fix is to write about systems, not tasks. Name the service, the technology, the problem and the result: latency cut, bugs reduced, releases sped up, users served. Link to GitHub or a portfolio only if it holds work you'd happily discuss in an interview. A tidy repository with a clear README says more than a list of twenty frameworks you used once.
Below you'll find the keywords tech recruiters search for, bullet examples you can adapt, and a sample CV you can open in the builder. Whether you call it a CV or a resume, the rules are the same for developers: one or two pages, a plain layout, and a skills section that mirrors the job you're applying for.
12 years in digital marketing and SEO; teaches tech and AI tools on YouTube. Built ATS CV Online for job seekers in the Gulf, Pakistan and abroad. See how we check CVs.
Software Engineer CV summary example
Software engineer with 5 years of experience building web backends in Node.js and TypeScript, most recently for a payments platform handling over a million transactions a month. Comfortable owning a service end to end, from API design and PostgreSQL schema to Docker deployments on AWS. Known for thorough code reviews and for turning flaky test suites into reliable ones. Looking for a backend or full-stack role on a product team.
Change the years, specialities and results to match your own record. A summary that could fit anyone helps no one.
Experience bullet points for a software engineer CV
- Rebuilt the order search API in Node.js and PostgreSQL, cutting median response time from 900 ms to 180 ms.
- Migrated 14 services from manual server deploys to Docker and GitHub Actions, reducing release time from half a day to 20 minutes.
- Designed an idempotency layer for payment webhooks that ended the duplicate charges customers had been reporting.
- Wrote integration tests for the billing module, raising coverage from 35% to 80% and catching 3 regressions before release.
- Led 3 developers to deliver a React admin dashboard in 10 weeks, replacing four spreadsheets used by the operations team.
- Traced a memory leak in a Java batch job to an unclosed stream, which let us retire one large cloud instance running 24/7.
- Mentored 2 graduate engineers through their first production releases with weekly pairing sessions.
Weak vs strong: rewriting duties as results
ATS keywords for software engineer jobs
Use the ones that are true for you, in the same words the job ad uses.
- JavaScript
- TypeScript
- Python
- Java
- C# / .NET
- React
- Node.js
- REST APIs
- SQL (PostgreSQL, MySQL)
- Git
- Docker
- Kubernetes
- AWS
- CI/CD
- Microservices
- Unit and integration testing
- System design
- Agile / Scrum
Soft skills to prove with examples
- Constructive code review
- Clear technical writing
- Breaking down vague problems
- Ownership of production issues
- Mentoring junior developers
Best section order
- Summary — Two or three lines naming your stack, years of experience and the kind of systems you build, so a recruiter can match you in seconds.
- Technical skills — Group them by languages, frameworks, databases, cloud and tools. Keep only what you'd be comfortable being quizzed on.
- Experience — The core of the CV. Each role should show what you built, with which technology, and what changed because of it.
- Projects — Essential for graduates and career changers. Give a link, the stack, and one line on what the project does and who uses it.
- Education — Degree, university and year. Graduates can add a final-year project; experienced engineers keep this short.
- Certifications — Cloud and Kubernetes certifications help for DevOps and cloud-heavy roles. Put them last unless the ad asks for them.
Certifications and licences worth listing
- AWS Certified Developer – Associate
- AWS Certified Solutions Architect – Associate
- Microsoft Certified: Azure Developer Associate
- Google Cloud Professional Cloud Developer
- Certified Kubernetes Application Developer (CKAD)
- Oracle Certified Professional (OCP), Java SE Developer
Common software engineer CV mistakes
- Listing every language you've touched once. A skills section with 30 technologies looks padded, and interviewers may ask about any of them.
- Describing tickets instead of outcomes. 'Fixed bugs in the mobile app' says nothing; say which bugs, how many, and what improved for users.
- Linking to an empty or messy GitHub. A profile full of forked tutorials with no READMEs can hurt more than having no link at all.
- Rating yourself with skill bars. '4 out of 5 in Python' means nothing to an engineer, and some parsers misread the graphics entirely.
- Leaving out scale. Users, requests per day, data volume or team size tell the reader whether your experience fits the system they run.
Applying in the Gulf, Pakistan or the UK
Pakistan
Many Pakistani engineers build products for foreign clients through software houses or remote contracts. Name the client's industry and country (for example 'US healthcare client') even when you can't name the client, and mention it if you've worked overlapping US or UK hours.
CV format guide →UAE / Gulf
Gulf tech employers often want nationality, visa status and notice period up front. Add them to the header if you're already in the region. List Arabic only if you can actually work in it, as some product teams will test it.
CV format guide →UK
Leave out your photo, date of birth and marital status. If you need visa sponsorship, say so briefly or state your right to work, because only licensed sponsors can hire on a Skilled Worker visa.
CV format guide →Templates that suit a software engineer CV
Software Engineer CV questions
Should a software engineer CV be one page or two?
One page works well for graduates and engineers with up to about five years of experience. Senior engineers with several relevant roles can use two. What matters more is that the top half of page one shows your stack and your strongest recent work.
Do I need a projects section if I already have work experience?
Not always. If your jobs already show the stack the employer wants, projects are optional. Add them when they prove a skill your day job doesn't, such as a mobile app when you work on backends, or a merged open-source contribution.
Should I put my GitHub link on my CV?
Yes, if it has a few repositories you wrote yourself, with READMEs that explain what they do. Pin your best two or three. If nearly all your work is private company code, leave the link out and let your experience bullets do the talking.
How do I write a software engineer CV with no experience?
Lead with education and projects. Describe two or three projects the way you'd describe a job: what you built, the stack, and one result such as users, speed or a live link. Internships, freelance gigs and hackathons all count as experience.
Related guides
CV examples for other jobs
- Nurse CV
- Accountant CV
- Teacher CV
- Sales Executive CV
- Customer Service Representative CV
- Civil Engineer CV
- Digital Marketing Specialist CV
- Administrative Assistant / Office Administrator CV
- Fresh Graduate CV
CV rules by country: UAE · Saudi Arabia · Pakistan · UK · Canada
Write your software engineer CV now
Free, no sign-up, real-text PDF that ATS software can read.