# Interview preparation sheet > Fill this in before EVERY interview, even the third one this week. > Takes 30 minutes. Best effort-to-result ratio in the whole process. ## The company - **Name / product:** - **What they sell, in one sentence a non-specialist would get:** - **Who pays (B2B, B2C, public sector, internal):** - **Size of the engineering team / of the front-end team:** - **Recent signals** (funding, acquisition, layoffs, engineering blog post, open roles): - **Advertised stack vs real stack** (job ads + blog + GitHub + StackShare): ## The role - **Title, and what it hides** (e.g. "full-stack" = 80% front-end? 50/50?): - **Why the role is open** (new, backfill, growth) — ask if not stated: - **Remote: their written policy, not their spoken promise:** - **Advertised range / target rate:** ## My three stories (ready to tell) > Format: Situation → what I did → outcome → what I learned. Two minutes each, max. 1. **A technical win:** 2. **A disagreement or conflict I handled:** 3. **A failure I own:** ## My questions for them > Ask at least three. They're what makes the end of an interview land. - How does code review work, and who has the final say? - What's the test coverage today, honestly? - Over the last six months, how much time went to technical debt? - What made the last person on the team leave? - What does a successful first three months look like? - Who decides prioritisation, and is front-end consulted before? - [Your product-specific question:] ## Logistics - **Date / time / duration / link or address:** - **Who I'm meeting** (name, role, what I saw of their profile): - **Announced next step:** - **Technical test planned?** Format, duration, paid or unpaid: