For employees a CV is an application. For freelancers it's a sales tool — outcomes first, clients named, framing tuned to the proposal. Different goals, different choices.
Specific positioning at the top
Not "freelance software engineer". Rather "Freelance software engineer | backend + DevOps for scale-ups in fintech | Amsterdam / remote". Specific wins — it signals you know which clients you serve.
Recent engagements in depth
Three to five engagements with depth. Per engagement: client (or sector under NDA), period + scope, problem, your role, measurable outcome. Client names matter — a €120/hour freelancer and a €180/hour one frame them differently.
Toolset and honest limitation
The three to five tools you're genuinely good at right now. Plus, for seniors: what you no longer take on. "Don't work with PHP codebases older than 2015 anymore" makes you serious about your craft.
Concrete examples
- Freelance backend engineer | scale-up fintech | Amsterdam/remote | available Q3 2026.
- Engagement 2024–2025: Bunq — re-architecture of payment engine; team of 5; 9 months; p99 latency 480ms → 110ms.
- Engagement 2023–2024: Cancom — multi-tenant SaaS platform; team of 3; 6 months; production-launched.
- Stack: Go, Postgres, Kafka, AWS (EKS/RDS/SQS), Terraform. Experience: distributed systems, event sourcing.
- Rate: €120/hour indicative; flexible around scope. Preference: scale-ups 50–200 FTE, technically strong teams.
Pitfalls
- Generic "freelance engineer" without positioning. Specific attracts; generic drifts.
- No measurable outcomes per engagement. For freelance proposals it's the proof of value.
- Claiming NDA client names without justification. Get permission or generalise to sector.
A freelance CV must read well for a C-level client. Balanced fits — no design statements, still professional.