Machine Learning

1 readers

1 users here now

Community Rules:

Be nice. No offensive behavior, insults or attacks: we encourage a diverse community in which members feel safe and have a voice.
Make your post clear and comprehensive: posts that lack insight or effort will be removed. (ex: questions which are easily googled)
Beginner or career related questions go elsewhere. This community is focused in discussion of research and new projects that advance the state-of-the-art.
Limit self-promotion. Comments and posts should be first and foremost about topics of interest to ML observers and practitioners. Limited self-promotion is tolerated, but the sub is not here as merely a source for free advertisement. Such posts will be removed at the discretion of the mods.

founded 11 months ago

MODERATORS

communick@academy.garden

[D] What are your duties as a Machine Learning Engineer? (alien.top)

submitted 10 months ago by Judessaa@alien.top to c/machinelearning@academy.garden

11 comments fedilink hide all child comments

Please elaborate on this.

Including your role at the company, your day to day tasks, tools and languages you’re using.

Thank you in advance!

you are viewing a single comment's thread
view the rest of the comments

[–] bimtuckboo@alien.top 1 points 10 months ago (1 children)

Acquire necessary data (scraping, processing into useful format storing somewhere accessible i.e. cloud storage or local hard drive) python, requests, pandas, google cloud storage.
Prepare training dataset (feature engineering, usually process into csv) python pandas, sometimes random external libraries sometimes in other languages.
Design initial model architecture, get training to actually work usually involves a lot of debugging. All in jupyter notebook using pytorch, local if possible else on gcp
Evaluate model, loss + accuracy good to confirm model is learning and sanity check but mostly this involves using the eye test in a real world scenario so build poc product integration at this stage (usually python web api and some frontend for interacting either python desktop app or js web app just running locally)
Iterate 3 + 4 until model is good enough for prod.
Implement prod deployment usually python web api often get frontend specialist involved at this point to handle any potential frontend integrations.
Maintain prod integration as bugs come up and new features are requested. Also continously eval model performance (depends on domain).
Come back a year later and work through the whole process again adding incremental improvements to each step.

That's the usual life cycle of a project for me personally. Could take anywhere from 1 week to 3 months to get to working prod implementation depending on the project. Any longer than that and need to seriously reevaluate the approach.

Basically just regular software engineer dutues plus ml stuff.

[–] chulpichochos@alien.top 1 points 10 months ago

All in jupyter notebook using pytorch

Jupyter seems like an awful environment to debug anything, no?