What to Do in Your First 90 Days After Landing the Job

Why the first 90 days matter

Your first 90 days set the tone for your entire tenure. They're about learning, building trust, and showing impact. Rushing to change everything can backfire; listening and asking good questions usually pays off. Research on onboarding shows that employees who build relationships early and deliver at least one visible win in the first 90 days have higher retention and faster promotion. A 2021 SHRM report found that structured onboarding improves 3-year retention by 58%. The goal isn't to prove yourself overnight—it's to show you're learning, contributing, and fitting in. This guide gives you a practical 30-60-90 framework and common mistakes to avoid. You used ClavePrep to land the role—now use the same preparation mindset to make a strong start.

The first 90 days set the tone

Your first 90 days are about learning, building trust, and showing impact. Rushing to change everything can backfire; listening and asking good questions usually pays off. Research on onboarding shows that employees who build relationships early and deliver at least one visible win in the first 90 days have higher retention and faster promotion. The goal isn't to prove yourself overnight—it's to show you're learning, contributing, and fitting in.

Learn the system and the people

• Codebase and processes – Get a mental model of how the product works, how code is reviewed, and how releases happen. Pair with teammates and read docs and tickets. Ask "How does X connect to Y?" and "What's the history behind this decision?"

• Stakeholders – Identify who depends on your work and who you depend on. Schedule short 1:1s to understand their goals and how you can help. Don't wait for them to reach out—proactively book 30 minutes with your manager, key peers, and cross-functional partners.

Deliver early wins

Pick one or two achievable goals: fix a nagging bug, improve a runbook, or own a small feature. Ship something visible and document what you did. It builds credibility and gives you something concrete to talk about in your first review. Avoid "boil the ocean" projects—small, high-impact wins matter more than grand plans that take six months.

Stay curious

Ask "why" more than "how." Understanding context and history will help you suggest better solutions and avoid repeating past mistakes. Your interview prep with ClavePrep got you in the door—now use the same curiosity to ramp up and add value.

A practical 30-60-90 framework

Days 1–30: Listen, learn, map. Focus on understanding the system, the people, and the priorities. Take notes. Ask questions. Don't propose big changes yet.

Days 31–60: Contribute. Pick one or two small wins. Fix something. Improve something. Build relationships. Start to form opinions based on what you've learned.

Days 61–90: Own. Take responsibility for a larger area. Propose improvements. Show you've absorbed the context and can add value. Document your wins for your first review.

Common mistakes to avoid

• Changing everything immediately – You don't have context yet. Listen first.
• Staying silent – Ask questions. Show you're engaged.
• Overcommitting – It's better to under-promise and over-deliver.
• Skipping 1:1s – Relationships matter. Invest in them early.

ClavePrep helped you land the role—now bring that same preparation mindset to your first 90 days. Good luck.

Research on onboarding

Studies on onboarding show that structured onboarding improves retention and performance. A 2021 report from the Society for Human Resource Management found that employees who complete a structured onboarding program are 58% more likely to remain with the organization after three years. New hires who receive clear goals and feedback in the first 90 days ramp faster and report higher job satisfaction. The 30-60-90 framework isn't just advice—it's backed by evidence that early clarity and early wins matter.

What your manager is watching for

In your first 90 days, your manager is assessing: (1) Can you learn quickly? (2) Do you ask good questions? (3) Can you deliver something tangible? (4) Do you fit the team? (5) Are you proactive or do you wait to be told? Show learning through your questions. Show delivery through your wins. Show fit through your relationships. Show proactivity by volunteering for tasks and following up without being asked.

Building your internal network

Your success isn't just about your manager—it's about your peers, cross-functional partners, and stakeholders. In the first 30 days, aim to have 1:1s with: your manager, your direct teammates, 2–3 people you'll work with closely (e.g., design, product, support), and someone in leadership if possible. Ask: "What do you wish you'd known when you started?" "What's the most important thing for me to understand about how we work?" "How can I help you?" Take notes. Follow up. These relationships compound over time.

When things go wrong

Not every first 90 days is smooth. Maybe you miss a deadline, misunderstand a requirement, or clash with a colleague. How you handle it matters: acknowledge the mistake, own it, learn from it, and adjust. Don't hide or blame. A single mistake rarely defines you—how you respond does. If you're struggling, talk to your manager sooner rather than later. "I'm finding X challenging—here's what I've tried. What would you suggest?" shows maturity and initiative.

Transitioning from interview prep to onboarding

You used ClavePrep to practice answering questions, structure your stories, and build confidence. Now use those same skills: ask questions (you practiced "questions to ask the interviewer"—now ask them of your team), structure your updates (STAR works for status updates too), and communicate clearly. The preparation mindset you built for interviews carries over into your first 90 days.

For more on interview prep, see our behavioral interview guide and how to answer tell me about yourself.

The 30-day deep dive

Days 1–10: Map the system. Read docs, explore the codebase, shadow teammates. Ask "How does X connect to Y?" and "What's the history behind this?" Take notes. Don't propose changes yet.

Days 11–20: Identify quick wins. What's a nagging bug? A missing runbook? A small feature that would help? Pick one or two and ship them.

Days 21–30: Build relationships. Schedule 1:1s with key stakeholders. Understand their goals and how you can help. Document what you've learned. Share a brief "what I've learned" summary with your manager.

The 60-day contribution

Days 31–45: Own something. Take responsibility for a feature, a process, or an area. Propose an improvement based on what you've learned. Get buy-in and execute.

Days 46–60: Expand impact. Help a teammate. Improve documentation. Fix something that's been bothering the team. Show you're a net positive.

The 90-day ownership

Days 61–75: Propose and lead. "I've noticed X. I propose we do Y. Here's the plan." Take initiative. Get feedback and iterate.

Days 76–90: Document and reflect. What did you achieve? What would you do differently? Prepare for your first review. Share your wins with your manager. Set goals for the next quarter.