|
|
|
|
|
by joshvm
1418 days ago
|
|
To add to this, companies at Google-scale tend to have a huge variety of ML related jobs, ranging from low level things like optimising libraries for different hardware, to the more general research positions where people are working on their own pet projects. Plus everything in between - data management and curation for training models that get used in production, people who try and figure out how to productionise cutting edge research, people who build the infrastructure that other ML engineers use (and here again, everything from hardware/server people, cloud, site reliability, tooling) and the list goes on. I know of at least one person who got an ML job at Google, but didn't apply specifically for it. They had a very strong ML background and applied for a generic software engineering and got team matched. That seems like a reasonable way to go if you don't want to go through a research interview loop. |
|
There is nothing quite like having a world-class researcher ask you to figure out why their model is exploding, and tracking down the crazy things that happen on TPUs when their math isn't absolutely perfect, then helping them fix it, and see them publish their results (or put them in prod). Or knowing enough software and hardware to debug a tensorflow TPU problem with an oscilloscope connected to the voltage regulator in a hardware lab.
Personally, i gained these skills over a long period starting in the mid-90s (working on machiine learning, and then later HPC for biology, and ultimately back to machine learning). But I am a slow learner. probably the shortest path is to get accepted to a major university and do really well in your ML and CS classes, then parlay that into a job in a FAAMG, then figure out what you want to do with all your skillz.