Sample report
English resume → English posting
Every requirement is judged against a line from the resume, quoted. Where there is no line, nothing is claimed.
The resume and posting in this report are invented examples, not a real person or a real opening. The analysis, scoring and verification are performed by exactly the same code the live service runs.
Fit report
Senior Backend Engineer, Payments Platform
Northbeam
Checked by arithmetic, not by the model
A language model wrote the wording. These were computed from your two documents and would come out the same on every run.
- 5 requirements settled against a line we located in your resume
- 1 stated years threshold tested by adding up your tenures
What this posting filters on before reading closely
These are the checks a recruiter runs first. A tick means the wording is in your resume; the rest are yours to confirm — not findings that they are missing.
- 5+ yearsIn your resume
- Payments domainIn your resume
- Willing to relocate to SingaporeConfirm it is visible
Overall job match
Competitive with edits
Your payments depth is genuinely relevant, but two stated requirements are unevidenced and the strongest thing you did is described in the wrong vocabulary.
Five years entirely inside payments, with quantified outcomes most applicants will not have. What holds this back is evidence, not capability: the posting names Kubernetes and ledger design as requirements, and neither appears in your document. The reconciliation job you built is ledger work — it is simply written in different words than the screener will search for.
Skill match 40%, experience match 32%, ATS readiness 28%. Keyword coverage is already inside ATS readiness and is not counted twice.
Your strongest advantage
Most resumes at this level list what the person was responsible for. Yours states what changed and by how much, which is the strongest signal available in a first-pass read.
Biggest risk
Kubernetes is a stated requirement and appears nowhere — A keyword screen drops the application before anyone reads the rest, and a human screener treats a silent requirement as a missing one.
Do this first
Headcount tells the reviewer nothing about whether you have operated at their volume. Answers the scale question in the first line the reviewer reads, which is where the company-size concern is decided.
Score breakdown
Skill match
60/100Borderline
Measured + AI3 of 6 must-have requirements are fully evidenced. Each requirement is weighted by how central the posting makes it, and partial evidence earns half credit.
5+ years of backend engineering experience in production systems
Strong Go or Java; you will work primarily in Go
Comfortable owning an on-call rotation for tier-1 services
Hands-on experience running services on Kubernetes
Experience with Kafka or another event streaming platform
Exposure to multi-currency and FX settlement
Experience match
77/100Competitive
AI judgmentWeighted across five dimensions: domain relevance carries the most, industry the least, and years, seniority and scope count equally in between.
Domain: Payments and settlement throughout, which is exactly the problem space.
Years: Five years against a 5+ ask — meets it, without surplus.
Industry: Consumer SaaS and commerce, not licensed financial services.
ATS readiness
69/100Borderline
MeasuredComputed from measured signals: keyword coverage (50%), parseability (25%), section completeness (25%). No formatting risk was found, so nothing was deducted.
Contact details are machine-readable
Employment dates are present
Reads as a single column
No heading was found for: Projects. Parsers split a resume on its headings, so a single line reading "Skills" above the list you already have is usually the whole fix.
Keyword coverage
43/100Weak
Measured4 of 10 posting terms appear in your resume. Critical terms count triple; a term matched only through a translated variant counts at 70%.
Go
reconciliation
on-call
Kubernetes
idempotency
ledger
Requirement coverage9
- CoveredRequired5+ years of backend engineering experience in production systems
Five continuous years of production backend work.
2020.01–2026.08 · 79 months · 2 periods
- CoveredRequiredStrong Go or Java; you will work primarily in Go
Go is the language of the most recent and most significant work.
Rebuilt the invoice pipeline in Go, reducing month-end processing from 6 hours to 40 minutes.
- PartialRequiredDistributed systems: idempotency, exactly-once semantics, event-driven design
Replica migration is distributed-systems work, but idempotency and exactly-once are never named.
Led migration from a single Postgres instance to read replicas; cut p95 API latency by 45%.
- Not foundRequiredHands-on experience running services on Kubernetes
Docker and EC2 appear, which reads as a pre-Kubernetes deployment model.
- PartialRequiredDouble-entry ledger design or financial reconciliation at scale
A reconciliation job is real ledger work, but scale and double-entry design are not evidenced.
Wrote the internal reconciliation job that closed a recurring settlement mismatch.
- CoveredRequiredComfortable owning an on-call rotation for tier-1 services
On-call ownership for the payments domain is stated directly.
Mentored two junior engineers and ran the on-call rotation for the payments domain.
- Not foundPreferredExperience with Kafka or another event streaming platform
No event streaming platform is mentioned.
- Not foundPreferredExposure to multi-currency and FX settlement
No multi-currency or FX work is described.
- Not foundPreferredExperience working with regulators or in a licensed financial entity
No regulated-entity experience is described.
Strengths3
Quantified outcomes, not responsibilities
Most resumes at this level list what the person was responsible for. Yours states what changed and by how much, which is the strongest signal available in a first-pass read.
Rebuilt the invoice pipeline in Go, reducing month-end processing from 6 hours to 40 minutes.
From your resume Domain ownership with the pager
Owning billing plus the on-call rotation is the responsibility profile this team is hiring into, not a nearby one.
Owned the billing service handling recurring subscriptions for 120,000 paying users.
From your resume
1 more strength found
- Every gap, ranked by what it costs you
- The concerns a recruiter will raise, with answers
- All missing keywords and where each belongs
- Every rewrite, applied into an exportable draft
- Positioning, channel, cover-letter angle and interview prep
Critical gaps3
- Critical
Kubernetes is a stated requirement and appears nowhere
Confidence: HighThe posting lists hands-on Kubernetes as a requirement. Your resume names Docker and EC2/RDS/S3, which reads as a pre-Kubernetes deployment model.
A keyword screen drops the application before anyone reads the rest, and a human screener treats a silent requirement as a missing one.
Resume lists AWS EC2, RDS and S3; no container orchestration appears.
If you have touched EKS, Helm, or kubectl even in staging, name it with the context. If not, deploy one service to a managed cluster and write it up as a project line.
- Major
Reconciliation work is described without the ledger vocabulary
Confidence: HighYou built a settlement reconciliation job — that is ledger work. The posting asks for ledger design, and your line describes the same problem in different words.
The reviewer cannot map your experience to their requirement, so it scores as absent rather than as a partial match.
Wrote the internal reconciliation job that closed a recurring settlement mismatch.
Rewrite the reconciliation bullet in the posting’s own terms — ledger, settlement, exactly-once — claiming only what you actually built.
1 more gap identified
- Every gap, ranked by what it costs you
- The concerns a recruiter will raise, with answers
- All missing keywords and where each belongs
- Every rewrite, applied into an exportable draft
- Positioning, channel, cover-letter angle and interview prep
Want a person to read this?
A reviewer who hires for this function — or who works at the company you are applying to — reads your resume against this posting and writes back.
AI-assisted analysis, based on the documents you provided. ATS readiness is an estimate measured from your resume text.