[jxm262]

This is literally opposite of me. Would you mind elaborating a bit on the negatives of working on the ML side of things?

Definitely not saying your wrong or that it's better than backend dev (it's probably just personal preference). But as someone considering it, I'd like to hear the good and bad of each type of role.

[drowning_sushi]

I too moved away from ML after actively pursuing it for many years. YMMV but here are my reasons

- Scientists dont always make the best 'clients'. The requirements you spend months implementing may be completely obsolete by the time you are done and then completely unused. - You often dont understand or are made aware of the impact of your work. - Its challenging to compete with Masters/Phd graduates who have spent years delving into ML. Entry-level knowledge only takes you so far. So its more likely that you wont work on cutting edge ML research. - MLE work in my experience has been mostly around infrastructure management and data security. Again it has interesting challenges and hard problems to solve but with the speed of the AI world, it all boils down to facilitating the scientists and researchers as much as you can

[bazmattaz]

Out of interest who led the team? Did you have a product manager? Ideally they should make everyone aware of the value of the work

[jxm262]

Thanks for sharing your input here.