Capture the offer exactly
Start with the complete text of the fictional offer, including headings, qualifications, responsibilities, and notes near the end. Copy each sentence into a working document before assigning a category. Preserve qualifiers such as “required,” “preferred,” “ideal,” “or,” “and,” “equivalent,” “minimum,” and “plus.” These words change how a requirement should be read. Keep the surrounding sentence when a short phrase could have multiple meanings. For example, “JavaScript or TypeScript” is not the same as “JavaScript and TypeScript.” At this stage, do not compare the offer with your background and do not rewrite the wording. The goal is a reliable source record that lets you check every later decision against the employer’s original language.
Split the wording into atomic items
Separate each sentence into the smallest units that can receive different classifications, while retaining relationships between them. A tool, duration, credential, responsibility, location condition, and language requirement may need separate rows. Do not split a combined condition if doing so changes its meaning: “Bachelor’s degree plus equivalent experience” contains permitted alternatives that must remain visible. Likewise, “JavaScript and PostgreSQL” describes a combination, while “JavaScript or TypeScript” offers an alternative. Use a source phrase column and an interpretation column so your reading can be reviewed. Avoid adding implied technologies or seniority levels. This step is about structure, not judgment. If a phrase remains too broad to divide safely, keep it intact and mark it unclear later.
Classify required, preferred, and unclear language
Assign a category using the offer’s explicit wording first. Required language includes direct terms such as “must,” “required,” or a stated minimum. Preferred language includes “preferred,” “nice to have,” or similar wording that signals value without making it a stated condition. Unclear language covers vague phrases such as “cloud exposure,” “strong communication,” or “modern tooling” when the offer does not define scope, depth, or acceptable alternatives. A responsibility can be important without being explicitly required, so do not promote it automatically. Record the exact reason for every category in a notes column. If two sections conflict, preserve both statements and flag the conflict for clarification rather than choosing the stricter interpretation.
Compare each item with career notes
Review the buyer’s career notes against each classified item and record only evidence that is actually documented. Use concise references such as a role, project, credential, date range, or named tool when those facts exist in the notes. Mark an item supported, partially supported, or unanswered. Partial support is useful when the evidence covers one side of an alternative, less than a stated duration, or a related but not identical scope. An unanswered preferred item is still worth recording, but it is not automatically a blocker. If the notes do not establish a fact, leave it unresolved. The Radaryno Resume Kit can use buyer career notes, select relevant experience, report gaps, and ask rather than invent; your matrix should follow the same evidence boundary.
Preserve conditions and alternatives
Review the matrix for wording that could be accidentally strengthened. A required “or” condition should not become two required skills. A phrase such as “degree or equivalent experience” should not be recorded as a degree gap when the permitted alternative may apply. A duration should remain attached to the skill it qualifies, and a location or schedule condition should not be mixed with technical evidence. For combined requirements, show the whole condition in the source column and describe which part is documented. This is also the point to distinguish missing evidence from missing experience: career notes may be incomplete even when the person has relevant work. Keep both possibilities visible until the buyer confirms the facts.
Choose clarification questions
Ask a question when the answer could change the category, the evidence judgment, or the practical next action. Good questions target undefined scope: which cloud services count, how much experience is expected, whether a preference is genuinely optional, or whether an equivalent credential is accepted. Avoid asking questions whose answers would not change the matrix. For a required item with no evidence, ask the buyer to confirm whether relevant experience exists in the career notes before treating it as a gap. For an unclear offer phrase, record the ambiguity and prepare a concise employer-facing question if appropriate. The final matrix should show what is supported, what is preferred, what remains unclear, and which points need confirmation.
| Offer wording | Category | Evidence status | Next action |
|---|---|---|---|
| “Required: three years of PostgreSQL experience” | Required | Supported, if career notes document the duration | Keep the duration and source visible |
| “Required: experience with JavaScript or TypeScript” | Required alternative | Partial or supported for one option | Preserve “or”; do not require both |
| “GitHub Actions preferred” | Preferred | Unanswered | Record as a preference, not a blocker |
| “Cloud exposure” | Unclear | Unanswered | Ask what services, depth, or duration the employer means |
| “Required: bachelor’s degree or equivalent experience” | Required alternative | Supported by one permitted route | Preserve “or”; assess the stated alternative |
Worked example: turning one offer into an evidence matrix
Begin with the fictional offer sentence “Build internal services with JavaScript, PostgreSQL, and GitHub Actions; three years of PostgreSQL experience required; cloud exposure preferred.” Keep the full wording in one source column. The sentence contains tools, a duration, and a preference, so it should not become one undifferentiated list of skills.
Classify the duration as required because the offer states it directly. Classify GitHub Actions as preferred because the wording says preferred. Treat cloud exposure as unclear because it does not say which provider, service, or level of responsibility counts. JavaScript and PostgreSQL are named work areas, but their priority still depends on the surrounding offer language.
Read the fictional career notes next. They document three years of PostgreSQL work and JavaScript service development, but they do not mention GitHub Actions or cloud services. Mark PostgreSQL and JavaScript as supported, GitHub Actions as an unanswered preference, and cloud exposure as an unanswered unclear item. Do not infer cloud experience from a general software role.
Choose clarification questions only for ambiguity that could change the interpretation. Ask which cloud services and level of responsibility are expected, and whether GitHub Actions is useful or essential for the team. The matrix now distinguishes evidence, preference, and uncertainty without producing a match score or predicting an outcome.