Remote for many years. Gitlab has some good materials for remote, async organization. Some suggestions:

    * formal onboarding guide checked in with the code. New people should be fixing errors and pushing patches to it as they go. The guide should cover all the logins and services, dev process, how to build and run the product, etc.
    * frequent 1:1 from boss and tech leads the first month
    * online social event to meet the team, bs, maybe play a game
    * automation in ci to build and test product for anyone to hit the button
    * maintain curated culture for faqs, problems, shared scripty bits. wiki, private SO, shared repos, etc
    * maintain SOP documents for common operations like making a release