How it works

What Reflect reads

Reflect is given two documents and nothing else. How faithfully each one describes the real thing is the ceiling on how useful the answer can be.

What it asks for
Two documents: your résumé as a PDF or Word file, and the job posting, pasted as text. No account, no sign-up.
What it costs you
The time it takes to find both, and a short wait once you submit them.
What comes back
A verdict, a score, the reasoning behind it, the gaps named, and what to do about them.
What it cannot do
Tell you anything your documents do not record — and it will decline outright rather than guess.
What you must do to keep it
Download the PDF. Your analysis lives in this browser tab; closing it puts the result out of reach.

Reflect reads two documents, and looks for one in the other.

The posting names what the role needs. Reflect looks for each of those in your résumé and credits it once, from the one place it found it. Where that place is decides whether it reads as something you showed or something you listed.

The posting asks forBackend Engineer

Required

Preferred

Your résuméone document

Technical skills

Docker · Git · Redis

Internship

Backend Intern · Orbit Systems

Built REST endpoints in Python against PostgreSQL for the reporting service

Projects

Campus transit tracker

Live tracking service in Python and FastAPI; cut p95 latency by 40% for 400 daily users

Education

B.E Computer Engineering · 2025

  • found in work you described — shown
  • found only in a list — listed
  • not found — Reflect has no record of it

Follow a requirement to see where Reflect found it.

  • Pythonshown

    Found in the internship — and again in a project. Credited once.

  • PostgreSQLshown

    Found in the internship, in work that was described.

  • REST APIshown

    Found in the internship, in work that was described.

  • Dockerlisted

    Found only in the skills line — named, not described.

  • Kubernetesnot found

    Nowhere in the document. Reflect has no record of it.

  • FastAPIshown

    Found in a project that was described.

Python appears twice in this résumé and is credited once. Naming a tool again does not add to it — what changes the reading is whether the document records you using it. Moving a word does not move the work.

What it cannot know

Everything Reflect concludes has to survive being traced back to something your documents actually record. Where there is no record, there is no conclusion — and it says so rather than filling the gap.

  • It cannot tell how well you did any of it.

    A document records what happened, not how good it was.

  • It cannot see work you left out.

    If the document undersells you, so will the result.

  • It cannot judge a role it was not shown.

    The requirements come from the posting you paste, not from a template of what the job usually wants. A thin posting gives a thinner reading, and Reflect says so when that happens.

When Reflect will not answer

Reflect is built for software engineering and technical roles, and it would rather decline than guess. It stops before scoring when it cannot read a résumé into anything it recognises, and when the posting names a graduation year you fall outside — which is the employer’s constraint, not a judgement of you.

What you leave with

A report in five chapters: the verdict and the reasoning, where you stand against the role, how the number was built, what qualifies the reading, and what Reflect inferred beyond the evidence. It lives in the browser tab that made it, so the PDF is the copy you keep.

What happens to the documents themselves — what is kept, for how long, and what leaves Reflect — is answered in full on Privacy & Trust.

Analyse my fit