evidence card

what a founder receives for each candidate: every requirement of the role, marked on whether the candidate understands it and has done it, with the source behind every mark.

each line ends in one of five results: shown, understands, thin, not there, or not assessed. a source sits behind each one: a quote, the stage of a situation the candidate reached, or a line of their code.

the card comes with an interview guide built from its gaps, and with the candidate’s cv exactly as they wrote it.

the evidence card, in the method · see sample cards

related terms

• not assessed: a result on an evidence card meaning the conversation never reached that requirement. it is different from “not there”, which means it was asked about and wasn’t shown.
• interview guide: questions built from the gaps on a candidate’s evidence card, so a founder’s interview goes straight to what the evidence didn’t settle.
• skill map: an engineer’s own record of the concepts they understand and the things they have done, each with the evidence behind it. the engineer sees it before any company does.