Candidate Evaluation Report
Why medium: Prompting and task correctness are supported by several messages that agree. Judgment and efficiency rest on a single short session, so those scores could move with more evidence. This one task cannot show years of experience.
| Criterion | Weight | Score | Points | Confidence |
|---|---|---|---|---|
| Task correctness | 30% | 72 / 100 | High | |
| Catching AI errors | 20% | 60 / 100 | Medium | |
| Prompting effectiveness | 15% | 82 / 100 | High | |
| Verification discipline | 15% | 48 / 100 | Medium | |
| Judgment and scope calls | 10% | 70 / 100 | Low | |
| Efficiency | 10% | 65 / 100 | Low | |
| Weighted total | 100% | 67 / 100 | Medium |
“Before you write anything: should an order with a null customer be skipped or grouped as unknown? And is the amount already a BigDecimal?”
“Looks good, I'll use that version.”
“Null list returns an empty map; entries with a null customer are skipped and counted separately in the notes.”
STRENGTHS
- Clarifies requirements before coding (E1)
- Explains edge-case decisions in writing (E3)
- Wrote their own final version rather than copying
RISKS TO PROBE
- Accepted AI output without checking null handling (E2)
- No tests written or run; verification only described
- Spring Boot and SQL were not exercised by this task