A new developer can receive a laptop and a welcome lunch yet still be unable to work because repository access, current documentation, and a first task are missing. A warm welcome matters, but a reliable path into the work matters more.

Key point HR should prepare access and shared guidance, while the engineering manager owns role clarity, learning, feedback, and the path to contribution. Connect administration, assimilation, and acceleration across the full 90 days.

Before day one: remove preventable friction

HR coordinates the contract, equipment, core accounts, working policies, and introductions. The manager confirms repository, issue tracker, staging, documentation, and development environment access.

Send a first-day schedule in advance and name the person who can solve access problems. Do not ask the new hire to discover ownership through trial and error.

Week one: build context and psychological safety

Explain the product, customer, architecture, team workflow, and why current priorities matter. Pair the developer with a buddy and make the manager available for a short daily check-in during the first week.

Choose a small production-relevant task with a safe blast radius. The goal is to learn the path from ticket to review and deployment, not to prove speed.

Days 1–30: learn how work actually moves

Set up recurring one-to-ones and clarify expectations for code quality, communication, review, incidents, and documentation. Ask the new developer to improve one confusing setup step so the onboarding system becomes better.

By day 30, look for a functioning environment, an understood delivery process, and one or more reviewed contributions—not mastery of the whole system.

Days 31–60: expand ownership with support

Move from isolated fixes to a small feature or operational responsibility. Continue design review and pairing where the system is risky, but let the developer own planning and follow-through.

Review whether access, team relationships, and role expectations are still blocking progress. Fix the system before treating a structural delay as an individual performance problem.

Days 61–90: agree on sustainable expectations

By day 90, the developer should be able to deliver a scoped change, explain important tradeoffs, and know when to ask for help. The manager and developer should agree on the next growth area and measurable outcomes.

Evaluate the onboarding process as well as the individual. Track time to first meaningful contribution, unresolved access issues, manager check-in completion, and feedback from the new hire.

Notes

  • Adapt the pace to role seniority, system risk, and the person’s prior context.