Software developer CV example

Hiring managers skim developer CVs for evidence you can deliver software — not for a exhaustive list of every framework on GitHub. Lead with impact, keep stacks honest, and make projects easy to find.

Put impact before buzzwords

Each role should answer: what did you build, for whom, and what changed? “Reduced API response time by 30%” beats “worked with Node.js” on its own.

Match technologies to the job description when you have real experience with them. Avoid listing tools you only touched once in a tutorial.

Projects for juniors, depth for seniors

Early-career developers should highlight two or three strong projects — coursework, open source or freelance — with links where available. Describe your specific contribution, not the team’s generic goal.

Senior profiles can shorten project lists and expand on architecture decisions, team leadership and production ownership.

GitHub and portfolio links

Add a link only if the profile is maintained. Pin repositories that show readable code and a short README. Recruiters may click once — make that click count.

If most work is private, describe outcomes in bullets without breaking confidentiality. NDA work can still mention scale (“payments platform serving X markets”) when allowed.

Skills section: group and prioritise

Group languages, frameworks and infrastructure separately if helpful. Put the stack relevant to the target role first.

Certifications belong when they are recognised in your market (cloud provider certs, security training). Omit outdated or irrelevant credentials.

Fictional example (structure only)

Use the sample below as a layout reference. All names and metrics are invented.

Fictional example

Jonas Weber — Backend Developer Profile: Backend developer with four years building APIs in fintech. Focus on reliable services, observability and clear documentation. Experience: Software Engineer, Paylane GmbH (2022–present) — migrated billing service to event-driven architecture; cut failed transactions by 12%. Software Developer, DataForm Studio (2019–2022) — built internal admin tools in TypeScript and PostgreSQL. Projects: Open-source CLI for schema migrations (1.4k GitHub stars) — maintainer since 2021. Skills: TypeScript, Go, PostgreSQL, AWS, Docker, automated testing.

Frequently asked questions

One page or two for a developer CV?

One page is fine up to roughly five years of experience if every line earns its place. Two pages are acceptable when older roles stay relevant.

Should I list every programming language I know?

No. List core strengths and anything the job requires. Long ungrouped lists suggest keyword stuffing.

Is a photo necessary on a developer CV?

In most tech markets outside parts of Europe, no. Follow local norms and employer instructions.

Can I copy the fictional example?

No. It illustrates structure only. Write your own bullets in the Eventiors builder.

Related resources

Ready to build your CV?

Create your developer CV →