Context Of Company
This is a really well funded company (Bank) that underwent a large scale leadership change. The company's primary source of revenue was never it's tech capabilities, however with the new leadership change they're looking for a large scale revamp on how the existing systems work and are working on setting upto a FAANG equivalent engineering environment. This is vision is consistent across the leadership upto the CEO. This org currently consists of multiple Staff engineers from Twitter, Meta, Amzn and Google leading big initiatives.
Personal Context
I'll be soon taking up an offer in this company and will be joining this freshly created Org, where I've opportunity to be among the first 10-15 engineers to join with potential of the org to grow over 100+ engineers. There are lot of existing tech that have been already deemed unscalable due to previous decisions and have been a known business blockers, these tech require either re-write or a large refactor or a completely different viewpoint on tackling this problem. This will involve me working with Engineers who've built this system (Not part of this new Tech Org, rather the old existing infra), I've been already given a heads up from my potential manager that there can be potential hesitancy that the existing engineers may feel and wouldn't be too open to provide all information necessary as our systems will be replacing their soon (Have been reported that this has happened). There isn't a concept of internal wiki similar to Amazon or other Big Tech, hence lot of this is just domain knowledge etc. Fortunately the leadership is aware of this and is taking steps to answer this, and takes into consideration when scoping for projects and setting up right expectations.
The following are certain concerns that I've, and wanted to understand what is the best course of action I can take up to make my onboarding successful.
This is my Current plan, given i'll be among first engineers to join this team.
Understand domain, reach out to multiple PMs and document all pain points, problems we are solving in long term & Short term.
Go through code base of relevant packages and start adding their UMLs, HLD etc to best of my abilities to a document to move towards creating a Knowledge base.
Socialize with engineers from the related org and try to gain their confidence, and potentially get few KT sessions (Not sure how i'll go about this as the team is situated in different city).
Work with manager to setup boy-scout rule, such that everyone onboarding will incrementally add more to the existing knowledge base.
Follow Up Questions :
I still haven't taken up the offer yet and still have a week before I can respond. The increase in pay and the growth opportunity in the new company is significantly big, I can see myself reaching Sr.SDE in < 2 years and Staff in < 4 years there due to the problem space being so fresh and getting a really early head start. However, I'm slightly concerned if the lack of co-operation from other org and lack of documentation, and the fact that the entire org is being setup fully freshly could be a concern. What's the best course of action i could take to minimize this risk?
Second, one would view moving out from FAANG to a not well known company as a downgrade, would this still hold true if the problem space and opportunities in the new company is more complex?