|
|
|
|
|
by dekhn
1418 days ago
|
|
I;'d like to echo this. I learned a long time ago that I don't want to be a "machine learning engineer"- I have no interest in designing new networks, feature selection, or training as a daily job. I know how to do all those things but it's not somethign I pursued at Google. Instead, I found jobs where I could work with those people (often the ones doing the real state of the art research at scale) using my experience, in ML, data engineering, pipelines, and HPC. 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. |
|