Santiago Profile picture
21 Sep, 13 tweets, 4 min read
One issue I see with people applying for a job:

They struggle to highlight their experience in an effective way.

If you are trying to get a job as a Data Scientist or Machine Learning Engineer, here is something you can do.

The first step is to stop thinking of "experience" exclusively as a synonym for employment history.

Experience is about all of the work you have done. It doesn't matter whether someone else paid for it.

If you know how to get things done, you should highlight it.
The second step is doing some inventory.

I'm sure you can find examples and exercises you've solved over the past few months.

They don't have to be end-to-end applications. They just need to showcase your knowledge and ability to make things work.

Collect them all.
Curate all of these examples. Remove duplicates. Get rid of those that are either too simple or need too much context to be relevant.

Keep a shortlist with the examples that are relevant to the job you want. Each highlighting something unique and exciting.
Some people have mentioned that they don't have any code lying around.

If that's the case:

1. You aren't looking hard enough.
2. You indeed have not done anything.

If you are part of the second group, I'd recommend that you start building right away.
You don't have to overthink this.

Something you can do: Take every exercise from the course you just finished, and create a notebook for each of them.

Document the code. Document the purpose of the example.
The final step is about presenting all of this work.

There are many different ways to accomplish this, but I enjoy @DeepnoteHQ's profiles.

Here is mine: deepnote.com/@svpino/.

Look at some of the few examples I have in there.
You could publish all of the work on GitHub, but @DeepnoteHQ gives you something that makes a huge difference:

You can run your code right there.

People don't need to set up or download anything. With Deepnote, you can run your entire portfolio right from the browser.
As you learn and make progress in your career, build the habit of collecting your work in a single place.

Not only you'll be helping other people, but over time, you'll build an impressive profile that will be your presentation card for new opportunities.
As part of your resume, you can link to this portfolio of work.

Highlight some of the most relevant examples. Explain the reason you think they are relevant for the position.

Show, don't tell. This is the way you open doors.
Every week, I post 2 or 3 threads like this, breaking down machine learning concepts and giving you ideas on applying them in real-life situations.

You can find more of these at @svpino.

If you find this helpful, stay tuned: a lot more is coming.
Put together a collection of notebooks showing your different skills.

You can use projects you have worked on or develop different hypothetical situations that you solve in your notebooks.

When in doubt about what to include in this portfolio, ask yourself the following question:

Does this piece help establish my credibility and experience?

Remember, you can spin and talk until your face turns blue, but nothing speaks more than showing your own work.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Santiago

Santiago Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @svpino

20 Sep
When designing a machine learning model, remember the "stretch pants" approach:

Don't waste time looking for pants that perfectly match your size. Instead, use large stretch pants that will shrink down to the right size.

What does this mean for your model?
The "stretch pants" approach in machine learning:

Pick a model with more capacity than you need. Then, use regularization techniques to avoid overfitting.

You gotta thank Vincent Vanhoucke, a scientist at Google, for this analogy.
One example:

Imagine designing a neural network, and you configure a hidden layer that's too small (not many neurons.)

The network may not preserve all the valuable information from the data: you don't have enough power to do it!

Realizing this is difficult.
Read 4 tweets
18 Sep
In theory, you can model any function using a neural network with a single hidden layer.

However, deep networks are much more efficient than shallow ones.

Can you explain why?
If my first claim gives you pause, I'm talking about the Universal approximation theorem.

You can find more about it online, but the attached paragraph summarizes the relevant part very well.
Informally, we usually say that we can model any function with a single hidden layer neural network.

But there are a couple of caveats with this statement.
Read 12 tweets
17 Sep
I need your help.

The doctor tested me, and I came back positive for a disease that infects 1 of every 1,000 people.

The test comes back positive 99% of the time if the person has the disease. About 2% of uninfected patients also come back positive.

Do I have the disease?
To answer this question, we need to understand why the doctor tested me in the first place.

If I had symptoms or if she suspected I had the disease for any reason, the analysis would be different.

But let's assume that the doctor tested 10,000 patients for no specific reason.
Many people replied using Bayes Theorem to solve this problem.

This is correct. But let's try to come up with an answer in a different—maybe more intuitive—way.
Read 8 tweets
16 Sep
Next Friday, 50 tickets. I’ll help you getting started.

twitter.com/i/spaces/1Yqxo…
This is my first ticketed space. Only 50 people will participate, so I can make sure everyone gets their money's worth.

I don't think tickets will be on sale for too long, so don't wait if you want to participate.
I just found out that this is only supported in iOS. To buy a ticket ($2.99) you need to be on iOS.
Read 4 tweets
15 Sep
Imagine I tell you this:

"The probability of a particular event happening is zero."

Contrary to what you may think, this doesn't mean that this event is impossible. In other words, events with 0 probability could still happen!

This seems contradictory. What's going on here?
Yesterday, I asked the question in the attached image.

Hundreds of people replied. Many of the answers followed the same logic:

"The probability can't be zero because that would mean that the event can't happen."

This, however, is not true.
Let's start with something that we know:

Impossible outcomes always have a probability of 0.

This means that the probability of an event that can't happen is always zero.

Makes sense. But the opposite is not necessarily true!
Read 12 tweets
14 Sep
It was a different morning.

People woke up that day to an astonishing New York Times article: "New Navy Device Learns By Doing."

It was July of 1958, and for the first time, an electronic device showed the ability to learn.

It was called "Perceptron."
Frank Rosenblatt was born in New York and spent most of his life as a research psychologist.

Sleepless years of research culminated in his best-known work, which shocked the world and was billed as a revolution.

His machine, designed for image recognition, was able to learn!
Frank's ideas were the center of controversy among the AI community.

The New York Times reported about the machine:

"[the Navy] expects will be able to walk, talk, see, write, reproduce, and be conscious of its existence.

Bold claims at that time!
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(