Extract the exact tool requirement
Copy the tool name from the offer without normalizing it into a broader category. Preserve product names, editions, cloud services, database systems, programming languages, and workflow platforms as written. If the offer lists several tools, separate them so each can receive its own evidence status. Also capture the surrounding task, because the same tool can be used for unrelated work. For example, an offer may request JavaScript for front-end development, while the notes mention JavaScript only in a small script. The comparison should show that context rather than treating the name alone as complete proof. Keep the original requirement distinct from any interpretation you make later.
Search the career notes for matching evidence
Review the buyer's career notes for the exact tool name, related spellings, and documented tasks. Treat a named tool plus a relevant task as stronger evidence than a tool name appearing without context. Do not infer experience from an employer, job title, industry, or general technical area. For instance, database work does not identify PostgreSQL, and deployment work does not identify Docker. If the notes are incomplete, retain that uncertainty. The Radaryno Resume Kit uses the buyer's career notes, selects relevant experience, reports gaps, and asks rather than inventing. Your job gap report should therefore preserve what is documented and leave unsupported details unresolved.
Classify direct, adjacent, or unsupported tools
Assign a clear evidence category to each requirement. Direct experience means the notes name the requested tool and connect it to relevant work. Adjacent experience means the notes name another tool or describe a related capability, but do not establish use of the requested product. Unsupported means neither the tool nor sufficient related evidence appears in the notes. A fourth status, needs clarification, can help when the requirement is vague or appears to describe a product family. These categories describe evidence quality, not whether an employer will accept an alternative. Never convert adjacent experience into direct experience simply because the tools appear related.
Write the exact gap without claiming equivalence
State the requested tool and the available evidence in separate phrases. A useful sentence can say that the candidate used MySQL for reporting while PostgreSQL experience is not documented. This is more accurate than writing that the candidate has PostgreSQL experience because both products are databases. Use the same approach for programming languages, cloud services, automation platforms, and collaboration tools. If the notes describe a shared task, include that task only when it is documented. Avoid promising that an employer will treat adjacent experience as sufficient. The report should make the missing tool visible so the buyer can verify, add, or discuss it honestly.
Ask a focused clarification question
When the evidence is incomplete, create a question that can resolve the gap without suggesting the desired answer. Ask whether the buyer has used the exact tool, which version or service was involved, and what task they performed. If the buyer confirms experience, the career notes can be updated before documents are generated. If the buyer does not confirm it, keep the gap visible. The Radaryno Resume Kit can ask rather than invent when relevant information is missing, but it does not independently validate a candidate's history. A precise question is therefore part of the review process, not proof that the requirement is satisfied.
Review the report across generated documents
Check that the comparison remains consistent in the generated HTML, PDF resume, and optional cover letter when a cover letter is requested. The Radaryno Resume Kit generates documents in the offer language and provides four designs: default, classic, compact, and modern. Design changes should not turn an adjacent tool into a direct match or remove an important gap. Review the wording in the selected design and confirm that the application tracker records the offer and document details locally. The tracker does not submit applications, search jobs, or contact employers, so use it to preserve your own comparison and follow-up notes rather than treating it as an application service.
| Requirement evidence | Classification | Report treatment | Illustrative wording |
|---|---|---|---|
| The career notes name the same tool and describe relevant work | Direct experience | Connect the tool to the documented task | Used PostgreSQL to maintain reporting queries |
| The notes name a related tool but not the requested one | Adjacent tool | Name both tools and preserve the distinction | Used MySQL; PostgreSQL experience not documented |
| The notes describe the task but name no tool | Capability without tool evidence | Report the task while leaving the tool unconfirmed | Built reporting queries; database tool not recorded |
| The notes contain no matching tool or task | Unsupported requirement | Keep the exact missing tool visible | Terraform experience not documented |
| The offer requests a tool that may be a product family or variant | Needs clarification | Avoid assuming interchangeability | Cloud deployment tool requested; exact product to confirm |
Worked comparison with before-and-after wording
Begin with the requirement as written: the fictional offer asks for PostgreSQL and GitHub Actions. The career notes state that the candidate used MySQL for reporting and ran deployment checks through a different continuous integration service. Before the comparison, a broad statement such as “database and automation experience” hides the tool difference. After the comparison, the report names PostgreSQL as unsupported, MySQL as adjacent database experience, and GitHub Actions as unconfirmed rather than equivalent.
For a second fictional example, the offer requests JavaScript and Docker. The career notes document JavaScript projects and container work, but they do not name Docker. Before review, “used Docker for deployments” would be an invented claim. After review, JavaScript is marked direct, container work is recorded as relevant adjacent evidence, and Docker remains an exact missing tool. The distinction protects the report from turning a general capability into a product claim.
For a third fictional example, an offer names Salesforce administration while the career notes describe customer-record workflows in another customer relationship system. Before review, “Salesforce administration” would overstate the evidence. After review, the report identifies the other system, describes the shared workflow only where documented, and states that Salesforce administration is not recorded. This gives the buyer a precise question to answer instead of silently changing the requirement.
Finish by checking whether the report preserves the employer's wording and the candidate's wording separately. A useful comparison does not decide that two tools are interchangeable. It shows the evidence, marks uncertainty, and gives the candidate a clear choice: add verified experience, leave the gap visible, or ask for clarification.