# Presenting a 30-60-90 Day Plan in a Final-Round Interview Some hiring managers ask senior or client-facing candidates to bring a "first 90 days" plan. Done well, it shows that you understand the role better than the job description does. Done badly, it reads like a generic template. Here is a structure that stays specific. ## Days 1–30: Learn before you change things - List the people you would meet in week one (your manager, two or three peers, one internal customer) and what you want to learn from each. - Name the tools, metrics or codebase you would study first. - State one small, low-risk task you could finish to build trust, such as fixing a documented bug or updating an outdated onboarding page. ## Days 31–60: Contribute inside existing priorities - Pick one goal from the team's public roadmap or from what the interviewers told you, and explain how you would move it forward. - Say which process you would watch closely before suggesting improvements. ## Days 61–90: Own a measurable outcome - Commit to one result with a number attached, for example "cut first-response time on support tickets from 6 hours to 3." - Mention how you would report progress and who you would ask for feedback. ## Presentation tips 1. Keep it to one page or three slides. Interviewers want to discuss it, not read it. 2. Mark your assumptions clearly ("I assumed the team uses Jira; correct me if not"). It invites conversation and shows humility. 3. Finish by asking: "Which of these would matter most to you in the first quarter?" Their answer tells you what to emphasize from then on. A plan that cites what you actually heard in earlier rounds will beat a polished generic one every time. --- *Disclosure: I work on [Linkjob AI](https://www.linkjob.ai/), an AI interview assistant you can use to rehearse final-round presentations and follow-up questions.*