This week, I will present a webinar on hiring a startup’s first Data-to-AI specialist.
Why Data-to-AI rather than Data & AI?
Because AI isn’t distinct from Data – AI is built on data. Further, solid data plumbing underlies both analytics and advanced AI/ML. Despite the hype, descriptive models (aka analytics) are often as critical as predictive and causal models (aka advanced AI/ML & statistics).
As practice for the webinar, I recorded myself going through the first part of the deck. I’m a bit uncomfortable watching myself, which makes sharing the video an especially valuable exercise:
The full slides are here (use the left/right and up/down arrows to navigate).
Key points from the video
These are the key points covered in the video, along with a couple of pointers to relevant posts:
- Intro: The intended audience and my relevant background.
- Main goal of the webinar: Avoid expensive mistakes – remembering that the cost of a wrong hire entails compensation + slowdown + opportunity.
- Sub-goals:
- De-hype Data & AI
- Clarify needs & opportunities
- Consider not hiring
- Hire well
- Avoid pitfalls
- Dataland is Venn diagram paradise – but startups need not worry about Dataland Venns. The lines between areas like artificial intelligence and data science are arbitrary and blurry. In any case, startups need generalists early on.
- Ask de-hyping questions on plumbing, decisions, and automation:
- Plumbing: What’s the state of your data engineering lifecycles?
- Decisions: How do you use descriptive, predictive, and causal modelling to support decisions?
- Automation: How do you use AI to automate processes?
- Work up from principles and business problems rather than by starting with the many tools from the MAD landscape. But keep in mind that tools do matter. Paraphrasing a quote from David Allen, a great wrench doesn’t make a great plumber, but a great plumber will always want to use a great wrench.
- Keep these terms in mind:
- Basic AI: Black boxes like ChatGPT and transcription tools.
- Advanced AI/ML: Custom models, harder, requires MLOps & serious data work beyond the prototype.
- Analytics: The M in Build-Measure-Learn, key to product-led growth – depends on plumbing.
- Don’t expect magic: Advanced AI/ML and Analytics are both hard and depend on solid plumbing.
Going deep into one Venn diagram
After creating the initial draft of the slides and making fun of Dataland Venns, I realised that going deep into one Venn diagram would be beneficial. I cover the diagram below in the last part of the video.
In the diagram, I highlight these three roles:
- Analyst: Focused on understanding and explaining the business (descriptive modelling)
- Engineer: Focused on building scalable systems (i.e., plumbing)
- Statistician: Focused on building mathematical models from data (predictive and causal modelling)
This diagram evolved from a post I wrote on the first data hire a few months ago. I adapted it from Andrew Bartholomew’s post on the same topic. The main change from the original is that it now contains two different recommendations for the first hire:
- Data Tech Lead (Analytics Engineer): If the startup isn’t AI/ML-centric or highly data-intensive, the first data hire would likely focus on setting up data pipelines and analytics. Therefore, they should have the skills of an analytics engineer (between an analyst and a data engineer).
- AI/ML Lead (AI/ML Engineer): If advanced AI/ML is core to the startup’s product, the first data hire would focus on building and iterating on the product. Therefore, they should have the skills of an AI/ML engineer and of a data engineer (i.e., build and scale data pipelines and AI/ML in production).
In the middle of the diagram, we have the unicorns who are good at everything. These do exist – they’re just hard to hire and retain. But even the most talented person can’t do everything all the time. That’s why hiring for one of the above two options is more feasible.
Next up, I’ll record the second part of the webinar, which covers the actual hiring. In the meantime, any feedback is welcome.
Update 2024-07-22: The second part is here.
Public comments are closed, but I love hearing from readers. Feel free to contact me with your thoughts.