Write a developer CV that gets read
The layout, the bullet formula, and what to leave out, with before-and-after examples.
4 نوفمبر 2026
Anatomy of a one-page CV
your-name-cv.pdf
Name · City · Email · LinkedIn · GitHub
Plain text, so software and people can both read it.
Backend engineer, 6 years in payments. Go, PostgreSQL, AWS.
Two lines: who you are and what you do best.
Experience, newest first
This gets the most space. Lead with results.
Skills: only what you could be interviewed on
If you cannot discuss it, remove it.
Education · Certifications
Short. Put it higher only if you are a recent graduate.
Skill bars, photo, full address, references
Skill bars mean nothing. Include a photo or date of birth only where it is the local norm.
The bullet formula
Action verbWhat you builtHowResult with a number
Rebuilt the checkout API in Go, cutting p95 latency from 800 ms to 200 ms.
Same work, stronger bullets
Before
- Responsible for backend development
- Worked on performance improvements
- Helped with the AWS migration
After
- Built 4 payment services handling 2M transactions a month
- Reduced page load from 4 s to 1.5 s by adding caching and fixing slow queries
- Moved 30 services to AWS with no customer-facing downtime
Before you send it
- Saved as a PDF with text you can select
- One page, or two with 10+ years of experience
- Must-have skills from the JD appear in your wording
- Every number is one you can defend in an interview
- Links open, and your GitHub shows work you are happy with
- Read aloud once to catch mistakes
Use only real numbers. If you have none, describe scale honestly: users, requests, team size or services owned.