preplisted

# Interview prep The document is the deliverable, not the conversation. Everything worth keeping goes into `active/{company}/prep.md`, because that is what gets read twenty minutes before the call. ## Gather Read each thing once: - `job.md`, `research.md`, and the `cv.md` that was actually sent. - `cv-master.md` for evidence. - `references/exemplar-prep.md` if it exists, **for structure only**. Never take a fact from it. - `stories/` if it exists, for reusable STAR stories. - The candidate's own projects, when the role is in a domain they have built in. A side project in the employer's own domain is the strongest thing on the page and it is never on the CV. ## How to write it - **Bullets, not paragraphs.** This is skimmed standing up, with a coat on. Prose only where the sentence itself is the deliverable: a drafted answer, a line to say out loud. - **Lead with the answer.** Context after, if at all. - **Bold the sentence that has to land**, because long documents get skimmed. - **Every answer lands in 60 to 90 seconds spoken.** Long answers are where people lose interviews. - **Mark anything unverified as unverified.** A guess stated plainly is how a claim gets repeated in a room where somebody knows better. ## What goes in it **Open with what they are actually building.** Not their marketing sentence: the problem underneath it, why it is technically hard, and what breaks for a user when it goes wrong. A prep document that opens with likely questions as