Reading Fit Without Letting Fit Rewrite the Job
Once a role has earned deeper attention, career-ops changes modes. The scanner has asked whether the opportunity is identifiable and worth inspecting; the evaluator must now ask what the work requires, how the candidate's evidence maps to it, and which risks deserve a response. This chapter explains how the structured report keeps those questions separate, and why its most important safeguard reads the job description before it reads the candidate's résumé.
One report, several kinds of judgment
The evaluation is not a single match number with explanatory decoration. It is a set of connected views of one role. The role summary describes the domain, function, level, work mode, team context, and culture signals. The CV-match section maps significant requirements to evidence and gaps. The level and strategy section asks how the candidate can present seniority honestly. Compensation and demand distinguish an advertised figure from what is likely to be stable pay and place it in the context of the hiring entity. The customization plan identifies changes to the candidate's materials. The interview plan turns requirements into stories, reflections, and a case study. Posting legitimacy asks whether the opening itself appears real and active.
These views answer different questions:
| Report surface | Question it answers |
|---|---|
| Role summary | What kind of work is this, and what context is visible? |
| CV match | Which requirements have evidence, and where are the gaps? |
| Level and strategy | How should the candidate position their actual scope? |
| Compensation and demand | What can be inferred about the offer and market context? |
| Customization plan | What truthful emphasis would make the evidence clearer? |
| Interview plan | Which experiences and lessons should the candidate prepare? |
| Posting legitimacy | How much confidence should the candidate place in the opening itself? |
A high-scoring role may receive a further application-answer section, but that section is conditional rather than part of every evaluation. The distinction matters because a report can be useful even when it recommends against applying. It can explain why a role is a poor match, which gap is recoverable, whether the compensation needs clarification, or why a posting should be verified before the candidate invests more time.
The architecture is intentionally resistant to a common shortcut: treating every negative observation as the same kind of negative. A missing skill is not the same as a suspicious URL. A weak compensation signal is not the same as a culture conflict. An uncertain posting is not a low-fit role. Keeping the views separate lets a candidate decide which issue changes the next action and which issue merely changes preparation.