4 ms·
I believe it was Apple who is really, really strict about that kind of thing (that is, contributing to open source while employed by Apple) (source is anecdotal
by Cthulhu_ 3y ago
I believe it was Apple who is really, really strict about that kind of thing (that is, contributing to open source while employed by Apple) (source is anecdotal, someone in the Go slack got hired by Apple and could no longer participate as actively in the space); how is Google that way, generally speaking?
Also, how do people get job offers for these high paid do nothing jobs?
I did get a recruiter email from Google the one time, I believe it was for the Google Docs / Workspace team, but it involved relocating to Germany and Docs didn't seem interesting to me, so I didn't take them up on the offer at the time.
- freeCandy 3y agoI've seen tons of very active projects under Google's GitHub org[1] that have the disclaimer "This is not an officially supported Google product" so I would take a guess that they have a much better policy on employees participating in OSS than Apple does. [1] https://github.com/google https://github.com/google
- PumpkinSpice 3y agoMost large tech companies essentially give a pass to new hires on their first eval cycle. Depending on your start date, you might be either outright ineligible for a rating, or the rating defaults to "meeting expectations," because the expectations for the first 1-2 months are for you to just learn the stack and get to know the team. If you hit the ground running, good for you, but your manager might face an uphill battle to justify anything other than "meets." For the next 1-2 months, you can probably keep making excuses. If your manager is paying close attention to new hires, they might object. But many managers are overstretched. Between office politics, planning, and all the ongoing "problem cases," they might simply not have enough cycles to watch your output real close. Even after your manager is fed up, it takes time to fire you. In part to avoid legal risks, HR typically wants to see a written plan first, giving you about three months to prove yourself. If you do nothing, that's usually the end of the road. But if you lift a finger and earn a passing grade, the timer essentially restarts. In fact, you're now your manager's success story, and they might be reluctant to admit they were wrong. And that's on average teams. If you end up on a dysfunctional team or on a project in turmoil, you might not even have to pretend. There's just no one who is close enough to your role and still cares about the result.
- raverbashing 3y agoOr: to participate in the cycle you need to be there for at least 6mo (or something like that) Of course, this doesn't mean you're fully off the hook during that time, while it is less informal and laid back, doesn't mean you don't have to deliver Especially in countries that have some kind of labour protections and limits on letting people go, this is important
- filoleg 3y ago> Depending on your start date, you might be either outright ineligible for a rating, or the rating defaults to "meeting expectations," because the expectations for the first 1-2 months are for you to just learn the stack and get to know the team. Just a small addition, starting from the beginning of 2023, all new hires get their first rating as OI (aka outstanding impact aka one rating higher than the target "meeting expectations"/"significant impact").
- yodsanklai 3y ago> But if you lift a finger and earn a passing grade Unfortunately, it takes more than lifting a finger to earn a passing grade. These companies are competitive and do fire low performers pretty easily, whether they are new employees or been there for a decade. The word goes that Google is more lenient on that regard though, I'd be curious to see some numbers.
- notpushkin 3y ago> how is Google that way, generally speaking? Haven't worked at Google so this is entirely my speculation, but: From the amount [1] of GitHub repos, with some things tangential to any current Google project [2], I think it's not too hard to get approval to do a project on company time. Maybe even contribute to a third-party one, totally unrelated to whatever you're supposed to do at Google. [1]: https://github.com/orgs/google/repositories https://github.com/orgs/google/repositories – 2.6k! [2]: e. g. https://github.com/google/sonic-midi https://github.com/google/sonic-midi, and I've seen a couple outright silly ones, though I can't remember the names right now
- cornel_io 3y agoGoogle generally approves almost any open source work. They're also really generous about approving even for-profit side projects as long as there are no conflicts and you're willing to wait for approval. I was cleared to work on a few side-project games while I was there. Re: do-nothing tolerance, the dirty secret at Google is that there's too little meaty work to satisfy all the people hungry to take it on, and everything takes ages to do anyways because of all the red tape, so it's kinda hard to tell who's phoning it in deliberately and who's getting stuck in the constant muck of cross-team approval and bikeshedding bullshit when they take 4x as long as expected to deliver half of what was promised (which mostly doesn't have any impact anyways). And managers are (were?) rated at least in part based on how many people they manage, not what their teams produce, so dead weight doesn't matter to most managers, if they're trying to get bumped up to director level the last thing they want is the distraction of having to PIP and then fire someone when they could just keep them around as padding and say they hit their staffing target...
- robertlagrant 3y ago> the dirty secret at Google is that there's too little meaty work to satisfy all the people hungry to take it on I think this is also a good reason behind 20% time. It's not to crowd source ideas, it's to keep smart people with the company.
- saagarjha 3y agoThe general policy is: ask, if it's not like an obvious competitor and you assign copyright to Google you'll probably get it approved. Trying to own the project is extra work.