How to write a software engineer CV
Make it easy to see what you built, the part you owned, and why it mattered. Put relevant technical skills in context instead of relying on a long list of tools.
Recommended structure
- Contact details and relevant portfolio or code links.
- A brief profile focused on the kind of engineering work you do.
- Technical skills grouped by language, framework, platform, or practice.
- Experience in reverse chronological order, with concise achievement bullets.
- Selected projects or education when they add relevant evidence.
Write bullets with a clear result
A useful pattern is action + technical context + verified result. If you do not have a reliable number, describe the outcome without inventing one.
Example: Reworked the deployment pipeline with GitHub Actions and Docker, reducing manual release steps and making rollbacks easier to run.
Use a specific outcome when you can support it: reliability, latency, cost, release frequency, user impact, or reduced manual work. Be ready to explain how you measured it and what your contribution was.
Make technical skills credible
- Group skills so a recruiter can scan them quickly.
- Prioritize tools requested in the role, if you have used them.
- Show important skills in experience bullets or project descriptions.
- Remove tools you only recognize but cannot discuss practically.
Keep the document easy to scan
Use clear section headings, consistent dates, and readable spacing. A simple layout makes your experience easier for both people and software to parse. Tailor the order of projects and bullets to each application.
Further reading: Harvard's resume guide recommends specific, fact-based statements and clear formatting.