Project Context
Notion's Growth Engineering team is adding a new backend engineer to support a high-priority activation initiative scheduled to launch in 8 weeks. The team has 7 engineers, 1 engineering manager, 1 product manager, and 1 designer, and is already operating near capacity because two senior engineers are splitting time between roadmap work and production support.
The business goal is to make the new engineer productive quickly enough to take ownership of a meaningful part of the launch scope without slowing the rest of the team. Leadership wants a repeatable onboarding approach that reduces ramp time for future hires as the org scales.
Key Stakeholders
The engineering manager wants the new hire shipping code by week 2 while avoiding excessive mentoring load on senior engineers. The product manager needs the activation launch to stay on schedule. The tech lead wants high code quality and strong system understanding before the new engineer touches critical services. HR wants the onboarding experience to reflect well on the company and improve new-hire retention.
Constraints
- Timeline: 30-day onboarding plan, with launch in 8 weeks
- Budget: $12,000 for training, tooling, and documentation support
- Team capacity: only 10 mentor hours per week available across the team
- Technical environment: 14 internal services, incomplete documentation, and 6 open P1/P2 bugs in the activation stack
- Dependency: production access requires security training and approval, which takes 5 business days
Complications
- The designated onboarding buddy is going on vacation during the new engineer's second week.
- The activation project scope may change after an executive review in week 3.
- One critical service has no current owner and limited documentation.
Deliverables
- Create a 30-day onboarding plan with milestones, owners, and expected outputs by week.
- Define how you will balance onboarding speed against code quality and team capacity.
- Propose a stakeholder communication plan, including escalation points if ramp-up slips.
- Identify the top execution risks and mitigation actions.
- Define measurable success criteria for when the engineer is considered productive.
