How to create a 30/60/90 day plan for developers

A 30/60/90 day plan provides structure and clear expectations for new developers. Here's how to create one that sets your team up for success.

Why 30/60/90 day plans matter

For developers, the first 90 days are critical. A structured plan helps:

Set clear learning objectives
Measure progress and growth
Build confidence through achievable milestones
Identify support needs early
Align expectations between developer and team

The 30-day plan: Learning and orientation

Goals

Understand codebase structure and architecture
Set up development environment
Complete first code review
Attend all team meetings and standups

Key activities

Week 1:

Clone repositories and set up local environment
Review documentation and README files
Pair program with senior developer
Attend onboarding sessions

Week 2:

Fix first bug or small feature
Submit first pull request
Review codebase patterns and conventions
Understand testing approach

Week 3:

Work on slightly larger feature
Participate in code reviews
Understand deployment process
Learn about monitoring and logging

Week 4:

Complete first independent feature
Present work in team demo
30-day check-in with manager

Success metrics

[ ] Development environment fully configured
[ ] First PR merged
[ ] Can navigate codebase independently
[ ] Understands team's coding standards

The 60-day plan: Contribution and growth

Goals

Contribute meaningfully to team projects
Take ownership of features
Improve code quality and practices
Build relationships with team

Key activities

Weeks 5-6:

Own a feature from design to deployment
Write comprehensive tests
Participate in architecture discussions
Mentor or pair with other new hires

Weeks 7-8:

Tackle more complex problems
Optimize existing code
Contribute to technical documentation
Attend external meetups or conferences

Success metrics

[ ] Multiple features shipped
[ ] Code reviews demonstrate growth
[ ] Comfortable with team's tech stack
[ ] Actively participating in discussions

The 90-day plan: Ownership and impact

Goals

Take full ownership of features
Contribute to technical decisions
Mentor others
Identify and solve problems independently

Key activities

Weeks 9-10:

Lead a feature or project
Propose improvements to processes
Contribute to technical roadmap
Share knowledge through documentation or talks

Weeks 11-12:

Handle on-call responsibilities (if applicable)
Review and improve team processes
90-day performance review
Set goals for next quarter

Success metrics

[ ] Shipping features independently
[ ] Contributing to architecture decisions
[ ] Helping other team members
[ ] Identified and solved problems proactively

Role-specific considerations

Frontend developers

Learn design system and component library
Understand state management approach
Master build tools and deployment
Review accessibility standards

Backend developers

Understand API design patterns
Learn database schema and migrations
Master deployment and infrastructure
Review security best practices

Full-stack developers

Balance frontend and backend learning
Understand end-to-end workflows
Master both sides of the stack
Review integration patterns

Template structure

Here's a template you can customize:

## 30 Days: Foundation
- [ ] Goal 1
- [ ] Goal 2
- [ ] Goal 3

## 60 Days: Contribution
- [ ] Goal 1
- [ ] Goal 2
- [ ] Goal 3

## 90 Days: Ownership
- [ ] Goal 1
- [ ] Goal 2
- [ ] Goal 3

Tips for managers

Make it collaborative: Work with the developer to create the plan
Be flexible: Adjust based on individual learning pace
Regular check-ins: Review progress weekly
Celebrate wins: Acknowledge achievements at each milestone
Provide resources: Ensure access to documentation, tools, and support

Common challenges and solutions

Challenge: Overwhelming codebase

Solution: Start with one module or feature area, expand gradually

Challenge: Unclear expectations

Solution: Define specific, measurable goals for each phase

Challenge: Lack of feedback

Solution: Schedule regular 1:1s and code review sessions

Challenge: Imposter syndrome

Solution: Normalize learning curve, pair program, celebrate small wins

Conclusion

A well-crafted 30/60/90 day plan provides structure and clarity for new developers. It's not about perfection—it's about creating a roadmap for growth and success.

Remember to customize the plan for each developer's role, experience level, and learning style. The best plans are collaborative, flexible, and focused on building confidence and competence.