Engineer Onboarding: The Ugly Truth About Ramp-Up Time
Writing Tech Brief By HackerNoon
Audio is streamed directly from the publisher (media.transistor.fm) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
This story was originally published on HackerNoon at: https://hackernoon.com/engineer-onboarding-the-ugly-truth-about-ramp-up-time-7e323t9j.
Though people often think about the time it takes for a new engineer to start delivering value, they rarely ask themselves how long it takes for them to be fully ramped-up.
Check more stories related to writing at: https://hackernoon.com/c/writing.
You can also check exclusive content about #hackernoon-top-story, #productivity, #leadership, #management, #growth, #software-development, #remote-working, #onboarding, and more.
This story was written by: @Tom Ahi Dror. Learn more about this writer by checking @Tom Ahi Dror's about page,
and for more stories, please visit hackernoon.com.
Engineer Onboarding: The Ugly Truth About Ramp-Up Time. Swimm surveyed 80 engineers and engineering managers about their onboarding journey. They reported it takes, on average, 3–9 months to fully ramp-up. This could mean a great deal of extra engineering time for your organization. From the moment you find your estimated time, the next step would be to try and decrease it. The rewards can be very significant. If you manage to cut the time of full ramp up in half, that would mean around 17 more developer-years in that year.