Extract the requirement into testable claims
Copy the job requirement into a working note and separate its components before comparing it with career evidence. Identify the tool, activity, level of responsibility, context, and any outcome implied by the wording. For example, “lead PostgreSQL migration projects” is more specific than “worked with databases.” This prevents a broad similarity from being treated as proof. Keep the wording neutral and do not start by deciding whether the requirement is present or absent. The goal is to define what evidence would count. If a requirement combines several actions, assess each action independently so that a confirmed part does not conceal an unverified part.
Search career notes for equivalent evidence
Review the buyer’s career notes using related terms, project names, deliverables, and outcomes rather than relying only on the wording in the job requirement. A requirement may be represented by an internal title, a business description, or a result that does not mention the tool explicitly. For each possible match, preserve the original source and classify it provisionally as direct, adjacent, or unclear. Direct evidence describes the required work itself. Adjacent evidence supports a related capability but does not establish the requirement. Unclear evidence suggests a possible match but lacks enough detail about the person’s action, scope, or context.
Resolve uncertainty with focused questions
When the notes suggest a possible match but do not establish it, ask a question designed to fill one evidence gap. State the requirement component, mention the relevant note, and request the missing fact. A useful question might ask whether the person personally configured the system, what part they handled, or whether the work reached production. Avoid questions that merely invite confirmation, such as “Did you use this tool?” when the surrounding context is unclear. If the answer remains vague, classify the requirement as uncertain rather than upgrading it to confirmed evidence. Record the answer in source language before drafting any resume wording.
Separate missing documentation from missing experience
Use the available evidence and answers to choose among three states: missing documentation, confirmed lack of experience, or uncertainty. Missing documentation means the person confirms doing the work but the available notes omit the details; ask for a factual account before writing it. Confirmed lack of experience means the person explicitly confirms they have not performed the required work; record that gap without manufacturing a match. Uncertainty means the material points in a direction but does not establish enough detail. This classification is more useful than a simple match or no-match label because each state leads to a different next action and different restraint in resume language.
Choose the narrowest accurate resume treatment
After classification, decide whether to include, narrow, or omit the requirement. Include a claim only when the source supports the tool, activity, and relevant scope. Narrow the wording when only part of the requirement is confirmed, such as describing data imports instead of claiming ownership of a full migration. Omit the requirement when no reliable evidence exists. Adjacent experience can still be useful if it is presented as adjacent rather than equivalent. The final wording should remain faithful to the buyer’s notes and should not imply certification, production responsibility, leadership, or proficiency that was not confirmed.
Run a final evidence and language check
Review the completed draft against the original requirement and the source notes. Check that each included claim has an identifiable basis, that uncertain items are not written as facts, and that adjacent experience is not framed as a substitute for the missing requirement. Also inspect the offer language: the document should use the requested language while preserving the confirmed meaning of technical terms and responsibilities. If a local resume workflow is used, the Radaryno Resume Kit can select relevant experience, report gaps, and ask rather than inventing, while the buyer remains responsible for confirming the answers. Keep the source notes and generated document together for later review.
| Evidence state | What to verify | Clarifying question | Resume decision | Illustrative example |
|---|---|---|---|---|
| Missing documentation | The activity may exist in notes, project records, or another role description | Which project, employer, date, or deliverable shows this work? | Add the claim only after the source is confirmed | A reporting task is recorded as “monthly business review” rather than “dashboard reporting” |
| Confirmed lack of experience | The available record shows no direct use of the required method or tool | Have you performed this task in any role, project, course, or documented volunteer activity? | Do not claim the requirement; retain relevant adjacent evidence | No record supports production PostgreSQL administration |
| Uncertainty | The notes suggest related work but do not establish scope, ownership, or proficiency | What did you personally do, and what was the outcome or deliverable? | Use a narrower verified description or omit the requirement | The notes mention automation but not whether JavaScript was used |
| Partial evidence | Some parts of the requirement are confirmed while others are not | Which component is supported, and which component remains unverified? | State only the supported component | Confirmed data imports, but no evidence of owning the full migration |
A worked evidence-classification process
Start with the exact requirement and divide it into observable parts. A requirement such as “manage PostgreSQL migrations” may contain database technology, migration work, ownership, and production responsibility. A broad match can hide an unsupported component, so record each part separately before reviewing the career notes.
Search the source notes for equivalent descriptions rather than exact wording alone. A note about schema changes, release coordination, or restoring a database may be relevant, but relevance is not proof of the whole requirement. Mark each possible match as direct, adjacent, or unclear, then retain the source wording for review.
Ask a focused question when the evidence is unclear. For example, ask whether the person personally created and deployed migrations, supported someone else, or only monitored the process. The answer should establish action, scope, context, and approximate timing without inviting the person to choose a flattering interpretation.
Use the answer to choose a narrow resume statement. If direct ownership is confirmed, describe that verified work. If only support is confirmed, describe support. If the requirement remains unsupported, preserve relevant neighboring experience without implying that the missing requirement was met.