3 ms·
> I think at Google's scale one of the biggest pain points is almost certainly integrating new employees to do things "the Google way". Ramping up at Google is
by munificent 11y ago
> I think at Google's scale one of the biggest pain points is almost certainly integrating new employees to do things "the Google way".
Ramping up at Google is definitely a stressful process, but I don't think open sourcing technology puts much of a dent in that. Even if you show up your first day at work knowing every tool Google uses, on your second day there will be some new tool and something else will be deprecated. By a couple of years, damn near every piece of software you were familiar with will have been replaced by something different. You are in a constant state of learning.
This is, I think, one of the reasons Google places such a premium on algorithms and data structures in hiring. They are some of the few things that don't change often and being familiar with fundamental concepts makes it much easier to quickly pick up a new tool that uses them.
- datashovel 11y agoThanks for the insights. I can definitely see what you're saying from the perspective of a software engineer. I wonder if those same concepts translate over to onboarding people who might have a weaker programming background, such as mathematicians / theorists who may have a more difficult time making the switch. For example if they've been using the same toolset their entire careers. This last point isn't in response to your comment, but more a response to the ideas presented in the article. I don't necessarily buy the idea that the data is incentive enough to researchers at the top of their fields to leave what they're doing to go work at Google. Surely they have access to plenty of public datasets large enough to accomplish what they want to accomplish. So the requirement for switching tools may be a much bigger hurdle when trying to recruit for ML. Maybe I'm wrong in assuming they are targets for employment at Google.