Be ready to explain core programming stuff to your not so technical and support background managers(multiple places not just One) reason to it is very simple people who join them with sound technical abilities usually leave early.
You have to take approval for each and everything be it your code design or architecture that too you first have to prepare formal documentation and get that approved from internal approvers(Its itself is chaos cause these approvers usually don't have a background of the problem in hand and there start coming with irrelevant ideas) before you reach your US Counter Parts.
Personal experience is that I almost spend 80 percent of my time doing documentation(sometimes it takes months to do actual code on an IDE ).
Be ready for getting your code reviewed from people who either don't code at all or been doing it in different technology. usually, it becomes problematic when you have to explain what even a naive developer of the same technology can understand, and then you might have to answer why it's taking so much time to get your PR Approved or why are so many comments on your PR.
Once you join them you may also be asked to switch your technology completely be it whatsoever is your experience and what your future aspirations are.
Your variable and Increments are purely based on your relation with your manager and not on your performance and how many times you played as sole showrunner or helped with the overall project milestones
People those never woked on respective technology are involved in the interview process and its service-based organization(once billable never goes out) so if you are coming at the lead or above technical roles then be assured to scratch your head if you get to work with those new hires as they can't even define a normal class in the asked technology and don't even know the very basics of the respective frameworks
