in #leo15 days ago (edited)

Lessons learned from a Machine Learning Engineer:

  1. When looking for an ML position, is better to research about the industry in which the company operates than the ML title itself. A Computer Vision job can be hidden by a Software Engineer - C++ title.

  2. Training models is just a tiny task of your job. During this year, I had to focus more on infrastructure, performance and scalability than building and actual model. Plus I highly recommend to have a strong SW background for this, and it was surprisingly cool to learn.

  3. Keep it simple, there are a lot of Machine Learning tools that are accesible and easy to use. The challenge will come when integrating the tools/models into your company’s production pipeline.

  4. “It’s all about the data” did not apply to me this year. I see companies focusing more on Augmented Intelligence rather than Artificial Intelligence. As ML you might end up building tools for people to easily use ML rather than building ML itself.

  5. If you want to work with something specific, you might want to do that as a side project. Don’t wait until you get your desired ML position, you can start working on it from today!


Great points, interesting read. Keep up the good work. :)

Thank you!

Congratulations @aicoding! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :

You got more than 50 replies.
Your next target is to reach 100 replies.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out the last post from @hivebuzz:

Feedback from the October 1st Hive Power Up Day
Hive Power Up Month Challenge - Winners List