How to Write a Software Engineer CV That Passes ATS

Engineering hiring is a funnel: applicant tracking system, recruiter screen, technical screen, interviews. Your software engineer CV must survive the first two before anyone asks about system design. That means plain-text skills the parser can find, bullets that prove impact — not just repositories — and seniority signals that match the level on the job ad. This guide covers what tech screening actually looks for and how to frame your experience so both the robot and the hiring manager say yes.

How engineering CVs get screened

In-house recruiters and sourcers often are not engineers. They search the ATS for tokens: Python, React, AWS, Kubernetes, "microservices", "CI/CD". If your CV says "full-stack development" but never names the stack, you may not surface in search even when you are qualified. Hiring managers then look for evidence: scale, reliability, ownership, and whether you have shipped in a similar domain (fintech, health, B2B SaaS).

Parsing matters too. Two-column CVs with skills in a sidebar graphic are a classic failure mode — the ATS reads columns in the wrong order or drops the skills block entirely. See our post on formatting mistakes that break ATS parsing before you upload another PDF.

Must-have sections and keywords

Structure your CV in this order unless you have a strong reason not to:

1. Contact — email, phone, city, LinkedIn, GitHub/portfolio URL
2. Professional summary — role, years, primary stack, domain, one proof point
3. Technical skills — grouped lists, not icons or rating bars
4. Experience — reverse chronological, 3–5 bullets per role
5. Education — degree, institution; include relevant modules only if junior
6. Certifications — AWS, Azure, etc., if relevant and current

Mirror the job description: if they ask for TypeScript and you have it, say TypeScript in skills and in a bullet. Our keyword matching guide applies directly to engineering ads.

Skills section: what to include

• Languages: e.g. Python, Java, TypeScript, Go
• Frameworks/libraries: React, Django, Spring Boot, .NET
• Data & messaging: PostgreSQL, Redis, Kafka
• Cloud & DevOps: AWS, GCP, Docker, Kubernetes, Terraform, GitHub Actions
• Practices: Agile, TDD, code review, on-call

Do not claim expert-level on everything. Recruiters and engineers both spot inflated skill lists in interview.

The bullet formula for engineers

Strong engineering bullets combine what you built or improved, how (stack or approach), and outcome (users, latency, cost, reliability, delivery time). "Worked on backend services" is invisible. "Reduced p95 API latency from 420ms to 180ms by introducing Redis caching and query indexing in PostgreSQL" is interview-worthy.

Three before-and-after bullet examples

Backend / platform

Before: Developed microservices using Java and Spring Boot.

After: Built payment reconciliation microservice (Java, Spring Boot, Kafka) processing 2M events/day; cut manual finance adjustments by 85% and achieved 99.95% processing SLA.

Frontend

Before: Responsible for React development on customer portal.

After: Rebuilt customer onboarding flow in React and TypeScript; completion rate rose from 61% to 78% and support tickets for "stuck signup" fell by 40% in Q1.

Senior / lead signals

Before: Led team and attended meetings about architecture.

After: Tech lead for 6-engineer squad owning checkout platform; introduced RFC process and phased monolith decomposition — deployed 14 services to AWS EKS with zero customer-facing downtime during migration.

Junior vs mid vs senior: what changes

Junior: Emphasise projects, internships, coursework with real stack. Show learning velocity and code quality habits (tests, reviews). One page is usually right.

Mid: Own features end-to-end. Bullets should show independence, debugging production issues, and collaboration with product and QA.

Senior: System design, mentoring, incident response, trade-off decisions, cross-team influence. Two pages acceptable if every line supports staff/principal-level scope — do not list every sprint task from five years ago.

Sample professional summary

Backend software engineer with 5 years building scalable services in Python and AWS. Shipped event-driven billing platform handling £12M annual transaction volume; strong in PostgreSQL, Docker, and CI/CD. Seeking senior backend role in fintech or payments.

Adjust stack, domain, and proof point to match each application. The summary is the highest-ROI tailoring on a developer CV — it feeds ATS keywords and wins the recruiter's first scan (see our 7-second test).

Common software engineer CV mistakes

• Skills only in a graphic sidebar the ATS cannot read
• Bullets that list tickets closed without business or technical outcome
• Internal codenames for products recruiters will not recognise — add a plain-English descriptor
• Omitting cloud provider and saying only "deployed to production"
• Ten-page CVs with every technology ever touched — tailor to the role
• No link to GitHub or portfolio when your public work is strong (humans will look)

Projects and education

If you have fewer than two years of commercial experience, a Projects section can carry weight. Format each like a mini job: project name, stack, what it does, outcome (users, performance, open-source stars if meaningful). For bootcamp graduates, name the bootcamp and capstone with the same discipline.

Computer Science degrees matter less after your first role unless you are applying to research-heavy or graduate programmes. Keep education to degree, institution, year, and optional distinction.

Dual audience reminder

Optimise for parsing and keywords without turning bullets into jargon soup. Read our guide on optimising for the robot and the recruiter and the broader guide to beating applicant tracking systems. The engineering market is competitive — a CV that parses cleanly and proves impact is table stakes.

Next steps

For section-by-section CV fundamentals, read our complete guide to writing a CV. Paste a target job description alongside your CV in Cvaluate's free analysis to see missing stack keywords, parsing issues, and line-by-line bullet rewrites — before you apply to your next engineering role.