On day one, a new hire typically starts out in corporate onboarding. HR typically enrolls them in a training program or orientation to help them get acquainted with the company, its policies, and the basic outline of the position. Generally, corporate onboarding doesn’t contain the engineering onboarding that engineers need to understand their jobs. Yet, new hires are expected to “hit the ground running” immediately after this welcome packet is handed to them.
This is the status quo: a stack of forms to complete, a brief history of the company and its policies, a lot of new names to memorize and virtual hands to shake, plus a session with IT to set up email and other user accounts. Engineers frequently get a checklist of links to read and the instruction to work through it at their own pace (they promptly abandon the checklist just a few days in!)
This approach is failing engineering teams. New hires are left undertrained and disoriented, and the strain of their constant questions slows down more experienced team members. The velocity of the whole team dips for every new hire and multiple new team members increase the problem exponentially.
It takes a new engineer 7-9 months to become productive. What if you could cut that time down to just one month?
As crucial as it is to get onboarding right, tech companies often underestimate it. It's difficult to balance a growing engineering team with the challenge of keeping documentation up to date. For engineering managers, sometimes the first problem sign is a shipping delay.
See a demo of eddy in action.
80% of new hires complete Edify's onboarding plan in 4 weeks or less.
If you lead a technical team, chances are you've experienced the following:
Sometimes the problem is a gap in the design of the onboarding program - such as a new hire being given a list of logins without the context required to absorb the information. Often, it's incomplete or outdated documentation. Other times, it's the more experienced members of the team not having the bandwidth, time, resources, or motivation necessary to support them. Frequently, it's all of the above. All of this contributes to low time-to-productivity and eventually high churn - two painful and expensive propositions for engineering teams.
The cost in time and money of losing an employee and restarting the hiring process is enormous. For example — if new hires meet for two to three hours with each person on a team, and there are 10 new hires in a rapidly-scaling startup, that’s 50 hours spent on training… and this training is likely neither effective nor lasting. The cost to the company is about three times an engineer's salary. Engineering onboarding failures are estimated to cost the industry $22 billion a year.
Developer onboarding is the process of imparting the technical, process, product, and professional expectations you have for your new hires in a context and delivery that makes the information usable and actionable for your new hire. Gone are the long and often outdated checklists filled with links without context.
Engineering onboarding reduces stress and overload for managers by creating a consistent, repeatable, customizable process. Instead of starting from scratch with each new hire, finding the right people to connect them with, and doing a gut-check whether your onboarding info is still good, you're able to trust your workflow and update it - once - when necessary. Additionally, engineering onboarding:
Engineers take an average of 7-9 months to truly understand their role, the company, the product, and how they fit into it all. With an onboarding program built for engineers, your new hires reach this understanding in record time (often just 4 weeks!) while helping you get rid of the headaches for engineering managers and existing team members.
90% of managers have used eddy to audit their knowledge repo and prioritize documentation gaps.
Read more about engineering onboarding on our blog.