Skip to content

Sign in or create an account

New here? Enter your email. The first code makes your account.

No password. We email you a 6-digit code. A free account keeps 10 CVs and gets a few free AI actions to start.

Guides · CVs by job

Software engineer CV: projects, stack and impact

How to write a software engineer or developer CV: put the stack where it is seen, describe impact rather than tickets, and link to work people can check.

Updated 6 October 2026 · 2 min read

A developer CV is read twice: once quickly, to check the stack matches, and once carefully, to judge how good you are. Make the first read easy and give the second read something real to judge.

Put the stack near the top

After your summary, add a short skills section grouped by kind: languages, frameworks, data, cloud and tools. Only list what you could be interviewed on today. A long list of things you touched once weakens the ones you know well.

  • Languages: TypeScript, Python, Go
  • Frameworks: React, Next.js, Django
  • Data: PostgreSQL, Redis
  • Cloud and tools: AWS (ECS, S3), Docker, GitHub Actions

Describe impact, not tickets

WeakWorked on the checkout page.
StrongerRebuilt the checkout in React and moved price calculation to the server; checkout errors fell by about two thirds and page load dropped under one second.
WeakDeveloped REST APIs.
StrongerDesigned the orders API used by the mobile apps and three partners; added rate limiting and idempotent retries after a double-charge incident.

Good bullets name the problem, what you built and what changed. Numbers help, but a clear before-and-after story works too.

Links people can check

GitHub, a portfolio or a live product is often worth more than another bullet. Link one or two things you are proud of and make sure the README explains what they do. An empty GitHub profile is better left off.

Early career

With little paid experience, lead with projects. Treat each one like a job: what it does, what you used, what was hard, and a link. Internships, freelance work and open-source contributions all count.

The Signal and Tech templates put skills first, where technical readers look. Both are single column, so screening software reads them cleanly.