30-60-90 Day Template Library
Select and customize onboarding goals for your new hires
Middle Software Engineer
Structured onboarding plan for mid-level engineers joining product teams. Focuses on codebase familiarity, architecture understanding, and first contributions.
Senior Software Engineer
Accelerated ramp-up for experienced engineers. Emphasizes technical leadership, system design, and cross-team collaboration.
Junior Software Engineer
Comprehensive foundation-building plan for junior engineers. Includes mentorship touchpoints, training modules, and guided first tasks.
Tech Lead / Engineering Manager
Leadership-focused onboarding for technical leaders. Covers team dynamics, stakeholder management, and strategic planning.
Your Path to Success
Welcome, Sarah! Here's your personalized 30-60-90 day roadmap
Productivity Ramp-up
First 30 Days
Foundation & Orientation
Days 31-60
Building Momentum
Days 61-90
Full Contribution
Days 31-60: Building Momentum Goals
Complete first significant feature independently
AchievedShip a user-facing feature from design to production with minimal guidance. Demonstrate full-stack capability.
- ✓ Feature requirement document reviewed and understood
- ✓ Code implemented, tested (unit + integration tests > 80% coverage)
- ✓ Pull request approved by 2+ senior engineers
- ✓ Feature deployed to production and monitoring set up
- ✓ Documentation updated (README, API docs, changelog)
Present technical design proposal to team
In ProgressLead a design review session for an upcoming feature. Practice communicating technical decisions and incorporating feedback.
- ✓ Design document created (architecture, data models, APIs)
- ✓ Review meeting scheduled with 5+ team members
- Presentation delivered with Q&A session
- Incorporated feedback and updated design doc
- Design approved by tech lead
Participate in on-call rotation (shadow mode)
AchievedShadow a senior engineer during on-call week. Learn incident response procedures and production troubleshooting.
- ✓ Completed on-call training module
- ✓ Shadowed 1 full week of on-call (responded to 3+ incidents)
- ✓ Created runbook entry for common issue
- ✓ Participated in post-incident retrospective
Contribute to cross-team initiative
In ProgressCollaborate with Product or Design team on a cross-functional project. Build relationships outside immediate team.
- ✓ Identified suitable cross-team project
- ✓ Attended 2+ cross-team meetings
- Delivered technical work that unblocks other team
- Received positive feedback from partner team
Conduct code review for 10+ pull requests
PendingActively participate in code review process. Provide constructive feedback and learn from others' code.
- Reviewed and approved 10+ pull requests
- Provided at least 3 substantial suggestions per PR
- Engaged in discussion threads on complex changes
- Received feedback from seniors on review quality
Progress & Alignment Dashboard
Track employee ramp-up against initial expectations
Manager & HR View
Initial Expectations vs. Reality
30-Day Milestone: Foundation
ExceededExpected: Complete environment setup, understand codebase structure, ship first bug fix
Actual: All goals achieved + proactively documented onboarding gaps
60-Day Milestone: Building Momentum
On Track (with notes)Expected: Ship significant feature, present design proposal, shadow on-call
Actual: Feature shipped ✓, On-call shadowing ✓, Design proposal in progress (minor delay due to scope expansion)
90-Day Milestone: Full Contribution
UpcomingExpected: Work autonomously on complex features, mentor junior team member, contribute to architecture decisions
Status: Not yet started
Manager's Observations
Sarah is ramping up faster than expected. Her feature work shows strong technical judgment. Consider accelerating to more complex tasks.
Positive engagement in team activities. No red flags in 30-day check-in. Team feedback is very positive.