> Communication has been a bit rough with the Indian dev team<p>This is the first thing to figure out how to make acceptable. If you feel like they're not answering your questions well enough, you need to find a better way of doing this. Sometimes when there is a language barrier, it helps to have synchronous calls/video calls, where you don't give up asking questions until everything been made clear.<p>> I struggle with the complexity of it all given how a lot of dev processes are basically a black box where lots of stuff on the server is just done manually.<p>Second thing to solve, write and improve documentation! Currently, you're in a kind of nice place, where you're still learning the codebase with a fresh mind, so you kind of know what information is missing. But make it easier for your future new colleagues (and yourself!), and write down everything you learn in a structured way that is accessible to everyone in the company. Once available, you can even ask your other colleagues to try to fill out areas where you don't know a lot, then help them rewrite it once they've done their infodump.<p>Eventually, you will want to automate everything (at least deploys, testing and QA) they're doing manually on the servers/services, and documenting everything will make that step so much easier when you get there.<p>In the end, it seems like the existing dev team is somewhat of a silo, and I think you need to aim to make it not so, so they're more open to collaboration, unblocking you and documenting more.