The prompt
Score 10 of 10, Excellent
Use it when An interviewer asked how you would approach your first three months, and you need a realistic plan built from what you know.
- {{role}}
- {{audience}}
- {{job_posting}}
- {{what_i_learned}}
- {{my_experience}}
- {{format}}
Full prompt and why it works
Prompt
Write a 30-60-90 day plan for the role of {{role}} that I will present in an interview to {{audience}}. The goal is to show I understand the job, will learn before changing things, and can deliver early results, so it should look realistic to people who know the team far better than I do. The job posting: """ {{job_posting}} """ What I have learned in the process so far (interviews, company materials, the brief for this presentation): """ {{what_i_learned}} """ My relevant experience to draw on: """ {{my_experience}} """ Format requested: {{format}} Produce: 1. The plan in three sections (Days 1 to 30: learn; Days 31 to 60: contribute; Days 61 to 90: improve), each with three to five specific actions and one measurable outcome. For example, an outcome with the right shape: "By day 60, own the weekly reporting pack with no corrections from my manager." 2. Assumptions: what I assumed about the team, tools or priorities, phrased so I can say "I'd want to check this with you." 3. Three questions to ask the panel at the end of the presentation, tied to the plan. Fit the length to the format requested. If none is given, keep the plan to one page, about 350 words, or five slides with a title and three bullets each. Base actions on the posting and what I learned. Do not invent the company's problems, numbers, systems or people, and do not promise big changes in the first month. A good plan does more listening early on and ends with specific, modest results by day 90. If I know little about the team's current situation, make the first 30 days heavier on discovery and say in the assumptions that the later sections would change once I learn more. If the brief asks for something specific, such as a focus on one problem, follow it over this structure.
Variables
- {{role}}
- The job title and company.
- {{audience}}
- Who you will present to, for example "the hiring manager and two team leads".
- {{job_posting}}
- The full job posting.
- {{what_i_learned}}
- What you know from interviews, the website, annual reports or the brief for this task.
- {{my_experience}}
- The parts of your background that matter for this role.
- {{format}}
- What the interviewer asked for, for example "10-minute presentation" or "one-page document". Write "not specified" if they did not say.
Why it works
- What good looks like. Each month ends in one measurable outcome, which is what panels look for when they ask for a 30-60-90 plan.
- What to avoid. It may not invent the company's problems or promise big changes early, the two things that make these plans look naive.
- If unsure. An Assumptions section turns every guess into a question you can ask the panel, which reads as judgment rather than a gap.