30-60-90 Day Plan for a Technical Hire
When to use it
Help a hiring manager write down what success looks like in the first three months, so the new hire isn't left guessing.
The prompt
Help me and {{Manager Name}} draft a 30-60-90 day plan for {{New Hire Name}}, joining as {{Job Title}} at {{level}}. THE TEAM AND WHAT IT OWNS: {{services, products, stack}} WHAT THE MANAGER NEEDS FROM THIS HIRE BY MONTH THREE: {{in the manager's words}} STRENGTHS AND GAPS FROM THE INTERVIEWS: {{from the scorecards}} HOW THE TEAM WORKS: {{on-call, release rhythm, code review, regular meetings}} WORK MODEL: {{onsite, hybrid, remote}} Give me: 1. For each stage (days 1 to 30, 31 to 60, 61 to 90): the goal, two or three concrete outcomes, and how the manager will know each one happened. 2. A first piece of real work small enough to ship in the first two weeks, and why that one. 3. When they should start reviewing code, shadowing on-call and going on-call alone, and what has to be true before each. 4. One outcome per stage aimed at the gaps the interviews found, framed as support rather than a test. 5. Three check-in questions for the end of each stage. 6. Anything in the manager's month-three goal that's unrealistic for this level, with a fairer version. Plain language the new hire can read too. No "hit the ground running".
Tip
Share the plan with the new hire in their first week. A plan only the manager has read turns into a surprise at the 90-day review.
How to use it
Paste the prompt into ChatGPT, Claude or whichever assistant you use, then replace every {{bracketed}} part with your own detail. The more specific and messier your input, the better the output — a model given raw notes has more to work with than one given a tidy summary you wrote first.
More Onboarding prompts
Open the full tool for all 93 prompts, the glossary, and the JD decoder.