Rules for Interview answers

# Voice rules for Interview answers

19 rules apply on the Interview answers surface, 19 declared, 0 measured, 0 inherited and 0 proposed. No rule on this surface has yet been measured from attested writing, so this profile is the author's stated preferences and not a measured fingerprint.

## Never violate

- No emoji. Not in copy, not in headings, not in commit messages.
  Declared, enforced as a house rule in his codebase.
- Sentence case everywhere. No all-caps strings and no uppercase text styling.
  Declared, enforced as a house rule in his codebase.
  Exception: The resume surface is exempt for section headings only: the author's own master resume sets PROFESSIONAL EXPERIENCE, EDUCATION & AWARDS and PERSONAL in all caps, and the template convention wins there. Resume body bullets stay sentence case.
- Every number, quote and factual claim carries its source. An interpretive read is labelled a computed read, never dressed as a sourced fact.
  Declared, enforced as a house rule in his codebase.
  Why: The non-negotiable house rule. A claim without provenance does not ship.
  Exception: On the resume surface numbers ship without inline citations. The provenance duty still holds, it just lives off the page: every figure must be attested in the author's work record or a prior resume, and a figure with no attestation does not go on the page.
  Exception: On the interview_answer surface a spoken answer carries no inline citation. The provenance duty holds off the page: every figure must be attested in the resume bullet catalogue or in a prior interview answer, and the two are separate sources, so a fact attested only in a prior answer is sayable but is known to be absent from the resume.
- Never invent a figure, a name, a citation or a confidence level. An honest gap is stated as a gap.
  Declared, enforced as a house rule in his codebase.
  Why: Repeatedly enforced across his codebase: a missing structure is an honest visible gap, a fabricated one silently corrupts everything downstream.
- Write interview answers as short bullets with indented sub-bullets, never as prose paragraphs. One idea per bullet, detail demoted to the indent below it.
  Declared, stated by the author himself.
  Why: The answers are a script to be glanced at and spoken from, not read aloud. A paragraph cannot be found again mid-sentence under pressure; a bullet can.
  Good: * McKinsey, Feb 2023 to May 2025, the planned post-PhD tour
    * Two and a half years, healthcare and pharma strategy
  Avoid: McKinsey was the planned post-PhD tour, two and a half years in healthcare and pharma strategy, learning the toolkit at the highest standard.
- Every company-specific beat names the company actually being interviewed. Never carry a why-this-company answer, a named project, or a mission line across from a prior prep doc.
  Declared, stated by the author himself.
  Why: This has failed twice in the corpus, and it is the single highest-cost error on this surface: a recycled company name reads as a recycled candidate.
  Good: Rare disease is where data strategy has the most leverage, because the populations are small enough that every asset counts.
  Avoid: Atticus is where analysis converts most directly into help arriving.
- Every figure must be attested in the resume bullet catalogue or in a prior interview answer. A fact attested only in a prior answer is fair to say, and should be known to be absent from the resume so it is defended rather than pointed at.
  Declared, stated by the author himself.
  Why: The interview corpus is a second attestation source alongside the resume, and it holds real facts the resume never carried. What it does not license is a number that appears in neither.
- Use job titles exactly as they appear on the resume in front of the interviewer. Do not paraphrase a title into a description of the work.
  Declared, stated by the author himself.
  Why: A paraphrase costs a credential the interviewer is already reading, and invites them to wonder which version is true.

## Default, depart only with a reason

- Avoid the em dash. Use a comma, or split the sentence, or use "and". Depart only where the em dash genuinely earns its place, and say why.
  Declared, stated by the author himself, changed in the local delta layer by delta 4, 6.
  Why: Stated by the author as a hard rule for decks, and repeated as a house rule.
  Good: Breadth is the one axis rivals cannot buy, 78 of 137 classes against Enamine's 52
  Avoid: Breadth is the one axis rivals cannot buy — 78 of 137 classes against Enamine's 52
  Exception: This rule is about the EM dash used as a sentence connector. An EN dash joining a numeric range or a relational compound is a different character doing a different job, and replacing it changes the meaning, so "Phase 1-3" is a span and "Phase 1, 3" is two phases. Leave those alone.
  Exception: Downgraded from never-violate on 2026-07-28. In an internal share deck the author deliberately rewrote complying lines to use an em dash, so treat this as the strong default for CEO-facing work and depart with a reason elsewhere.
- Avoid the semicolon. Use a comma and "and", or start a new sentence. Depart only where two clauses genuinely belong in one sentence, and say why.
  Declared, stated by the author himself, changed in the local delta layer by delta 5, 7.
  Why: Stated by the author alongside the em-dash rule.
  Exception: Downgraded from never-violate on 2026-07-28. The author added four prose semicolons while editing an internal share deck, each one replacing a compliant construction, so this is the strong default rather than an absolute.
- Keep the visible sentence short and punchy, and push the supporting detail into a trailing parenthetical, usually "(e.g., X, Y)".
  Declared, stated by the author himself.
  Why: Stated by the author as the way to keep a dense line readable.
- Lead with the conclusion and the commercial consequence. Put method and technical detail after it.
  Declared, stated by the author himself.
- Behavioral answers run as labelled beats in sub-bullets: Situation, Action, Result. Add Task or Challenge only when it carries information the other three do not.
  Declared, stated by the author himself.
  Why: The author already writes this way; naming the beats keeps the result from being buried under the setup.
- Name a real gap once, plainly, with no hedge and no apology, then turn it into a question for the interviewer. This surface departs from the letters rule that leaves unmentioned gaps unmentioned.
  Declared, stated by the author himself.
  Why: A letter is read without a reply; an interview has someone across the table who will probe. A gap named first is a gap you framed, and the question that follows converts it into their information to give.
  Exception: This overrides the cover-letter surface's no-deficit-framing rule on this surface only. It does not license volunteering a weakness nobody asked about, and it never applies to a gap the posting lists as preferred rather than required unless the interviewer raises it.
- For tenure, employment-gap and why-are-you-leaving questions, name the question out loud first, then give the arc in chronological order, one stop per bullet, each with the reason for the move. Never invent a reason for leaving.
  Declared, stated by the author himself.
  Why: Short stints read worse when the interviewer assembles the timeline themselves. Saying the dates raise a fair question converts an interrogation into a narration.
- When the posting's bar sits above the record, concede the visible number first in plain terms, then add the part they cannot see. Never lead with the mitigation.
  Declared, stated by the author himself.
  Why: The interviewer has already done the subtraction. Leading with the mitigation reads as evasion; leading with the concession buys the second half a hearing.
  Good: In consulting and operating roles I am at about three and a half years. Before that I spent three and a half years at Michigan on computational modelling.
  Avoid: If you count my PhD I actually have closer to seven years of data experience.
- Close in the first person on his own credentials, three at most, then one sentence on why this role specifically. No comparisons to other candidates.
  Declared, stated by the author himself.

## Preferences

- Prefer a clause that carries itself over the "X: Y" colon-as-separator pattern. This is a preference, not a default, and his own writing uses the colon freely.
  Declared, stated by the author himself, changed in the local delta layer by delta 8.
  Exception: A colon introducing a genuine list is fine.
  Exception: Code, file paths, and key-value data are not prose.
  Exception: Downgraded from strong to soft on 2026-07-28. His attested MediSure deck uses the pattern 81 times in 2619 words, so on the evidence it is not a rule he follows. Weigh it, do not enforce it.
- Prepare six to eight questions as a menu, ask three or four, and keep one for last that invites the interviewer to name the assumption they would most want pressure-tested.
  Declared, stated by the author himself.
  Why: A menu survives a conversation that answers half of it unprompted, and the closing question hands the interviewer the first ninety days to describe.

## How to report what you applied

State that you used the Interview answers voice surface and repeat the honesty note above verbatim.
Do not say the output was style matched, voice matched or modelled on the author's writing. No rule here was measured from his text, so the accurate claim is that you followed his stated rules.
If you departed from a rule, say which rule and why, rather than leaving the reader to find it.