3 ms·
I have two recent perspectives about onboarding. 2018 - the company eventually grew to 60 people before getting acquired for 10x revenue. I was the then new
by scarface74 5y ago
I have two recent perspectives about onboarding.
2018 - the company eventually grew to 60 people before getting acquired for 10x revenue. I was the then new CTOs 3rd technical hire and the fifth technical person overall. He was bringing engineering in house. They were using an outsourcing company at first.
I onboarded myself, I scheduled a meeting with sales and the product owner and asked them questions as if I were a customer.
The CTO gave me a small project and I reached out to people when I had issues. It was much better than getting a brain dump. I learn a lot more by struggling through releasing a feature.
On the other hand, my next company was BigTech where there are standard corporate, division, subdivision and team specific onboarding.
They were both appropriate for the maturity of the company. But even in the latter case, I learned by struggling through a feature as part of my onboarding.
- spaetzleesser 5y agoThe problem in my company is that a lot of engineers are extremely reluctant to reach out to anybody. They barely reach out within their team and even less so to sales or marketing. For these people on boarding would be very helpful. And in larger companies it’s definitely useful to get an overview of how decisions are made, how processes work and so on. Otherwise you may work there for years and still not understand how things work outside your little box.