At one company I joined, my onboarding consisted of a laptop, a Confluence page titled “Getting Started,” and a Slack message saying “let us know if you need anything.” At another, I had a structured first week with an assigned buddy, a schedule of introductions, and a 30/60/90-day plan. The difference in how quickly I became effective was enormous, and it had almost nothing to do with the technical setup.

Most engineering onboarding focuses on the wrong things. Getting the dev environment running, merging a first PR, completing compliance training, these are necessary but they’re not onboarding. Real onboarding is about helping someone become a functioning member of a team, and that’s fundamentally a human process, not a technical one.

People, Not Technology

Marcus Blankenship makes this point directly: onboarding is about relationships, clarity, values, and processes, not just dev environment setup. It takes weeks to months, not days. The technical setup is the easy part. The hard part is helping someone understand how the team actually works, the unwritten rules, the communication norms, the decision-making patterns, the cultural expectations that nobody thinks to document because they’re “obvious” to everyone who’s already there.

Fournier extends this to mentoring new hires specifically: the job is to help them understand both the spoken and unspoken cultural rules, build their internal network, and feel like they belong. The technical knowledge will come. The sense of belonging is what determines whether they stay long enough to acquire it.

The Onboarding Buddy

The single most impactful change I’ve seen in onboarding programmes is the assignment of a dedicated buddy. Jean Hsu describes requiring that on the new hire’s first day, the buddy has a conversation making their priority explicit: “My highest priority is getting you up to speed, so even if I look busy, feel free to ask me questions any time.”

This dramatically reduces the barrier to asking for help. New hires are acutely aware of being a burden, and without explicit permission to interrupt, many will sit stuck for hours rather than ask a question that would take five minutes to answer. The buddy normalises asking for help and provides a safe first point of contact.

Larson adds practical detail: bring the new hire along to meetings, to lunch, and to meet other people. Don’t let them linger alone, especially in remote companies. Schedule daily time with them for the first several weeks, even if it’s just a quick check-in to resolve blocking issues.

Powerful Questions

Hsu also suggests asking new hires questions that most onboarding programmes never think to ask:

• “What would be your ideal onboarding experience?”
• “What’s a time when you felt really excited and motivated on a new project and team? What about it was most motivating?”
• “What does being supported at work look like for you?”

These questions do two things. They give you information about how to tailor the onboarding to the individual. And they signal that you care about the person, not just their output. That signal matters more than most managers realise.

The Welcome Document

Cris Concepcion describes creating personalised “WELCOME, {HUMAN}!” documents for each new hire, covering team information, first-week plans, 30-day and 90-day goals, people to meet, and resources to explore. The personalisation matters, a generic onboarding checklist feels like a process. A document written specifically for you feels like someone prepared for your arrival.

One thing Concepcion emphasises that I think is crucial: don’t make the goals feel like a test. Remind new hires that they passed an interview to get here, that you tested for competency in that process, and that they deserve to be on the team. They joined with aspirations, and the goals are there to help them achieve those aspirations, not to evaluate whether the hiring decision was correct.

Senior Hires Need It Most

There’s a counterintuitive pattern I’ve seen repeatedly: the more senior the hire, the more likely they are to want to skip onboarding, and the more they actually need it. Senior engineers and managers arrive with strong opinions and established patterns from their previous organisations. Without proper onboarding, they’ll default to those patterns, which may or may not fit the new context.

Larson is explicit about this: require all engineers and managers to attend onboarding regardless of level. The senior hire who says “I don’t need the basics” is exactly the person who needs to understand how this organisation does things, because their assumptions from elsewhere will lead them astray.

I’ve seen senior hires who skipped onboarding spend their first six months fighting against cultural norms they didn’t understand, alienating colleagues by importing practices from their previous company, and making decisions based on assumptions that didn’t hold in the new context. Proper onboarding would have prevented most of it.

What I’ve Seen Work Across Different Sizes

At a start-up with 20 engineers, onboarding can be informal but intentional. A buddy, a few key introductions, a shared document with context, and regular check-ins from the manager. The small team size means cultural integration happens naturally through proximity.

At a large corporate with hundreds of engineers, you need more structure. A formal programme with a curriculum, scheduled sessions, cohort-based activities, and clear milestones. But the principles are the same, relationships first, technical setup second, and ongoing support for weeks, not days.

The mistake I see at both sizes is declaring onboarding “done” too early. Merging a first PR is not the end of onboarding. Completing a checklist is not the end of onboarding. Onboarding is done when the person feels like a full member of the team, when they know who to ask for help, when they understand the norms, when they can navigate the organisation independently. That takes time, and it takes ongoing attention from the manager and the team.

The investment pays for itself many times over. Good onboarding reduces time to productivity, improves retention, and sets the tone for the entire employment relationship. Bad onboarding, or no onboarding, sends a message that the organisation doesn’t care enough to prepare for your arrival. And that message is hard to undo.