The one thing that's hurting your resume


Hey Reader

I am going to be honest with you.

Most resumes suck.

I've reviewed well over 100 resumes at this point, and it still surprises me how very intelligent people really struggle to craft a decent one.

No matter how good your grades are, or how many internships you had or even if you created a robot dog that can walk up walls, none of it matters if your resume is dogwater (pardon the pun).

I want to tell you the one most important thing candidates don't do, but it's something recruiters and hiring managers really want to see.

Are you ready for this?

ADD METRICS TO EVERYTHING YOU HAVE DONE.

I know. Mind = blown.

But being serious for a second, metrics, especially financial ones, make it so clear the impact you bring.

Whether you are a Principal Data Scientist, a non-technical recruiter or my childhood idol, Luke Skywalker, they all know what "with an estimated savings of $500,000 per annum" means.

I bet you are gagging to see an example?

Like a postman, I always deliver.

This is an example statement that is pretty subpar:

"Improved the accuracy of the recipe popularity forecasting model by using new features in the LightGBM model."

Yawn.

The issue with this is that it's so vague. Like, what does "improved" mean? What problem did you really solve?

This is a revised and much better version:

"Implemented a recipe popularity forecast machine learning model using LightGBM that improved the lead day 5 forecast by 33%, leading to £500,000 in annual food waste savings. The algorithm was deployed on AWS through lambdas and step functions."

It obviously is just better. It describes the specific problem solved, the technical implementation, and the impact on the business.

This is a framework you can follow:

  • State what you were analysing, predicting or modelling.
  • State the technologies, algorithms and statistical tools you used.
  • State the metrics you improved.
  • State the business value you generated.

Feel free to email me with your examples. I'd be happy to provide feedback!

Speak soon,
Egor

PS: It would mean the world if you filled out this short form to let me know which part of the data science and machine learning job process you are struggling with most.

Dishing The Data

Weekly emails helping you land a job in data science or machine learning

Read more from Dishing The Data

Hey Reader, The other day, a coaching client asked me: "When should I start applying for jobs, I still don't feel I have learned enough?" I get it. The last thing you want to be is sitting like a lemon when the interviewer asks you what linear regression is. Trust me. I've been there. Your hands go sweaty knees weak arms are heavy, you try to rattle your brain for an answer and you feel like a fraud. Maybe not Bernie Madoff running a $65 billion Ponzi scheme-level of fraud, but it's close...

Hey Reader, Let me cut to the chase. You clicked this email because you want to know the best resources for studying data science. Well, like Sergio Agüero scoring the last-minute winner against QPR in 2012 to win Man City their first-ever Premier League title, let me deliver. The amount of books, courses and guides on data science has exploded over the last few years. Some of them are good, and some of them are dogwater. So, how does a beginner decipher what is what? The truth is, there is...

Hey Reader, Let me be upfront with you. I have some correct controversial opinions: I don't think AI is "that" great, and it won't replace data scientists Logistic regression is a regression, not a classification algorithm Lord of the Rings is absolute dogwater (and yes, I have read the books) There is one more view that I have (don't worry, it's not LOTR-related for you die-hards here). I don't see why people care more about their Instagram profile than their LinkedIn page. Think about it...