Choose one contribution you can support. Separate your decision from team work, observed results from estimates, and evidence from inference.
Problem
Audit this fictional draft: “I built the training platform and improved launch quality”. The evidence instead attributes benchmark design and a launch-gate recommendation to the candidate; another team built the platform. Rewrite the claim without inventing exclusive causal credit.
Picture: One Claim, Different Checks
Patch authorship does not prove ownership of the team rollout
Derivation
Which additional evidence would establish personal rollout responsibility?
Work the Ownership Boundary
This replacement is also fictional, not an achievement to reuse as your own:
I designed a slice benchmark and recommended a launch gate. Another team owned the training platform. The report records the observed slice recovery. Concurrent data cleanup limits causal attribution.
It has 29 words under the rule “trim, then split on whitespace”. Use the destination form’s actual counting rule and confirmed limit; 100 words is not a universal requirement.
Build one evidence table
| Claim | Artifact | Your ownership | Team ownership | Direct witness | Caveat |
|---|---|---|---|---|---|
| Slice evaluation and gate | Permitted report or labeled reconstruction | Benchmark design; gate recommendation | Platform and rollout | Direct observer, if available | Concurrent cleanup limits causal credit |
Add evidence kind: observed/estimated/unavailable, and disclosure: approved/restricted. Record unresolved failures separately.
Choose one contribution
Look for six properties: technical constraint, personal decision, available evidence, consequence, trade-off or learning, and role relevance. Unavailable evidence is a limit to disclose, not a reason to invent an artifact, witness, failure or numeric result.
The 100-word structure
Use five prompts within the confirmed limit: problem/constraint; personal ownership; technical mechanism; evidence; consequence or learning.
Change 1: The Report Is Confidential
New task. Original evidence cannot be shared.
Picture and change. Use approved sanitized architecture, a synthetic fixture or a precise verbal reconstruction; label its provenance.
Check. An unrelated public repository does not prove this private contribution.
Use when. Disclosure is restricted.
Change 2: The Reference Saw Only the Outcome
New task. A senior reference did not observe the decision.
Picture and change. Supplement with a direct observer if available; mark each person’s knowledge boundary.
Check. Title does not establish firsthand knowledge.
Use when. Witness coverage differs from the claim.
Common failure modes
Team work claimed personally, coordinated scripts and leaked evidence undermine verification rather than strengthen it.
Transfer Check
Must all three sources repeat the same wording?
Reasoned Answer
No. They should be factually compatible within their knowledge. Independent wording and honest limits are desirable.
Artifact selection
Choose the artifact relevant to the claim:
- Repository/PR: implementation.
- Paper/report/notebook: research.
- Design document: architecture/trade-offs.
- Benchmark/data card: evaluation/data.
- Incident review: debugging/operations.
- Talk/deck: communication.
- Product/demo: user value.
Prepare the verification path
Ask seven questions: What evidence exists? Observed or estimated? Team ownership? Personal ownership? Direct observer? Confidential details? Unresolved failure?
References are independent evidence
Choose direct observers and preserve independent judgment, not statistically independent measurements. Possible perspectives: manager for scope/reliability; peer for technical quality; cross-functional partner for collaboration; mentor for research judgment.
Ask permission before contact. Share accurate role, resume and project context; do not script praise. Keep names and contact details in private authorized storage, not public preparation artifacts.
What references may expose
Reconcile factual errors about ownership, metric context, reliability, conflict, causal credit or later growth. A changed recollection needs honest clarification, not synchronized accounts.
Preparation checklist
- Write within the confirmed statement limit.
- Verify every personal ownership verb.
- Attach an allowed artifact or labeled reconstruction, if available.
- Prepare the same decisions for the confirmed presentation duration.
- Build the claim/evidence table.
- Ask references; privately confirm contact details.
- Share which real work may arise.
- Reconcile factual differences across resume, deck, artifact and reference context.
Absence of a witness or artifact remains an explicit corroboration limit, not proof that the claim is false.
Related: present a technical ML project, your most ambitious project, and technical presentation practice.