Home / CV examples / Software Engineer
Software engineer CV example
A backend-leaning engineer with six years of experience, applying for senior roles. The skills sit in the sidebar grouped by type, so a reviewer can check the stack in five seconds and spend the rest of their time on what was actually built.
No sign-up. Download as PDF or Word when you are done.
A fictional example, set in the Terminal template.
Why this CV works
Every bullet has a before and an after
“Latency fell from 840 ms to 210 ms” tells a hiring manager the size of the problem and the size of the fix. “Improved performance” tells them nothing. If you cannot share exact figures, give the order of magnitude.
Skills are grouped, not dumped
Four short groups are easier to scan than a paragraph of twenty technologies, and they show which tools you use together. Only list what you could discuss in an interview.
Scope is stated early
Requests per day, number of integrations and team size appear in the first lines. Engineering managers read for scale before anything else, because it decides the level of the role.
One project, and it is real
A single maintained project with a link is worth more than five tutorial clones. It gives the reader something to open.
The full text of this CV
The same CV as plain text, 284 words — about one page. Read it for length and tone as much as for content: this is how much fits, and how short each line is.
Priya Raman
Senior Software Engineer | Backend & Platform
Toronto, Canada | +1 (416) 555-0137 | priya.raman@example.com
Professional Summary
Backend engineer with six years building and running payment and logistics services in Python and Go. Led the split of a monolith into services handling 4 million requests a day, and mentors three junior engineers. Looking for a senior role with ownership of a platform area.
Skills
- Languages: Python, Go, TypeScript, SQL
- Backend: Django, FastAPI, gRPC, PostgreSQL, Redis, Kafka
- Cloud: AWS (ECS, RDS, SQS), Terraform, Docker, GitHub Actions
- Practice: System design, Code review, On-call, Mentoring
Professional Experience
Senior Software Engineer, Larkfield Payments, Toronto Apr 2022 – Present
- Led the design of a reconciliation service that matches 1.2 million card transactions a day, cutting unmatched items from 0.9% to 0.1%.
- Split the billing monolith into five services over nine months with no customer-facing downtime; p95 API latency fell from 840 ms to 210 ms.
- Introduced contract tests between services, reducing integration bugs reaching staging by roughly half over two quarters.
- Mentor three engineers through weekly pairing; two were promoted within eighteen months.
Software Engineer, Tidewater Logistics, Toronto Jun 2019 – Mar 2022
- Built the shipment-tracking API used by 300 carrier integrations, sustaining 99.95% availability over two years.
- Replaced nightly batch exports with event streaming, bringing partner data delay down from 24 hours to under one minute.
- Cut CI time from 38 to 11 minutes by parallelising tests and caching dependencies.
Key Projects
ledger-diff Go, PostgreSQL
Open-source command-line tool that compares two ledgers and explains every difference line by line.
- Used by four finance teams to check month-end migrations.
Education
B.Sc. (Hons) Computer Science, Halden University — Graduated with distinction 2019
Certifications
- AWS Certified Solutions Architect – Associate — Amazon Web Services, 2023
Languages
English (Fluent), Tamil (Native), French (Intermediate)
Priya Raman does not exist. Every person, employer, school and figure here is invented to show structure and wording.
Adapting it to your situation
- Applying through a large company's portal? Switch to a single-column template such as Classic — sidebars can be read out of order by older applicant tracking systems.
- Put the language and framework named in the job advert first in each skills group.
- Under two years of experience: move Projects above Experience and give each project two bullets.
Common mistakes on software engineer CVs
- A skills list of thirty technologies, half of them used once.
- Bullets that describe the product instead of your part in building it.
- A link to a profile full of empty or forked repositories. Link one or two projects worth opening.
Words employers look for
Terms that commonly appear in adverts for this kind of job. Use the ones that are true of you, in the exact wording of the advert you are answering — and only where you can back them with an example.
- Python
- Go
- microservices
- REST API
- PostgreSQL
- AWS
- CI/CD
- system design
- code review
- Kubernetes or ECS
Questions
Should a software engineer CV be one page?
One page for up to about eight years of experience; two if you are senior and the second page is recent, relevant work. Reviewers rarely read beyond the first two roles, so put your strongest results there.
Do I need a GitHub link?
Only if there is something to see. A maintained project, a real contribution or a clear write-up helps. An empty profile adds nothing, and plenty of strong engineers are hired on their work history alone.
Data Analyst
Civil Engineer
Mechanical Engineer
Electrical Engineer