Live data from Hacker News

What I learned getting acquired by Google

shreyans.org

151–160 of 645 posts

Re: What I learned getting acquired by Google

#151

The "red badge" thing was very real. It was really weird having TVCs on your team. You'd all work hard together to launch a thing, and then everybody except the red badge would get a celebratory team tchotchke or a team lunch or something. If you asked about it, the manager would say "we can't give Jim things directly because that might be like compensation and they'd be like an employee." There'd be all-hands meetin…

That's how it works with contractors in most large organisations. The other side of the coin is that they're usually rewarded better than employees are, on the basis that they can be fired at any time with no notice. In practice that rarely happens, as higher-pay => better-retention => becomes-most-knowledgeable-person-over-time.

Most large orgs don't have the perks of Goog, Meta. Amazon and Cisco don't have free food, massages, etc. so it doesn't matter contractor vs. fulltime.

Re: What I learned getting acquired by Google

#152

The "red badge" thing was very real. It was really weird having TVCs on your team. You'd all work hard together to launch a thing, and then everybody except the red badge would get a celebratory team tchotchke or a team lunch or something. If you asked about it, the manager would say "we can't give Jim things directly because that might be like compensation and they'd be like an employee." There'd be all-hands meetin…

That's how it works with contractors in most large organisations. The other side of the coin is that they're usually rewarded better than employees are, on the basis that they can be fired at any time with no notice. In practice that rarely happens, as higher-pay => better-retention => becomes-most-knowledgeable-person-over-time.

I've never seen a contractor have better salary/pay unless they're a fully independent subject matter expert and have no interest in being employed. I've hired a quite a few contractors and there is usually two cases, I need workers, or expertise that is highly limited.

Most contractors, not SME, are sourced from staffing agencies/partners. Sure, the resource cost is on par with a salaried worker, but typically the staffing company sourcing these people are going to take a huge chunk on that contract, at least 1/3. So yes, the resource/person is 280K on paper, but it's extremely rare they actually get paid that. The staffing agencies will provide benefits, but they're not even close to what in house staff are getting.

It also becomes nearly impossible to hire a contractor from partners in cases like this because you have to buy out the resource on the contract which is almost a non-starter because these fees can easily be 6 figures per head.

Re: What I learned getting acquired by Google

#153

Earlier quoted context omitted.

Gyms yes, pianos - only really big/fancy ones like MV, Zurich, London, etc

In my experience nearly every Google campus has a music room, and nearly all of them have at least a weighted keyboard. In the Bay Area there are a lot of acoustic pianos available. There's even a special building that has like 12 practice rooms, each with an acoustic piano.

Yeah i was thinking of full size acoustic ones since electronic keyboards are pretty common everywhere

Re: What I learned getting acquired by Google

#154

The "red badge" thing was very real. It was really weird having TVCs on your team. You'd all work hard together to launch a thing, and then everybody except the red badge would get a celebratory team tchotchke or a team lunch or something. If you asked about it, the manager would say "we can't give Jim things directly because that might be like compensation and they'd be like an employee." There'd be all-hands meetin…

Same at MSFT (I know because I was on both sides).

Re: What I learned getting acquired by Google

#155

Earlier quoted context omitted.

This isn't just google, it's every company with contractors and employees. Microsoft learned the hard way to not treat contractors like employees. https://www.reuters.com/article/businesspropicks-us-findlaw-... Nobody else wants to learn that same lesson.

Ok but then contractors have the freedom to work whatever hours they want, not show up to the office, and subcontract out their work - right? If so that might be more appealing than being an employee

Not in practice, because they use a hiring entity to dictate the terms. You're expected to show up on a schedule, do the work etc. much like a FTE, but you're not an FTE.

I think some folks have this illusion of software contractors that this is somehow common, it really isn't. The norm is you-are-almost-but-not-quite an employee type work environment, and thats at the better places.

I've worked at a place where contractors were treated like they weren't human, basically. Worst equipment, forced to work in an old warehouse that barely passed code to be considered retrofitted for an office, people routine got sick out there because they were exposed to the elements. Not to mention, during fire season (this was California) they were in a building that didn't have a good enough air filtration system, so they were forced to sit in smoke all day, more or less

I quit that place pretty quickly, but it was nothing short of terrible

Re: What I learned getting acquired by Google

#156
post #96

The "red badge" thing was very real. It was really weird having TVCs on your team. You'd all work hard together to launch a thing, and then everybody except the red badge would get a celebratory team tchotchke or a team lunch or something. If you asked about it, the manager would say "we can't give Jim things directly because that might be like compensation and they'd be like an employee." There'd be all-hands meetin…

thank you for mentioning this. i was a red badge. it was fucking demeaning. i have a lot of stories, but my favorite was when everyone on my floor got an earthquake safety kit except me. literally google didn't care if i lived or died. the expectation was that if i sucked up enough ("demonstrated my value") they MIGHT make me a real boy, like some bizarre Velveteen Rabbit fetish game. i loved watching how Google woul…

IBM basically invented this particular kind of caste shaming in a business organization. Hardly their worst crime, and they're still allowed to operate.

Re: What I learned getting acquired by Google

#157

Earlier quoted context omitted.

This isn't just google, it's every company with contractors and employees. Microsoft learned the hard way to not treat contractors like employees. https://www.reuters.com/article/businesspropicks-us-findlaw-... Nobody else wants to learn that same lesson.

Ok but then contractors have the freedom to work whatever hours they want, not show up to the office, and subcontract out their work - right? If so that might be more appealing than being an employee

> Ok but then contractors have the freedom to work whatever hours they want, not show up to the office, and subcontract out their work - right? If so that might be more appealing than being an employee

Depends on the agreement. First off, probably 99% of these contractors work for a contracting company, so as a contractor you have no say: You are an employee of (another) company and they'll set the rules.

If you're truly independent, then sure - try to make whatever agreement you want with Google.

Re: What I learned getting acquired by Google

#158
post #130
post #9

Earlier quoted context omitted.

Was it an aquihire?

That's an interesting word. I assume it's when a large company buys your startup just to have access to the talent, without much regard for the startup's product? What sorts of offers do they make to the founders?

Varies heavily depending on background labor market. In 2021: $1M+ per solid engineer. These days it's closer to $0 as they're not aggressively hiring and plenty of talent floating around.

Re: What I learned getting acquired by Google

#159

Earlier quoted context omitted.

Not at Google but I was a contractor at a hospital. All the employees got active shooter training. I guess the contractors were meant to be fodder.

No doubt there are some HR/legal folks wanting to avoid the liability of 'training' someone on something that goes badly. The workaround to that is to have the training in an auditorium and not keep attendance on who is in the room.

or mandate the contracting entity do the training. I've seen that in places that tried to be equitable about the relationship with their contractors.

Typically the business gets billed for the privilege though

Re: What I learned getting acquired by Google

#160
post #118

The "red badge" thing was very real. It was really weird having TVCs on your team. You'd all work hard together to launch a thing, and then everybody except the red badge would get a celebratory team tchotchke or a team lunch or something. If you asked about it, the manager would say "we can't give Jim things directly because that might be like compensation and they'd be like an employee." There'd be all-hands meetin…

For those unaware, these rules are pervasive in the US corporate world, and stem directly from Vizcaino v. Microsoft in 1996. See: https://en.wikipedia.org/wiki/Permatemp Effectively the fact that an employer treats a temporary employee "the same" as a regular one (i.e. by granting them the same perks) is construed by courts as evidence that they are not temporary . So, if a company wants to hire temp/contractor empl…

> Blame the courts, basically. It was a terrible decision, for exactly this reason. Its effect is directly contra to its intent.

Blame them for enforcing labor law? Why not blame the companies for exploiting labor by misclassifying them to deny benefits?

Post reply on HN