Overall Assessment
This CV shows genuine technical depth but undersells it at every turn. The experience section reads like a list of responsibilities rather than a record of impact.
There's no sense of scale, ownership, or outcome. A recruiter scanning this for 10 seconds would see 'developer who ships code' rather than 'engineer who moves the needle'.
The missing summary section is a real problem: without it, there's no narrative thread connecting your experience, and you're relying on the reader to do work you should be doing for them. The keyword gaps (Docker, CI/CD, AWS) are fixable in an afternoon and will meaningfully improve your ATS pass rate for senior roles in the UK market.
Below level
For a mid-level software engineer role in the UK market, this CV sits just below the bar. The technical skills are there, but the presentation doesn't yet reflect mid-level expectations: ownership of features, measurable impact, and architectural decision-making. The missing summary and weak achievement framing make it read as junior.
With targeted rewrites to the experience section and the keyword fixes, this would comfortably meet the standard.
Overall Score
Good
Score Breakdown
Page count, layout clarity, and machine-readability. Issues here trip up ATS before a human sees your CV.
ATS Issues
Section Feedback
Top 5 Improvements
Add a professional summary (3-4 sentences)
Without a summary, there's no narrative. Recruiters spend 7 seconds on a first scan, so give them something to anchor on.
Software engineer with 4 years building consumer-facing products in TypeScript and React. Specialise in performance-critical frontend systems.
Currently looking for senior IC roles at product-led companies in the UK.
Add email and LinkedIn to your contact section
Missing email is a critical ATS failure. LinkedIn is expected for UK tech roles.
Header format: Name | email@domain.com | linkedin.com/in/yourname | github.com/yourname
Add Docker, CI/CD and cloud keywords to your skills section
These appear in 80%+ of senior UK software engineer job descriptions. Their absence drops your ATS ranking significantly.
Even basic familiarity counts: 'Docker (containerisation, local dev), GitHub Actions (CI/CD pipelines), AWS S3/EC2 (deployment)'
Rewrite 3 experience bullets with the format: [Action verb] + [What you built] + [Measurable result]
Numbers make your impact concrete and memorable. One strong quantified achievement outweighs five vague bullets.
'Optimised database query layer, reducing average API response time from 800ms to 120ms for 50k daily active users'
Add a GitHub link and make sure your repos are public
UK tech recruiters and hiring managers will look at your GitHub. A strong profile (even 2-3 solid projects) compensates for a thin CV.
Pin your best 3 repos. Each should have a clear README explaining what it does and how to run it.
Here's what a recruiter sees in 10 seconds…
Honestly? I'd probably pass on this CV in its current state. Not because the person isn't capable, but because it doesn't give me enough to fight for them internally.
When I'm screening 80 CVs for a senior role, I need to quickly build a case: what's their impact, what's their level, why are they right for this specific role? This CV makes me do too much guesswork. Fix the contact details (non-negotiable), add a summary, and rewrite two or three bullets with real numbers.
Then I've got something I can present to the hiring manager.
What's Working
- Strong core tech stack (TypeScript, React, Node.js) that's in high demand across UK tech
- Projects section shows initiative and independent work beyond employment
- Two-page format is appropriate for your level of experience
- Education section is clean and well-presented
Keyword Analysis
Based on key technical terms for your sector. A gap here is a prompt to review: only add keywords that genuinely reflect your experience.
Detected in your CV
Common in Tech – software / ic
Keywords typically seen in Tech – software / ic CVs, for reference only.
2 pages