A buddy covers what documentation and managers structurally can't: the unwritten context. How decisions actually get made, which channel to ask in, who owns what, why the deploy works the way it does — plus the social side of joining a team where everyone else already knows each other.
The role has boundaries. A buddy is not a second manager: no performance evaluation, no goal-setting, no reporting upward on how the new hire is doing. That separation is the point — the buddy channel stays safe precisely because nothing said there feeds an assessment.
What makes it work in practice:
- Named, not implied. "The team will help" produces nobody; a named buddy written into the onboarding plan produces ownership.
- Scoped. The buddy knows it is a few hours across the first weeks, front-loaded — and their project load reflects it.
- A peer. Close enough in role to answer the daily questions, experienced enough to know where the traps are.
For a services company the payoff is speed: new engineers often land on client projects within weeks, and a buddy shortens the path to the first confident commit while catching confusion before a client sees it.
In Helia, every 30/60/90 new-hire plan can name a buddy alongside the manager: the buddy is shown on the plan and sees it read-only, while milestones stay editable by the manager and HR — the channel is explicit without becoming an evaluator.