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 2 years ago

MODERATORS

communick@academy.garden

Data Scientist to Machine Learning Engineer - Do I Need a Portfolio [D] (alien.top)

submitted 2 years ago by Fiboniz@alien.top to c/machinelearning@academy.garden

2 comments fedilink hide all child comments

With 7+ years of experience in data science and data analytics roles, would it be necessary to create a portfolio to begin applying to Machine Learning Engineer positions? If I already have the experience using sklearn/tf/keras/etc. in my current role of >2 years, how important is a portfolio when applying to these MLE roles?

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

[–] d84-n1nj4@alien.top 1 points 2 years ago (1 children)

Start contributing to GitHub repositories like tinygrad. If you have the skills of an ML engineer, you can make these contributions. Your work will speak for itself.

[–] SmolLM@alien.top 1 points 2 years ago

This is a joke, right?