The whole dashboard, no account
This is what a real scan looks like
Most tools ask you to sign up before showing you anything. Here is a complete inteller.ai scan instead — a backend engineer against a payments role — with every panel a paying customer sees, and none of it edited to flatter us.
What is real here: the candidate is invented, but nothing else is. The match score, keyword breakdown and posting analysis below are produced by the same engines your own scan runs through, on the pair shown above. The two AI panels are a saved run of our production prompts from 8 September 2026 — stored, not re-generated per visitor, so this page costs nothing to read.
The job
Senior Backend Engineer — Payments Platform
London, hybrid. Python, PostgreSQL, Redis, Docker, Kubernetes, AWS. Terraform and fintech experience listed as nice-to-have.
The resume
Backend Engineer, six years
Python services at scale, a ledger on PostgreSQL, Redis caching, Docker on AWS ECS. No Kubernetes, no Terraform, no regulated-industry background.
Is the posting even real?
Before fit, legitimacy. Every scan starts with 30+ fraud and ghost-job patterns run against the posting itself — the check no resume tool does.
Worth applying
Looks legitimate — 3 green signals, no ghost job signals. Worth applying if you match the requirements.
Ghost-job signals: 0 of 5 · 3 green flags · 0 serious flags
On-Call Duties Expected
Hybrid Work Model
Equity/Stock Options
Flexible Schedule
How well does the resume match?
The ATS match is scored against this exact posting, not a generic grade. The same resume scores differently on every job, because every job wants different things.
Fair match
ATS match, this job
9 of 14 requirements this posting names appear on the resume.
A keyword count is where most tools stop. It is the first panel here, not the last — it tells you the resume will get read, not whether the person can do the job.
Which words are missing
The actionable gap — hard skills and certifications the posting names and the resume does not. Generic soft skills are kept out on purpose: nobody should edit a resume to add the word 'communication'.
Matched Keywords (9)
Missing Keywords (4)
Also mentioned (1)
Soft skills the posting names. Show these with evidence in your bullets rather than listing them.
Notice the two numbers: 67% on keywords, 87% on requirements. They are not in conflict — they measure different things, and the distance between them is the point. The keyword score models what dumb filtering software sees: the literal words. The requirement score is what a person reading the resume would conclude. This candidate is a much better fit than the keyword count suggests, and would still be filtered out by a system that only counts words.
Which is exactly what tailoring is for — and why it has to be honest rather than keyword-stuffed. Employers detect stuffing at 77%.
Requirement by requirement, with the proof
This is the panel that is not a keyword counter. Each requirement is judged covered, partial or missing — and every claim has to cite a line from the resume, which we verify in code before showing it. The model does not get to assert that evidence exists.
87%
requirements met
6 of 7 must-haves covered
You've got six years of Python backend work with a real ledger service on PostgreSQL and Redis, which is nearly a direct match for this role's core ask. The gap is Kubernetes — you've run containers on ECS, not K8s, and there's no fintech/regulated-industry or Terraform experience to point to.
Terraform
Nothing in your resume mentions Terraform or infrastructure-as-code tooling, so this nice-to-have is currently a blank.
Production experience running containers with Docker and Kubernetes
RequiredYou clearly have production Docker experience, but the resume shows ECS rather than Kubernetes, so a recruiter will ask whether you've actually run workloads on K8s.
Containerised the estate with Docker and ran it on AWS ECS.
Experience in fintech or another regulated environment
Building a ledger service is adjacent to fintech-style work, but the posting's regulated/compliance framing isn't explicitly present in your background, so you'll want to spell out any regulatory exposure if you have it.
Designed and shipped a ledger service on PostgreSQL handling around four million rows a day
5+ years building backend services in Python
RequiredYou have six years against a five-year bar, so this is a clear match.
Six years building and running backend services in Python for high-volume consumer products.
Deep experience with PostgreSQL, and with Redis for caching
RequiredYou've built a ledger service on PostgreSQL at real volume with Redis caching on hot paths, which is exactly what this posting wants.
Designed and shipped a ledger service on PostgreSQL handling around four million rows a day, with Redis caching in front of the hot paths.
Familiarity with AWS
RequiredRunning production services on AWS ECS demonstrates real AWS familiarity.
Containerised the estate with Docker and ran it on AWS ECS.
Comfortable designing REST APIs
RequiredYou've designed and maintained internal APIs used by multiple teams, which directly covers this requirement.
Built and maintained the internal APIs used by four product teams
Strong written communication
RequiredAuthoring an incident review process that's still in use is solid evidence of written communication, backed by 'technical writing' in your skills list.
wrote the incident review process the team still uses today
Reading between the lines
Not stated in the posting, but implied by how the role is described.
- ·Given the emphasis on 'work closely with our compliance team on regulated flows,' they likely want someone who can navigate compliance requirements and audit trails, not just build the ledger technically.
- ·The mention of 'a handful of partners' for the API suggests they want someone comfortable with external-facing API contracts and versioning, not just internal-only APIs.
The honest read
What a friend who knew the market would tell you. Note that it does not say 'apply, you're perfect' — it names the gaps and what to do about each one.
AI Analysis
Quick Take
Worth applying to — you cover the core technical stack solidly, and the gaps are the kind that come up in interviews rather than kill your application outright.
Fit Assessment
- •Kubernetes — you have Docker but it sounds like your K8s exposure is partial. This is likely to come up directly since they say "production experience," not just familiarity.
- •Terraform — listed as nice-to-have, so not disqualifying, but worth having a story ready ("I've used CloudFormation/Pulumi, picked up Terraform basics" or similar).
- •Fintech/regulated environment — also partial. This matters more than it looks on paper because the role explicitly involves compliance and "moving real money." You'll want a compelling narrative even if it's adjacent experience (healthcare, security-sensitive systems, anything with audit trails or strict data handling).
Your foundation is strong: Python, PostgreSQL, Redis, AWS, Docker, and REST API design are all matched, and those are the bulk of the "must-have" list. That's a legitimate 5+ years profile for this kind of role.
The gaps worth being honest with yourself about:
None of these are dealbreakers, but expect the interviewer to probe them.
Red Flags & Highlights
- •"We write things down" signals a mature, low-chaos engineering culture — a good sign for how decisions and incidents are handled.
- •Reasonable scope (ledger + reconciliation, not "rebuild the entire platform").
- •Hybrid 2 days/week is a manageable ask.
- •On-call for a payments system with compliance involvement can be genuinely stressful — ask about incident frequency, escalation support, and what "share the rotation" actually means in practice (how many people, how often).
- •"A handful of partners" using your APIs suggests you'll need to think about backwards compatibility and external-facing reliability, not just internal tooling.
- •No mention of team size or reporting structure — worth clarifying in the interview.
Highlights:
Watch for:
Recommendation
1. Apply — your match is strong enough that ATS/recruiter screens shouldn't be a barrier.
2. Before applying, add 1-2 lines to your resume/cover letter addressing Kubernetes and any regulated-environment experience directly, even if it's "operated services in production K8s clusters" rather than deep expertise.
3. Prep a specific story about handling sensitive data, audits, or strict correctness requirements (ledgers demand precision) — this will matter more in the interview than your resume keywords suggest.
Now run it on the job you are actually looking at
Panels 1 to 3 run free, on your own posting and resume, with no account and nothing saved. The requirement coverage and the advisor come with a plan — but you can see exactly what you would be paying for, above, before you decide.