I've been talking with a few customers about how they onboard new software engineers with Glean and I've notice a few important trends in how they describe Glean's impact:
- First, yes, they use Glean to onboard by building onboarding collections, by suggesting how to find help from HR, facilities, IT, etc. This can really accelerate onboarding
- Second, they use Glean to help new engineers understand engineering processes, best practices, and code examples. This gets new hires from start date to first PR about 30% faster.
- Third, it's not just new hires. Engineers are often asked to move between projects (products, features, etc.) as their work evolves. Glean can help them get up to speed on their new role or on new products more quickly than they could alone.
- Fourth, on-call engineers love Glean. They aren't always familiar with the areas of code they're asked to support when they're on call. This means, in the event of a production outage, the on-call engineer needs to "onboard" to a new part of the product in minutes. Glean really helps them get code context, but also helps them find out who the product SME is, what changed, related issues, etc.
So onboarding means a lot more than just getting new hires up to speed!
