I've found the bane: If your company pays for co-pilot with MS Teams (it's more likely than not),
enable copilot and transcription during the call. refuse to turn it off as you 'need it to take notes'. They might say it's not necessary for a quick question, but you can insist with any number of quick excuses. 'I need to track where my time goes', 'i summarize all calls, even the short ones', etc. If they call me on slack, I immediately decline, and call them on teams. Make excuses- dirty ones if needed. "my microphone doesn't work on Slack / Discord / whatever, let's use teams"
Every time they see the little AI notification pop up, you can tell by the way that they speak that they're much more nervous. number of 'quick calls' has been cut in half, easily.
I have the same experience. These locusts have been infesting every crevice of tech and you can expect to have to 'collaborate' with offshore teams in most places. They do these 'quick calls' asking you to do their work for them, or demonstrating they have no idea what they're working on and trying to push the responsibility onto you.
If you're doing interviews for tech jobs, I would heavily, heavily advise that you ask 'Will I need to manage offshore resources?' or any variation thereof. Do not directly mention India or Indians, offshore means jeets 99% of the time.
You can assume that if you're dealing with anyone that has a jeet name, even if they're onshore, that you'll have to deal with unhinged jeet behavior. One example I can think is a pajeeta project manager I've had to deal with. All this bitch did was constantly pressure engineers to ship features that were sold to clients without any input from the non-jeet engineers, with completely insane timelines. What would often happen is that the other jeets clientside would not provide proper documentation, it would lead to delays, and the jeeta would repeatedly harass engineers to ship in this timeline that was never feasible to begin with. We've had to chat with the non-jeet engineers off work to devise how to deal with this shit.
Among other things:
- One of the engineers was written up to HR because he didn't reply to the pajeeta within 15 minutes for something that was absolutely not urgent and could have waited for a daily scrum.
- This business insists on having these daily scrums including the offshore jeets. The jeets never turn on their cameras and never say anything other than "Yes" and "I understand".
- The jeets will avoid interacting with the pajeeta project manager in any way.
- The pajeeta would try having these "quick calls" over slack with the engineers, the engineers stopped taking these calls. Nothing good ever came out of those.
- Any communication with the pajeeta would result in her going "So you have everything you need then, you can ship yesterday". She had 0 understanding of any aspects of the projects
- The pajeeta pressured on-shore engineers to present slide decks to clients they had 0 input on an hour before a client call. Often the slide decks were full of typos and nonsense.
These shit eater checklist checking jeets don't bring anything positive to a project. I'm looking to leave tech in the next 5 years, there's pressure to constantly upskill off work because the work corporations ask you to do prevent you from furthering the skills HR/Hiring departments want you to have, having to deal with jeets daily mentally drains you, and the constant looming threat of layoffs makes it impossible to have any sort of stability.
I think that's partly why everything is becoming a "service", I'm talking Google Cloud Platform, Amazon Web Services, Microsoft Azure, Oracle Cloud, IBM Cloud. These companies think they can compartmentalize everything in such a way that even moronic jeets can work it. I've had to deal with jeets who have these platforms certifications and they don't seem to know the first thing about architecture, it's all quite strange.
than "horrifying" reacts because I feel everyone's pain being forced to experience that.
