The Positioning Mistake That's Killing Your Data Career


Last week, I cringingly looked back at my old email posts from 2022, as I prepared to migrate to my new email list provider. The experience has been eye-opening.

What struck me most was that they all seemed so… random.

For example:

  • What Robodebt Teaches Us About Responsible AI
  • Business Lessons From “Succession”
  • How to Avoid the Robopocalypse
  • Design Principles for Data Science (from the Victorian Government’s Digital Strategy)

It wasn’t terrible content, by any means.

But unless someone specifically needed an assessment of the Victorian Government’s Digital Strategy, it was more “nice to have” than anything else.

Looking back, it’s unclear exactly what value I offered readers, because back then, I was unclear on what value I offered them - except, of course, “data science advice.”

In case you’re interested, you can see the complete archive here: https://genevievehayes.kit.com/

Here’s the thing…

Many data scientists do the same in their careers.

They position themselves as “data science experts” without articulating what specific value they bring.

They say things like:

  • “I’m a machine learning specialist”
  • “I do predictive analytics”
  • “I’m passionate about data science”

None of this tells a potential employer what problem you actually solve for them.

Just like my old blog posts, it’s “nice to have” information that doesn’t clearly communicate value.

The shift happened when I stopped thinking “what do I know?” and started thinking “what problems can I solve?”

Instead of random data science commentary, I focused on helping data scientists create business impact and advance their careers.

My audience doubled in 4 months.

Instead of being “Genevieve the data science expert,” I became “Genevieve who helps data scientists turn their technical skills into career growth.”

The same principle applies to your career:

  • Don’t just tell people you’re a data scientist. Tell them what you can do for their business.
  • Don’t just list your technical skills. Frame them around the value they bring.

What problems can you solve and who can you solve them for?

Answer that question, and you’ll become more than just “nice to have.”

Talk again soon,

Dr Genevieve Hayes.

p.s. This is the first post I'm sending from my new email provider, Kit. To make sure everything is working, if you can read this message, please reply and let me know.

Data Science Impact Algorithm

Twice weekly, I share proven strategies to help data scientists get noticed, promoted, and valued. No theory — just practical steps to transform your technical expertise into business impact and the freedom to call your own shots.

Read more from Data Science Impact Algorithm

I've built data science solutions that nobody wanted to use. Technically brilliant models. Clean code. Perfect documentation. And exactly zero end-users. If you're a traditional employee, working within an organisation, this situation is depressing. If you're an independent data professional, this situation can be financially devastating. Yet some data professionals seem to avoid this trap entirely. Take Daniel Bourke. His machine learning courses have over 250,000 students. His Nutrify app...

I recently met a brilliant data scientist who had built some amazing AI automation tools. But he kept saying things like “it’s not very original” and “I’m not building anything new, I’m just piecing together what’s there.” And I told him: “Your solutions don’t have to be original. They just have to solve the problem.” This is something I see all the time with technical people. They think they need to invent something revolutionary to be valuable. Here’s the thing… Your stakeholders don’t care...

Like most data scientists, I started my career in traditional 9-to-5 roles. With bills to pay and limited experience, a regular job felt "safe". Then COVID hit. Nothing felt "safe" anymore, and my dreams of working for myself no longer seemed so insane. I finally made the leap - and never looked back. Many data scientists share similar dreams of breaking free from traditional employment, but don't know where to begin. Yet, here's what I've learned along the way: there's no single path to data...