An assessment or take-home task needs its own contract
Before an assessment, record the prompt, timebox, allowed tools, expected signal, constraints, and stop conditions. Do not call an exercise a completed real assessment without evidence that it was received and completed.
A feedback loop starts with an observed signal, not an assumption about the hiring team’s decision. Even in a learning example, separate feedback received, feedback requested, and Unknown.
- Read the conditions and write acceptance signals without expanding the scope.
- Set a timebox, allowed AI assistance, and human review checkpoints.
- Prepare expected evidence: decisions, trade-offs, checks, and limitations.
- After a result or feedback, record an observation without inventing an evaluation.
- Turn a verified finding into one next remediation action.
A feedback record
| Field | What it records | How not to overstate |
|---|---|---|
| Source | Prompt, review note, or Unknown | Do not call it feedback if feedback was not received |
| Observation | A concrete signal or Unknown | Do not turn silence into rejection or approval |
| Gap | What needs improvement | Separate a personal hypothesis from an external verdict |
| Next attempt | A small preparation change | It does not promise success at the next stage |
Canonical lesson source · JavaRush
Open JavaRush material