Job intelligence means breaking text into signals
Treat the vacancy as a requirements source: separate must-have, nice-to-have, responsibilities, evidence signals, and clarification questions. Do not attribute requirements that are not in the source.
A fit and gap map does not issue a “fit/no fit” verdict. It shows what is supported, partially aligned, missing, and still needs verification.
- Save the vacancy source or mark it Unknown when the URL is unavailable.
- Extract requirements into short atomic lines without changing their meaning.
- For each requirement, add evidence, fit/gap/Unknown status, and confidence.
- Write one bounded follow-up: clarify, collect evidence, or defer the role.
Separate fit, gap, and Unknown
| Status | Meaning | Next action |
|---|---|---|
| Fit | Specific evidence matches the requirement | Check freshness and safe wording |
| Partial fit | A related signal exists but scale or context is missing | Name the boundary and choose a small gap action |
| Gap | No verified evidence is available | Do not hide the gap; decide whether learning is needed |
| Unknown | The text, source, or check is insufficient | Do not make a strong conclusion before clarification |
Canonical lesson source · JavaRush
Open JavaRush material