Sample report. Daniel Mercer is a fictional candidate — this is real output on invented data.
Analyse my CVPrefer offline? Download advanced sample (with job spec) · Without job spec
Senior Backend Developer
senior level · 7.2 years experience
Filling in the missing metrics, fixing the heading, and evidencing Kubernetes/AWS from real work would lift impact and craft substantially. The ceiling stays moderate because PostgreSQL and production Kafka experience are structural gaps no rewrite can close.
You read as a credible senior .NET engineer with genuine payments-domain exposure — the .NET 8 migration you led at Bytegrove is your strongest card. What holds you back is that not a single bullet carries a number, and the eighteen-month gap before Bytegrove is unexplained, so a screener has to take everything on faith. Quantify the payments API and the migration, and this becomes a very different resume.
Advanced analysis · 20 credits
What an AI Screener Sees
▮ Automated screening report
MAYBEThe candidate matches the core .NET stack and holds a relevant CS degree, but shows no PostgreSQL, no Kafka, and no demonstrated production Kubernetes or AWS work. Payments-domain experience at the current employer is the main reason not to reject outright. Flagged for human review only if the shortlist runs thin.
Decisive factors
- 1.PostgreSQL (required) absent from the resume
- 2.Kubernetes and AWS appear only as skill keywords with no supporting experience
- 3.Current payments API role is directly relevant to the team's domain
Keyword scan
Simulated by a separate AI screening agent that saw only your CV and the job description: the same view a high-volume automated screener gets. It is deliberately colder than the coaching report above.
Your Action Plan
- 1
Replace the "MY JOURNEY" heading with "Experience" so ATS parsers recognise your work history.
MinutesQuick fixAddresses: ATS readiness check: standard_headings
Impact: Lifts resume_craft by removing the one heading most likely to break automated parsing.
- 2
Rewrite the "Improved API response times significantly" bullet with the real before/after latency numbers.
About an hourContentAddresses: Suggested rewrite: "Cut p95 API response times..."
Impact: Directly raises evidence_of_impact — it is currently your weakest dimension because no bullet is quantified.
- 3
Answer the brainstorm questions on the payments API's client count and transaction volume, then add those numbers to your top Bytegrove bullet.
About an hourEvidenceAddresses: Brainstorm prompt: payments API scale
Impact: Raises scale_and_scope by proving the criticality your senior title claims.
- 4
Add a bullet to Bytegrove or Northlight describing real deployment work with Docker/Kubernetes or AWS — or remove them from the skills list.
About an hourContentAddresses: Weakness: skills listed but never demonstrated
Impact: Moves R3/R4 from hollow keywords toward partial or met in requirement_fit.
- 5
Add a one-line explanation for the 2021-2023 gap (e.g. career break) at the top of Experience.
MinutesQuick fixAddresses: Weakness: unexplained eighteen-month gap
Impact: Protects career_trajectory — an explained gap reads far better than one left for a screener to guess at.
- 6
If you have any PostgreSQL exposure from side projects or earlier roles, evidence it; if not, expect keyword screens for this JD to fail on it.
OngoingStrategyAddresses: Requirements matrix: R5 (missing)
Impact: requirement_fit is capped while a named must-have is entirely absent.
Score Breakdown
Core stack matches ("Built REST APIs in C# and ASP.NET Core", ".NET 8"), but PostgreSQL — a stated must-have — appears nowhere, and Kubernetes/AWS exist only in your skills list. A missing must-have caps this dimension.
Every achievement is unquantified: "Improved API response times significantly" is the closest you come to an outcome, and it has no number attached.
"the core payments API used by clients" hints at criticality but no traffic, client count, or team size is ever stated, which undersells a senior title.
Clean junior-to-senior progression across three companies, but the gap between 2021-08 and 2023-03 is unexplained and recent.
Bullets are scannable and dates are complete, but "MY JOURNEY" as a section heading will confuse ATS parsers, and JD keywords like PostgreSQL and microservices are absent.
ATS Keyword Coverage
50%
keyword coverage
70%
of must-have keywords
Missing from your CV
Found in your CV
* found as a variant or abbreviation. Strict keyword matchers may miss it, so consider mirroring the job description's exact wording.
ATS Readiness
- ✓
Contact info in parseable text
Name, email, and phone are present as plain body text.
- !
Standard section headings
"MY JOURNEY" is a non-standard heading — rename it to "Experience" so parsers can find your work history.
- ✓
Dates on every role
Every role has a readable start and end date.
- ✓
Single-column layout
The document uses a single-column layout that parses cleanly.
- ✓
No graphics-only information
No images, icons, or text boxes that would break extraction.
- ✓
Text-based document
All text is selectable and machine-readable.
- ✓
Appropriate length
Content volume is appropriate for roughly seven years of experience.
- ✓
Scannable bullet density
Achievements are written as scannable bullets rather than paragraphs.
Job Requirements Coverage
5+ years of professional backend development experience
Met“Senior Backend Developer - Bytegrove Ltd, Manchester / Mar 2023 - Present”
Roughly seven years of employment clears the bar, though the 2021-2023 gap will get checked.
Expert-level C# and .NET (.NET 8 microservices)
Met“Led the migration of legacy services to .NET 8”
Current, hands-on .NET 8 work — this is your strongest line against the JD.
Kubernetes in production
Partial“C#, ASP.NET Core, SQL Server, Docker, Kubernetes, AWS, Redis, RabbitMQ”
Kubernetes appears only in the skills list; a screener will not credit a required skill that no bullet demonstrates.
AWS (ECS/EKS, SQS, RDS)
Partial“C#, ASP.NET Core, SQL Server, Docker, Kubernetes, AWS, Redis, RabbitMQ”
Same problem as Kubernetes: listed, never evidenced, and the JD names specific services you never mention.
PostgreSQL and relational data modelling
MissingYour database evidence is SQL Server; PostgreSQL is a named must-have and its absence will cost you keyword screens.
Event-driven architectures using Kafka or RabbitMQ
Partial“C#, ASP.NET Core, SQL Server, Docker, Kubernetes, AWS, Redis, RabbitMQ”
RabbitMQ in a skills list is not an event-driven architecture story; no Kafka anywhere.
Designing and operating REST APIs at scale
Partial“Built REST APIs in C# and ASP.NET Core for the logistics platform”
API design is evidenced; "at scale" is not — no volume, latency, or availability numbers exist anywhere.
Bachelor's degree in Computer Science or related field
Met“BSc Computer Science, University of Leeds, 2017”
Clean match.
Terraform / infrastructure as code
MissingNice-to-have, but its absence reinforces the thin infrastructure story.
Observability tooling (Grafana, Prometheus)
MissingNot mentioned; on-call experience at Northlight could have carried this if tooling were named.
Strengths
- ✓You led a platform-level modernisation in your current role, which is exactly the seniority signal this JD wants.“Led the migration of legacy services to .NET 8”Bytegrove Ltd — Senior Backend Developer
- ✓You work in the payments domain the employer operates in.“Working on the core payments API used by clients”Bytegrove Ltd — Senior Backend Developer
- ✓Steady progression from junior to senior across three companies shows real momentum.“Junior Developer — PixelForge Agency, Leeds / Sep 2017 - May 2019”Dates
Weaknesses
- !There is an unexplained eighteen-month employment gap immediately before your current role.“Jun 2019 - Aug 2021 ... Mar 2023 - Present”Dates
- !Not one bullet on the resume contains a number, so every achievement reads as unverified.“Improved API response times significantly”Bytegrove Ltd — Senior Backend Developer
- !Kubernetes, AWS, and RabbitMQ are listed as skills but never demonstrated in any role's bullets.“C#, ASP.NET Core, SQL Server, Docker, Kubernetes, AWS, Redis, RabbitMQ”Skills section
- !The JD's required PostgreSQL experience is absent; your only database evidence is SQL Server.“Wrote SQL Server stored procedures and optimised slow queries”Northlight Systems — Backend Developer
Questions You Should Expect
“What were you doing between August 2021 and March 2023?”
Triggered by: gap between 2021-08 and 2023-03
How to prepare: Have a one-sentence, factual account ready (study, family, freelance, sabbatical) and pivot straight to what you shipped at Bytegrove.
“You list Kubernetes and AWS — describe a production incident you handled on that stack.”
Triggered by: C#, ASP.NET Core, SQL Server, Docker, Kubernetes, AWS, Redis, RabbitMQ
How to prepare: If your exposure is limited, say precisely what you have done (e.g. deployed to a managed cluster) rather than defending the list.
“You say response times improved significantly — what was the actual before and after?”
Triggered by: Improved API response times significantly
How to prepare: Dig out the real p95 numbers before the interview; a concrete delta turns your weakest bullet into your best.
“How large is the payments API you work on — traffic, clients, team?”
Triggered by: Working on the core payments API used by clients
How to prepare: Know your system's scale numbers cold; senior candidates are expected to quantify criticality without hesitation.
Suggested Rewrites
Original
Working on the core payments API used by clients
Improved
Develop and operate the core payments API serving [N] clients and processing [X] transactions per day on .NET 8
Why: Turns a passive duty statement into an ownership claim with the scale evidence R7 asks for.
Original
Improved API response times significantly
Improved
Cut p95 API response times by [X%] (from [Y]ms to [Z]ms) by profiling and optimising the hottest endpoints
Why: "Significantly" convinces no one; a latency delta is the single most credible performance claim you can make.
Original
Led the migration of legacy services to .NET 8
Improved
Led the migration of [N] legacy services to .NET 8 with [zero/minimal] downtime, cutting deployment time by [X%]
Why: Adding scope and outcome converts a good bullet into direct evidence for R2 and your seniority.
Original
Mentoring two junior developers on the team
Improved
Mentor two junior developers through weekly 1:1s and code review, [outcome: e.g. both now own services independently]
Why: An outcome makes mentorship a leadership claim instead of a calendar entry.
Brainstorming Prompts
Where You're Strongest
You're applying at the right level
The JD asks for a senior engineer with 5+ years; your title, tenure, and migration leadership match that level, though your evidence understates it — the resume proves less than you have likely done.
Senior .NET Developer
Current .NET 8 migration leadership ("Led the migration of legacy services to .NET 8") plus seven years in the C# ecosystem is exactly this market's core ask.
Lead with: The .NET 8 migration, the payments API ownership, and your mentoring of two juniors.
Backend Engineer (Payments/Fintech)
Payments-domain exposure ("the core payments API used by clients") is scarce and commands a premium; your stack matches the sector's .NET-heavy incumbents.
Lead with: Payments API work first, then reliability signals: on-call experience and incident response at Northlight.
API Developer (C#/.NET)
"Built REST APIs in C# and ASP.NET Core" plus current API ownership makes API-focused roles your highest-probability interviews.
Lead with: REST API design at Northlight, API contract collaboration with frontend, current payments API operation.
One deliberate move away
Platform Engineer
Gap to close: You need demonstrated production Kubernetes/AWS work — one real deployment migration or infrastructure project turns your skills-list keywords into evidence.
Engineering Team Lead
Gap to close: Extend the mentoring you already do into owned delivery outcomes — lead a project end-to-end and quantify the team result.
See your own report like this
Daniel's report took under a minute. Upload your CV and get the same score, screener verdict, and line-by-line fixes on your own experience.
Analyse my CVFree to try · Sign in in one click · No credit card