674
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Mar 2024
674 points (98.8% liked)
Technology
55606 readers
2492 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Not sure how much of the fault is from Google's side here since the employees contracted from another company.
I am not defending Google here, but Cognizant is trash. I run a firm of specialist and a bulk of our work is cleaning up after outfits like Cognizant , Infosys, etc.
All that said, firing a group of 43 workers that chose to unionize during an Austin City Council meeting as it was being live streamed is all sorts of spicy. Google and Cognizant fucked up.
How's that work, is there lots of hair pulling? Or are you able to charge an arm and a leg and set your timelines because the clients don't have much of a choice?
This is all corpo speak for "they were cheap and their H1Bs were close to expiration"
It's no surprise, after all Cognizant is the first letter in CHWTIA. 🤭
Contractors at Google and other tech companies are typically treated and managed as real employees except for minor legal-motivated things like travel which is treated differently.
Further, contracts are typically for a fixed period of time.
That these employees/contractors seemed genuinely surprised by the abrupt termination suggests this was not the natural end of their contract. Google, not Cognizant, decides when their contracts end. If their contracts were terminated with no warning or reason given, it was initiated by Google. And with that background it seems pretty likely it was in retaliation to the union activity.
"But they're not Google employees", right? But then, that's why Google and other tech companies use contractors - to avoid giving those employees actual employee protections.
If the team is finding out that their job ends on the same day, it's totally Google's doing, and not the vendor company.
Google loves cheap, disposable workers, that why half of their workers are contractors.
I mean, if you're a contractor and they haven't discussed extending more than a month ahead of time, expect your contract to end on its end date. That's just common sense.
You assume the cognizant employees are privy to the contract terms.
That could be the case, in any case it wouldn't be Google fault, but Cognizant.
I've worked at two employers who used the contractor loophole. At the first one, the length of the contract and extensions were never mentioned to me ever. The second one constantly played games with extension. At one point I was set to have my final week of employment, only for them to extend it over the weekend.
I've been in the contractor shoes for way longer than I should have (which is zero), So as a hardfast rule, "expect your contract to end on its end date" simply doesn't hold up. Corps like to play games with it, and leave employees out of the loop.
They did tell these employees to not worry about their contract ending, that it would be extended.
The National Labor Review Board ruled that Google was a co-employer of these union members and, thus, ruled that both Google and Cognizant had to come to the table to hammer out a bargaining agreement with them. Google refused. When this council resolution was put forth, Katherine McAden of Google Austin emailed the Austin City Council members on 02/28/24 to ask them to postpone the vote to "give Google, and the City Council, time to fully understand the direction of this item and potential local outcomes." The very next day (02/29/24), while two members were in the middle of testifying to the council, that was the exact moment Google fired the lot of them.
I don't see how much more open and shut you can get here.
Thank you for this. This should be the top comment.
I wonder how the new Cemex framework affects this.
Lol corporate world is not for you my guy. They contract other companies specifically for this reason. Order cognizant to fire workers and when questioned , oooohh they were contractors. 🤷♀️
At least in the UK, if you work like an employee enough, the court can overrule the technicality of your employment status as a contractor and apply labor law protections.
This is exactly what happened with these union members. The National Labor Review Board ruled that Google was a co-employer along with Cognizant, and they ruled that Google just come to the bargaining table with these union members. They refused. They emailed city council members asking for a postponement of their vote to give them time to sort stuff out, and it was granted. The very next day, the fired the entire union out of retaliation for speaking to the city council voicing their concerns.
You have any idea the wide spread feelings on this?
It sounds like that's what we should be doing in more countries,.US.
Oh the US has tried to fix this issue multiple times. The end result was many of us getting laid off after 18 months every time because they couldn't extend our contacts any further by law. There's no reason for a company to convert a contractor if they're not required to.
that's because they keep going at it from a timeline POV; I believe if they made required work time slots as a limitation against contract work (i.e if you are required to work between x-y daily) this issue would be resolved. There's no real reason for many contract positions to be a static time slot, contractors are supposed to be fully flexible on their own time as long as the end product is correct and within SLA, thd only benefit to fixed scheduling is management level, so I think that would tip the scale onto employee instead of contractor
That's really only true for independent contractors, not W2 contract work to be fair. And every 1099 contract I've worked I've always clarified that stipulation in writing. In the interest of working together I do agree to be on daily or semi daily standups to allow progress.
Yeah, it's frustrating when people in turn can't find good medical insurance.
The trade for sometimes higher pay or flexibility in assignments doesn't work when you can't afford insurance or other benefits.
Assuming you were even being paid about permanent positions.
Yeah it's really frustrating. I'm fortunately at a level where the contracting companies have to provide at least decent benefits to get employees. But contracting sucks. Often you're restricted in what you can do, causing unnecessary delays to getting software done at the rate the company wants.
I've been yelled at by upper management for not doing something I legally wasn't allowed to. No apology when an employee on the call pointed it out of course.
It's a shit show. But my market is fucked right now so I'm about to go get a job at a grocery store or something and figure it out I guess.
Good luck to you.
Those work situations are the worst. It reminds me of the saying "you can be right, or you can get what you want, but not both".
You can correctly assert your contractor status and correctly point out that you're not legally allowed to do a thing. You're in the right, no doubt, but that doesn't stop an unhappy executive from "letting you go" anyway.
On the books, that is the case in the US too but it is almost never enforced
Contactor staffing companies exist solely to get around employment regulations. Demonic industry
Blaming another business? Hmmm. Sounds like Boeing's attempted solution.