An interview proof point is defensible when it begins with a real artifact, distinguishes the candidate's decision from the team's work, and includes the limitation or tradeoff a technical interviewer is likely to test.
Select one artifact for one role dimension
Choose the strongest inspectable artifact for the dimension rather than the candidate's favorite project. Record the relevant repository path, diagram, incident record, specification, talk, or work sample and the exact claim it supports. Confirm that the candidate may discuss it. If the source contains restricted material, prepare a disclosure-safe description without copying details into the interview card.
Write the context in one or two sentences: the system, constraint, and problem at the time. Then identify the candidate's actual responsibility. Separate a decision they made from work they implemented, reviewed, proposed, or observed. This prevents a polished team story from obscuring the contribution the interviewer is trying to understand.
Connect decision, evidence, result, and limitation
Describe the decision or action, the evidence available at the time, and the artifact that records what happened. Use measured outcomes only when the source supports the number and scope. Qualitative results can be precise: a failure became reproducible, a protocol gained compatibility fixtures, an incident gained a recovery path, or a review rule moved into an executable check.
Add the main tradeoff, unresolved question, or thing the candidate would change. Harvard's interview guidance recommends preparing examples while remaining responsive to the question rather than reciting a script. A limitation helps the proof point stay conversational and gives the interviewer a real technical decision to probe. It should not be added as performative humility when the artifact does not support it.
Prepare challenge questions and source reminders
For each card, write two likely challenges: how do you know, what was your contribution, what failed, why this design, what scale, what tradeoff, or what would change in the employer's environment. Answer from the source, and mark any point that relies on recollection. The card should be a memory index, not a paragraph for the candidate to read aloud.
Reality Contact, LLC prepares the cards for Role-Fit Evidence Pack. The candidate checks every fact, practices in their own words, controls disclosure, and speaks for themselves. The cards do not impersonate the candidate, contact an employer, verify the underlying work, or promise a particular interview or hiring outcome.
Where the service stops
Reality Contact, LLC prepares the evidence document but does not give employment advice, verify work history, contact employers, submit applications, invent achievements, impersonate candidates, or promise outcomes. The candidate confirms every fact and citation, chooses what to use, controls all communications, and personally applies and interviews. This is candidate document preparation; it does not replace professional legal, employment, immigration, credential, or career advice. We do not promise interviews, offers, employer interest, factual verification beyond supplied sources, or a favorable assessment of any evidence or gap.
Sources: Harvard career guidance for interviewing; MIT Communication Lab resume and CV guide.