管理员
- 积分
- 77025
- 大米
- 颗
- 鳄梨
- 个
- 水井
- 尺
- 蓝莓
- 颗
- 萝卜
- 根
- 小米
- 粒
- 学分
- 个
- 注册时间
- 2009-5-28
- 最后登录
- 1970-1-1
|
ML product engineer - use well known algorithms, leverage relatively mature ML infra, and build ML into product, mostly working on feature engineering, could train using mature methods, "use" inference (instead of optimizing inference deep into the stack), track results maybe via AB test. Output is measured by lift in product metrics. Highest expertise is not in deep knowledge in modeling, but in software engineering - "can ship sth to production" is the most important.
ML infra engineer - build ML infra, does not focus on modeling, but should be deeper in the stack, more like engineer than scientists. Most likely not even remotely like scientists. often works with distributed systems, has deep knowledge about data infra, sometimes hardware (if deals with inference on the edge). Can help other teams work better is the most important.
ML scientist - work on new algo (new algo), would read papers, often write papers, output is measured not by publication but often by some product related metrics. Need a solid foot in product domain, and another foot in fairly deep ML algo. Many of them work on search ranking, recommender systems etc. Can build prototypes, and can help engineers develop models that move product in the right direction is the most important.
research scientist - cutting edge research, output is measured by publication. Most important: advancing the field. |
|