Behavioral & Leadership (50 Qs)•Part 3: Engineering Leadership, Code Quality & Collaboration (26 - 36)
What is your approach to technical onboarding and setting up new engineers for success in their first 30-60-90 days?
In Simple Words: Create a structured ramp-up plan with clear expectations, a designated onboarding buddy, and small early wins.
The 30-60-90 Day Plan:
- First 30 Days (Learn & Ship):
- Day 1: Working local development environment with
make dev-setup. - Week 1: Ship a small documentation fix or minor bug fix to production to experience the deployment pipeline.
- Month 1: Shadow on-call rotations and complete a mid-sized feature with an onboarding buddy.
- Day 1: Working local development environment with
- Day 31–60 (Own & Collaborate):
- Independently own a core feature from design to release.
- Participate actively in PR code reviews and secondary on-call support.
- Day 61–90 (Lead & Improve):
- Proactively identify tech debt, propose an RFC, or improve developer tooling.
- Begin onboarding or buddying the next incoming hire.
Practical Script & Summary Template
markdown
### Day 1 Onboarding Success Checklist:
- [ ] Access granted to GitHub, Slack, AWS staging, and Jira.
- [ ] Repository cloned and local server running on `localhost:3000`.
- [ ] Run test suite locally: `npm test` passes with 0 failures.
- [ ] PR #1 opened: update onboarding documentation or fix a typo.
- [ ] First deployment completed to staging environment.