Search starts with target roles, not a list of vacancies
AI can help group vacancies and formulate search hypotheses, but the decision about role, level, work format, and acceptable trade-offs stays with the person.
Instead of mass submissions, build a small set of role families. For each one, name expected responsibility, evidence, constraints, and what still needs verification.
- A role family describes recurring responsibility rather than only a vacancy title.
- A search hypothesis includes a signal source, a priority criterion, and one bounded next action.
- Compensation, location, format, domain, and seniority are constraints, not hidden assumptions.
- Mass automation, impersonation, and unsupported hiring claims are outside a safe workflow.
The TARGET_ROLE_STRATEGY.md frame
| Field | What it records | Safe boundary |
|---|---|---|
| Role family | Role class and characteristic responsibility | It does not guarantee fit for every vacancy |
| Evidence | Verified proof-of-work or Unknown | It does not turn a learning example into employment history |
| Constraints | Format, location, level, and time limits | Do not store unnecessary personal or secret data |
| Next action | One next check or human decision | It is not proof of a submitted application or employer response |
Canonical lesson source · JavaRush
Open JavaRush material